sensors Mode-S transponder
346386
ICAO 24-bit transponder address · allocated to Spain
Currently assigned to EC-NGT · AIRBUS A-350-900
- Hex
- 346386
- Octal
- 15061606
- Decimal
- 3,433,350
- Country
- ES
- Tail
- EC-NGT
- Type
- A359
- Flights observed
- 162
- Distinct callsigns
- 20
- Country
- ES
- Last broadcast
- 6h ago
Last known position
Country allocation
The ICAO 24-bit address 346386 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 |
|---|---|---|---|
| IBE0138 | Iberia Airlines | 11 | 2026-05-23 |
| IBE0137 | - | 7 | 2026-07-13 |
| IBE0308 | - | 6 | 2026-06-19 |
| IBE0307 | - | 6 | 2026-06-18 |
| IBE0304 | Iberia Airlines | 6 | 2026-06-25 |
| IBE0303 | - | 6 | 2026-06-24 |
| IBE0152 | Iberia Airlines | 6 | 2026-05-23 |
| IBE0117 | Iberia Airlines | 6 | 2026-06-04 |
| IBE0103 | Iberia Airlines | 6 | 2026-05-02 |
| IBE03ZB | - | 5 | 2026-07-04 |
| IBE0156 | - | 5 | 2026-07-03 |
| IBE0154 | - | 5 | 2026-06-30 |
| IBE0153 | Iberia Airlines | 5 | 2026-06-29 |
| IBE0151 | Iberia Airlines | 5 | 2026-05-22 |
| IBE0102 | Iberia Airlines | 5 | 2026-05-03 |
| IBE0352 | - | 4 | 2026-07-05 |
| IBE0124 | - | 4 | 2026-06-14 |
| IBE0118 | Iberia Airlines | 4 | 2026-06-05 |
| IBE5109 | - | 3 | 2026-06-30 |
| IBE0311 | Iberia Airlines | 3 | 2026-06-11 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | IBE0137 | - | Jul 13, 11:10 UTC | Jul 14, 00:50 UTC | 13h 40m |
| 2026-07-12 | IBE0212 | - | Jul 12, 21:45 UTC | Jul 13, 04:05 UTC | 6h 20m |
| 2026-07-12 | IBE02DA | MAD → JFK | Jul 12, 11:25 UTC | Jul 12, 18:30 UTC | 7h 5m |
| 2026-07-05 | IBE0352 | - | Jul 5, 01:00 UTC | Jul 5, 11:10 UTC | 10h 10m |
| 2026-07-04 | IBE03ZB | - | Jul 4, 11:35 UTC | Jul 4, 22:35 UTC | 11h 0m |
| 2026-07-03 | IBE5106 | - | Jul 3, 21:15 UTC | Jul 4, 08:05 UTC | 10h 50m |
| 2026-07-03 | IBE5105 | - | Jul 3, 07:10 UTC | Jul 3, 19:25 UTC | 12h 15m |
| 2026-07-03 | IBE0156 | - | Jul 3, 01:55 UTC | Jul 3, 03:00 UTC | 1h 5m |
| 2026-07-01 | IBE0155 | - | Jul 1, 22:35 UTC | Jul 1, 23:55 UTC | 1h 20m |
| 2026-07-01 | IBE5110 | - | Jul 1, 04:40 UTC | Jul 1, 15:55 UTC | 11h 15m |
| 2026-06-30 | IBE5109 | MAD → EZE | Jun 30, 14:50 UTC | Jul 1, 02:50 UTC | 12h 0m |
| 2026-06-30 | IBE0154 | - | Jun 30, 04:30 UTC | Jun 30, 11:50 UTC | 7h 20m |
| 2026-06-29 | IBE0153 | XRY → MAD | Jun 29, 15:09 UTC | Jun 29, 16:19 UTC | 1h 10m |
| 2026-06-29 | IBE5108 | - | Jun 29, 01:00 UTC | Jun 29, 12:14 UTC | 11h 15m |
| 2026-06-28 | IBE5107 | MAD → EZE | Jun 28, 10:44 UTC | Jun 28, 22:39 UTC | 11h 55m |
| 2026-06-27 | IBE5106 | - | Jun 27, 20:59 UTC | Jun 28, 08:19 UTC | 11h 20m |
| 2026-06-27 | IBE5105 | - | Jun 27, 07:15 UTC | Jun 27, 19:05 UTC | 11h 50m |
| 2026-06-25 | IBE0304 | MEX → MAD | Jun 25, 17:30 UTC | Jun 26, 03:24 UTC | 9h 55m |
| 2026-06-24 | IBE0303 | MAD → MEX | Jun 24, 22:10 UTC | Jun 25, 08:45 UTC | 10h 35m |
| 2026-06-24 | IBE5110 | EZE → MAD | Jun 24, 04:44 UTC | Jun 24, 16:14 UTC | 11h 30m |
| 2026-06-24 | IBE5109 | - | Jun 24, 01:04 UTC | Jun 24, 02:45 UTC | 1h 40m |
| 2026-06-23 | IBE5109 | - | Jun 23, 14:49 UTC | Jun 24, 00:59 UTC | 10h 10m |
| 2026-06-23 | IBE0154 | - | Jun 23, 10:59 UTC | Jun 23, 12:20 UTC | 1h 20m |
| 2026-06-22 | IBE0153 | XRY → MAD | Jun 22, 15:20 UTC | Jun 22, 16:29 UTC | 1h 10m |
| 2026-06-21 | IBE03TH | - | Jun 21, 21:10 UTC | Jun 22, 04:54 UTC | 7h 45m |
| 2026-06-21 | IBE03TM | MIA → MAD | Jun 21, 10:25 UTC | Jun 21, 19:05 UTC | 8h 40m |
| 2026-06-20 | IBE0304 | MEX → MAD | Jun 20, 17:54 UTC | Jun 21, 03:40 UTC | 9h 45m |
| 2026-06-19 | IBE0303 | - | Jun 19, 22:14 UTC | Jun 20, 08:59 UTC | 10h 45m |
| 2026-06-19 | IBE0308 | - | Jun 19, 02:45 UTC | Jun 19, 12:54 UTC | 10h 10m |
| 2026-06-18 | IBE0307 | - | Jun 18, 11:50 UTC | Jun 18, 23:00 UTC | 11h 10m |
| 2026-06-17 | IBE0304 | MEX → MAD | Jun 17, 17:40 UTC | Jun 18, 03:45 UTC | 10h 5m |
| 2026-06-16 | IBE0303 | - | Jun 16, 22:30 UTC | Jun 17, 09:00 UTC | 10h 30m |
| 2026-06-16 | IBE5108 | EZE → MAD | Jun 16, 01:25 UTC | Jun 16, 12:45 UTC | 11h 20m |
| 2026-06-15 | IBE5107 | MAD → EZE | Jun 15, 11:00 UTC | Jun 15, 23:25 UTC | 12h 25m |
| 2026-06-14 | IBE0124 | - | Jun 14, 07:55 UTC | Jun 15, 03:15 UTC | 19h 19m |
| 2026-06-13 | IBE0123 | MAD → LIM | Jun 13, 23:35 UTC | Jun 14, 17:50 UTC | 18h 15m |
| 2026-06-13 | IBE0123 | MAD → LIM | Jun 13, 22:30 UTC | Jun 14, 17:50 UTC | 19h 20m |
| 2026-06-13 | IBE0032 | DUS → SAL | Jun 13, 05:55 UTC | Jun 13, 15:55 UTC | 10h 0m |
| 2026-06-11 | IBE0311 | MAD → MEX | Jun 11, 17:00 UTC | Jun 12, 03:35 UTC | 10h 36m |
| 2026-06-11 | IBE0308 | MEX → MAD | Jun 11, 01:20 UTC | Jun 11, 11:45 UTC | 10h 25m |
| 2026-06-10 | IBE0307 | MAD → MEX | Jun 10, 11:40 UTC | Jun 10, 22:15 UTC | 10h 35m |
| 2026-06-09 | IBE0106 | MAD → SVQ | Jun 9, 21:30 UTC | Jun 10, 08:20 UTC | 10h 50m |
| 2026-06-09 | IBE0105 | MAD → EZE | Jun 9, 07:05 UTC | Jun 9, 19:05 UTC | 12h 0m |
| 2026-06-08 | IBE0304 | MEX → MAD | Jun 8, 17:55 UTC | Jun 9, 03:55 UTC | 10h 0m |
| 2026-06-07 | IBE0303 | MAD → MEX | Jun 7, 22:20 UTC | Jun 8, 09:20 UTC | 11h 0m |
| 2026-06-07 | IBE0282 | NRT → MAD | Jun 7, 03:05 UTC | Jun 7, 17:55 UTC | 14h 50m |
| 2026-06-06 | IBE0281 | MAD → NRT | Jun 6, 10:50 UTC | Jun 6, 23:50 UTC | 13h 0m |
| 2026-06-05 | IBE0118 | SCL → MAD | Jun 5, 16:55 UTC | Jun 6, 02:40 UTC | 9h 45m |
| 2026-06-05 | IBE0118 | SCL → MAD | Jun 5, 15:05 UTC | Jun 5, 15:20 UTC | 15m |
| 2026-06-04 | IBE0117 | SVQ → MAD | Jun 4, 22:25 UTC | Jun 5, 09:30 UTC | 11h 5m |
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-NGT page for operator, model, and routing details .