sensors Mode-S transponder
347386
ICAO 24-bit transponder address · allocated to Spain
Currently assigned to EC-NXC · AIRBUS A-350-900
- Hex
- 347386
- Octal
- 15071606
- Decimal
- 3,437,446
- Country
- ES
- Tail
- EC-NXC
- Type
- A359
- Flights observed
- 196
- Distinct callsigns
- 20
- Country
- ES
- Last broadcast
- 14m ago
Current position
Country allocation
The ICAO 24-bit address 347386 falls within the block assigned to Spain (ES) by ICAO Annex 10, Volume III. Every aircraft registered in Spain receives a permanent address from this block at the time of registration; the address stays with the airframe even if the aircraft is re-registered to a different operator within the country.
Callsign history 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| IBE0152 | - | 13 | 2026-07-06 |
| IBE0151 | Iberia Airlines | 12 | 2026-07-06 |
| IBE0107 | Iberia Airlines | 12 | 2026-06-10 |
| IBE0154 | Iberia Airlines | 11 | 2026-06-03 |
| IBE0108 | Iberia Airlines | 10 | 2026-06-11 |
| IBE0307 | - | 8 | 2026-06-21 |
| IBE0156 | - | 8 | 2026-07-11 |
| IBE0155 | - | 8 | 2026-07-09 |
| IBE0138 | - | 8 | 2026-07-07 |
| IBE0312 | - | 7 | 2026-07-02 |
| IBE0308 | - | 7 | 2026-06-22 |
| IBE0153 | Iberia Airlines | 7 | 2026-06-02 |
| IBE0311 | - | 6 | 2026-07-01 |
| IBE0304 | - | 5 | 2026-07-14 |
| IBE0303 | - | 5 | 2026-07-13 |
| IBE0124 | - | 5 | 2026-06-28 |
| IBE0121 | Iberia Airlines | 5 | 2026-04-17 |
| IBE0118 | Iberia Airlines | 5 | 2026-05-08 |
| IBE0103 | - | 5 | 2026-06-14 |
| IBE5107 | - | 4 | 2026-07-12 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | IBE0304 | - | Jul 14, 17:35 UTC | Jul 14, 19:30 UTC | 1h 55m |
| 2026-07-13 | IBE0303 | - | Jul 13, 22:35 UTC | Jul 14, 09:20 UTC | 10h 45m |
| 2026-07-13 | IBE5108 | - | Jul 13, 01:01 UTC | Jul 13, 12:05 UTC | 11h 5m |
| 2026-07-12 | IBE5107 | - | Jul 12, 12:50 UTC | Jul 12, 23:15 UTC | 10h 25m |
| 2026-07-12 | IBE5107 | - | Jul 12, 10:55 UTC | Jul 12, 12:20 UTC | 1h 25m |
| 2026-07-11 | IBE0156 | - | Jul 11, 00:55 UTC | Jul 11, 02:50 UTC | 1h 55m |
| 2026-07-10 | IBE0156 | - | Jul 10, 17:55 UTC | Jul 10, 18:05 UTC | 10m |
| 2026-07-09 | IBE0155 | - | Jul 9, 22:30 UTC | Jul 9, 23:50 UTC | 1h 20m |
| 2026-07-09 | IBE03KE | - | Jul 9, 01:40 UTC | Jul 9, 08:05 UTC | 6h 25m |
| 2026-07-08 | IBE03SD | MAD → JFK | Jul 8, 15:05 UTC | Jul 8, 22:10 UTC | 7h 5m |
| 2026-07-07 | IBE0138 | - | Jul 7, 19:30 UTC | Jul 8, 09:10 UTC | 13h 40m |
| 2026-07-07 | IBE0138 | - | Jul 7, 11:35 UTC | Jul 8, 09:10 UTC | 21h 35m |
| 2026-07-07 | IBE0137 | - | Jul 7, 10:30 UTC | Jul 8, 02:10 UTC | 15h 40m |
| 2026-07-06 | IBE0152 | BOG → MAD | Jul 6, 22:45 UTC | Jul 7, 07:45 UTC | 9h 0m |
| 2026-07-06 | IBE0151 | XRY → MAD | Jul 6, 10:50 UTC | Jul 6, 20:00 UTC | 9h 10m |
| 2026-07-05 | IBE4270 | - | Jul 5, 22:55 UTC | Jul 6, 07:55 UTC | 9h 0m |
| 2026-07-05 | IBE4269 | - | Jul 5, 11:00 UTC | Jul 5, 20:40 UTC | 9h 40m |
| 2026-07-04 | IBE5106 | EZE → MAD | Jul 4, 21:20 UTC | Jul 5, 08:15 UTC | 10h 55m |
| 2026-07-04 | IBE5105 | - | Jul 4, 07:15 UTC | Jul 4, 19:20 UTC | 12h 5m |
| 2026-07-04 | IBE0156 | - | Jul 4, 01:35 UTC | Jul 4, 02:55 UTC | 1h 20m |
| 2026-07-03 | IBE0156 | - | Jul 3, 05:35 UTC | Jul 4, 02:55 UTC | 21h 20m |
| 2026-07-02 | IBE0155 | - | Jul 2, 22:25 UTC | Jul 3, 06:55 UTC | 8h 30m |
| 2026-07-02 | IBE0312 | - | Jul 2, 06:20 UTC | Jul 2, 16:50 UTC | 10h 30m |
| 2026-07-01 | IBE0311 | - | Jul 1, 16:45 UTC | Jul 2, 03:25 UTC | 10h 40m |
| 2026-07-01 | IBE5108 | - | Jul 1, 00:50 UTC | Jul 1, 12:05 UTC | 11h 15m |
| 2026-06-30 | IBE5107 | MAD → EZE | Jun 30, 10:50 UTC | Jun 30, 22:50 UTC | 12h 0m |
| 2026-06-30 | IBE0152 | - | Jun 30, 06:35 UTC | Jun 30, 07:45 UTC | 1h 10m |
| 2026-06-29 | IBE0151 | XRY → MAD | Jun 29, 11:35 UTC | Jun 30, 07:45 UTC | 20h 11m |
| 2026-06-29 | IBE0151 | XRY → MAD | Jun 29, 10:59 UTC | Jun 30, 07:45 UTC | 20h 46m |
| 2026-06-28 | IBE0124 | - | Jun 28, 14:54 UTC | Jun 29, 06:40 UTC | 15h 45m |
| 2026-06-28 | IBE0127 | - | Jun 28, 05:34 UTC | Jun 29, 05:30 UTC | 23h 55m |
| 2026-06-27 | IBE0156 | CZE → MAD | Jun 27, 18:49 UTC | Jun 28, 02:39 UTC | 7h 50m |
| 2026-06-26 | IBE0155 | - | Jun 26, 22:44 UTC | Jun 27, 07:15 UTC | 8h 30m |
| 2026-06-26 | IBE5108 | - | Jun 26, 00:59 UTC | Jun 26, 12:19 UTC | 11h 20m |
| 2026-06-25 | IBE5107 | MAD → EZE | Jun 25, 10:59 UTC | Jun 25, 22:45 UTC | 11h 45m |
| 2026-06-24 | IBE0124 | - | Jun 24, 08:09 UTC | Jun 25, 02:49 UTC | 18h 40m |
| 2026-06-24 | IBE0124 | - | Jun 24, 05:59 UTC | Jun 25, 02:49 UTC | 20h 50m |
| 2026-06-23 | IBE0123 | MAD → LIM | Jun 23, 23:34 UTC | Jun 24, 17:59 UTC | 18h 25m |
| 2026-06-23 | IBE0123 | MAD → LIM | Jun 23, 22:25 UTC | Jun 24, 17:59 UTC | 19h 35m |
| 2026-06-23 | IBE6116 | - | Jun 23, 07:05 UTC | Jun 23, 17:15 UTC | 10h 10m |
| 2026-06-23 | IBE6116 | - | Jun 23, 05:20 UTC | Jun 23, 05:29 UTC | 10m |
| 2026-06-22 | IBE6113 | - | Jun 22, 14:34 UTC | Jun 23, 01:25 UTC | 10h 50m |
| 2026-06-22 | IBE0308 | - | Jun 22, 01:29 UTC | Jun 22, 11:54 UTC | 10h 25m |
| 2026-06-21 | IBE0307 | MAD → MEX | Jun 21, 11:55 UTC | Jun 21, 22:44 UTC | 10h 50m |
| 2026-06-21 | IBE0156 | - | Jun 21, 01:19 UTC | Jun 21, 02:45 UTC | 1h 25m |
| 2026-06-19 | IBE0155 | - | Jun 19, 22:24 UTC | Jun 20, 06:54 UTC | 8h 30m |
| 2026-06-18 | IBE0126 | LIM → MAD | Jun 18, 21:50 UTC | Jun 19, 12:19 UTC | 14h 29m |
| 2026-06-18 | IBE0126 | LIM → MAD | Jun 18, 13:35 UTC | Jun 19, 12:19 UTC | 22h 44m |
| 2026-06-18 | IBE0125 | - | Jun 18, 12:10 UTC | Jun 19, 11:30 UTC | 23h 19m |
| 2026-06-18 | IBE03KE | JFK → MAD | Jun 18, 01:50 UTC | Jun 18, 08:00 UTC | 6h 10m |
About Mode-S
A Mode-S transponder code (also called an "ICAO 24-bit address" or "hex code") is a 6-character hexadecimal identifier permanently assigned to an aircraft when it's first registered. Unlike callsigns (which change with each flight) or registrations (which can change if an aircraft is sold internationally), the Mode-S address stays with the airframe for the life of the aircraft in that country.
Every ADS-B transmission from an aircraft includes its Mode-S address, making it the most reliable way to identify a specific airframe. Flight-tracking services like Apparatus use the Mode-S address as the primary key for tying position broadcasts, callsigns, and ownership records together.
Prefer a tail-number view? See the EC-NXC page for operator, model, and routing details .