sensors Mode-S transponder
347343
ICAO 24-bit transponder address · allocated to Spain
Currently assigned to EC-NVR · AIRBUS A-350-900
- Hex
- 347343
- Octal
- 15071503
- Decimal
- 3,437,379
- Country
- ES
- Tail
- EC-NVR
- Type
- A359
- Flights observed
- 193
- Distinct callsigns
- 20
- Country
- ES
- Last broadcast
- 21m ago
Current position
Country allocation
The ICAO 24-bit address 347343 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 |
|---|---|---|---|
| IBE0281 | - | 11 | 2026-06-27 |
| IBE0154 | - | 11 | 2026-06-15 |
| IBE0282 | Iberia Airlines | 10 | 2026-06-28 |
| IBE0103 | Iberia Airlines | 9 | 2026-06-09 |
| IBE0312 | - | 8 | 2026-07-12 |
| IBE0311 | - | 8 | 2026-07-11 |
| IBE0303 | - | 7 | 2026-07-01 |
| IBE0153 | Iberia Airlines | 7 | 2026-06-14 |
| IBE0102 | Iberia Airlines | 7 | 2026-06-10 |
| IBE0155 | Iberia Airlines | 6 | 2026-05-19 |
| IBE0114 | Iberia Airlines | 6 | 2026-06-08 |
| IBE0307 | - | 5 | 2026-07-14 |
| IBE6118 | - | 4 | 2026-07-06 |
| IBE5108 | - | 4 | 2026-07-04 |
| IBE5107 | - | 4 | 2026-07-03 |
| IBE07MM | - | 4 | 2026-07-01 |
| IBE07GF | - | 4 | 2026-07-01 |
| IBE0308 | - | 4 | 2026-06-12 |
| IBE0304 | Iberia Airlines | 4 | 2026-07-02 |
| IBE0156 | Iberia Airlines | 4 | 2026-05-19 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | IBE0307 | - | Jul 14, 12:10 UTC | Jul 14, 12:45 UTC | 35m |
| 2026-07-13 | IBE5102 | - | Jul 13, 16:10 UTC | Jul 14, 03:10 UTC | 11h 0m |
| 2026-07-12 | IBE5103 | - | Jul 12, 22:40 UTC | Jul 13, 10:55 UTC | 12h 15m |
| 2026-07-12 | IBE0312 | - | Jul 12, 06:10 UTC | Jul 12, 16:05 UTC | 9h 55m |
| 2026-07-11 | IBE0311 | - | Jul 11, 16:55 UTC | Jul 12, 03:45 UTC | 10h 50m |
| 2026-07-11 | IBE0126 | - | Jul 11, 02:30 UTC | Jul 11, 12:15 UTC | 9h 45m |
| 2026-07-10 | IBE0125 | - | Jul 10, 11:50 UTC | Jul 10, 22:55 UTC | 11h 5m |
| 2026-07-09 | IBE6114 | - | Jul 9, 20:45 UTC | Jul 10, 08:50 UTC | 12h 5m |
| 2026-07-09 | IBE6113 | - | Jul 9, 06:00 UTC | Jul 9, 16:25 UTC | 10h 25m |
| 2026-07-08 | IBE0352 | - | Jul 8, 01:10 UTC | Jul 8, 11:30 UTC | 10h 20m |
| 2026-07-07 | IBE03ZB | - | Jul 7, 11:40 UTC | Jul 7, 22:45 UTC | 11h 5m |
| 2026-07-06 | IBE6118 | - | Jul 6, 16:00 UTC | Jul 7, 03:05 UTC | 11h 5m |
| 2026-07-06 | IBE6118 | - | Jul 6, 15:15 UTC | Jul 6, 15:25 UTC | 10m |
| 2026-07-05 | IBE6117 | - | Jul 5, 22:25 UTC | Jul 6, 09:15 UTC | 10h 50m |
| 2026-07-05 | IBE0312 | MEX → MAD | Jul 5, 06:25 UTC | Jul 5, 16:25 UTC | 10h 0m |
| 2026-07-04 | IBE0311 | MAD → MEX | Jul 4, 17:50 UTC | Jul 5, 04:15 UTC | 10h 25m |
| 2026-07-04 | IBE5108 | - | Jul 4, 01:15 UTC | Jul 4, 12:05 UTC | 10h 50m |
| 2026-07-03 | IBE5107 | MAD → EZE | Jul 3, 10:40 UTC | Jul 3, 22:55 UTC | 12h 15m |
| 2026-07-02 | IBE0304 | MEX → MAD | Jul 2, 17:25 UTC | Jul 3, 03:40 UTC | 10h 15m |
| 2026-07-01 | IBE0303 | - | Jul 1, 22:25 UTC | Jul 2, 09:00 UTC | 10h 35m |
| 2026-07-01 | IBE07GF | - | Jul 1, 18:00 UTC | Jul 1, 19:45 UTC | 1h 45m |
| 2026-07-01 | IBE07MM | MAD → LHR | Jul 1, 14:25 UTC | Jul 1, 16:10 UTC | 1h 45m |
| 2026-06-30 | IBE0126 | LIM → MAD | Jun 30, 21:45 UTC | Jul 1, 12:10 UTC | 14h 25m |
| 2026-06-30 | IBE0126 | LIM → MAD | Jun 30, 12:50 UTC | Jul 1, 12:10 UTC | 23h 20m |
| 2026-06-30 | IBE0125 | - | Jun 30, 12:10 UTC | Jul 1, 10:45 UTC | 22h 35m |
| 2026-06-29 | IBE6118 | - | Jun 29, 16:44 UTC | Jun 30, 02:55 UTC | 10h 11m |
| 2026-06-29 | IBE6118 | - | Jun 29, 15:00 UTC | Jun 29, 15:09 UTC | 10m |
| 2026-06-28 | IBE6117 | - | Jun 28, 22:45 UTC | Jun 29, 09:14 UTC | 10h 30m |
| 2026-06-28 | IBE0282 | NRT → MAD | Jun 28, 02:44 UTC | Jun 28, 17:30 UTC | 14h 45m |
| 2026-06-27 | IBE0281 | MAD → NRT | Jun 27, 11:14 UTC | Jun 28, 00:30 UTC | 13h 15m |
| 2026-06-26 | IBE03CY | - | Jun 26, 22:25 UTC | Jun 27, 05:29 UTC | 7h 5m |
| 2026-06-26 | IBE03SY | MAD → ORD | Jun 26, 10:30 UTC | Jun 26, 19:00 UTC | 8h 30m |
| 2026-06-26 | IBE03KE | - | Jun 26, 01:29 UTC | Jun 26, 07:45 UTC | 6h 15m |
| 2026-06-25 | IBE03SD | MAD → JFK | Jun 25, 14:55 UTC | Jun 25, 22:20 UTC | 7h 25m |
| 2026-06-23 | IBE0312 | - | Jun 23, 06:34 UTC | Jun 23, 16:44 UTC | 10h 10m |
| 2026-06-22 | IBE0311 | - | Jun 22, 17:04 UTC | Jun 23, 03:39 UTC | 10h 35m |
| 2026-06-22 | IBE5108 | - | Jun 22, 11:35 UTC | Jun 22, 12:59 UTC | 1h 25m |
| 2026-06-22 | IBE5108 | - | Jun 22, 01:29 UTC | Jun 22, 11:30 UTC | 10h 0m |
| 2026-06-21 | IBE5107 | - | Jun 21, 18:29 UTC | Jun 21, 23:00 UTC | 4h 30m |
| 2026-06-21 | IBE5107 | - | Jun 21, 11:00 UTC | Jun 21, 12:14 UTC | 1h 15m |
| 2026-06-21 | IBE03KE | JFK → MAD | Jun 21, 02:20 UTC | Jun 21, 08:40 UTC | 6h 20m |
| 2026-06-20 | IBE03SD | MAD → JFK | Jun 20, 15:34 UTC | Jun 20, 23:10 UTC | 7h 35m |
| 2026-06-20 | IBE5108 | - | Jun 20, 00:59 UTC | Jun 20, 12:45 UTC | 11h 45m |
| 2026-06-19 | IBE5107 | - | Jun 19, 10:50 UTC | Jun 19, 22:30 UTC | 11h 40m |
| 2026-06-18 | IBE0132 | GYE → MAD | Jun 18, 15:15 UTC | Jun 19, 05:40 UTC | 14h 24m |
| 2026-06-18 | IBE0131 | - | Jun 18, 06:20 UTC | Jun 19, 04:44 UTC | 22h 24m |
| 2026-06-17 | IBE5102 | - | Jun 17, 16:05 UTC | Jun 18, 02:50 UTC | 10h 45m |
| 2026-06-16 | IBE5103 | - | Jun 16, 22:35 UTC | Jun 17, 11:05 UTC | 12h 30m |
| 2026-06-16 | IBE0312 | - | Jun 16, 06:15 UTC | Jun 16, 15:55 UTC | 9h 40m |
| 2026-06-15 | IBE0311 | - | Jun 15, 16:35 UTC | Jun 16, 03:10 UTC | 10h 35m |
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-NVR page for operator, model, and routing details .