sensors Mode-S transponder
34520F
ICAO 24-bit transponder address · allocated to Spain
Currently assigned to EC-MNL · AIRBUS A-330-200
- Hex
- 34520F
- Octal
- 15051017
- Decimal
- 3,428,879
- Country
- ES
- Tail
- EC-MNL
- Type
- A332
- Flights observed
- 180
- Distinct callsigns
- 20
- Country
- ES
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address 34520F 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 |
|---|---|---|---|
| IBE0222 | - | 18 | 2026-06-23 |
| IBE0132 | Iberia Airlines | 12 | 2026-07-02 |
| IBE0221 | Iberia Airlines | 9 | 2026-06-22 |
| IBE0131 | - | 9 | 2026-07-01 |
| IBE03AE | Iberia Airlines | 8 | 2026-07-08 |
| IBE0169 | Iberia Airlines | 8 | 2026-06-18 |
| IBE03PB | - | 7 | 2026-07-09 |
| IBE0306 | - | 7 | 2026-07-08 |
| IBE0305 | - | 7 | 2026-07-07 |
| IBE0258 | Iberia Airlines | 7 | 2026-07-05 |
| IBE0272 | Iberia Airlines | 5 | 2026-04-17 |
| IBE0170 | - | 5 | 2026-06-19 |
| IBE02SJ | - | 4 | 2026-07-12 |
| IBE0271 | Iberia Airlines | 4 | 2026-04-16 |
| IBE0124 | Iberia Airlines | 4 | 2026-06-01 |
| IBE03KK | Iberia Airlines | 3 | 2026-05-24 |
| IBE0356 | - | 3 | 2026-07-10 |
| IBE0355 | - | 3 | 2026-07-09 |
| IBE02CR | - | 3 | 2026-07-12 |
| IBE0274 | Iberia Airlines | 3 | 2026-05-28 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | IBE3267 | MAD → GRU | Jul 13, 22:45 UTC | Jul 14, 09:30 UTC | 10h 45m |
| 2026-07-12 | IBE02CR | - | Jul 12, 22:30 UTC | Jul 13, 08:25 UTC | 9h 55m |
| 2026-07-12 | IBE02SJ | MAD → SJO | Jul 12, 09:55 UTC | Jul 12, 20:25 UTC | 10h 30m |
| 2026-07-11 | IBE03TH | - | Jul 11, 21:10 UTC | Jul 12, 05:35 UTC | 8h 25m |
| 2026-07-11 | IBE03TM | MAD → MIA | Jul 11, 10:05 UTC | Jul 11, 18:55 UTC | 8h 50m |
| 2026-07-10 | IBE0922 | - | Jul 10, 23:15 UTC | Jul 11, 02:55 UTC | 3h 40m |
| 2026-07-10 | IBE09RY | - | Jul 10, 17:15 UTC | Jul 10, 21:25 UTC | 4h 10m |
| 2026-07-10 | IBE0356 | - | Jul 10, 01:20 UTC | Jul 10, 11:55 UTC | 10h 35m |
| 2026-07-09 | IBE0355 | MAD → SFO | Jul 9, 11:25 UTC | Jul 9, 23:00 UTC | 11h 35m |
| 2026-07-09 | IBE03PB | - | Jul 9, 07:35 UTC | Jul 9, 08:50 UTC | 1h 15m |
| 2026-07-09 | IBE03PB | - | Jul 9, 01:15 UTC | Jul 9, 01:30 UTC | 15m |
| 2026-07-08 | IBE03AE | MAD → SJU | Jul 8, 22:35 UTC | Jul 8, 23:00 UTC | 25m |
| 2026-07-08 | IBE03AE | MAD → SJU | Jul 8, 14:40 UTC | Jul 8, 16:10 UTC | 1h 30m |
| 2026-07-08 | IBE0306 | MTY → MAD | Jul 8, 00:45 UTC | Jul 8, 10:30 UTC | 9h 45m |
| 2026-07-07 | IBE0305 | MAD → MTY | Jul 7, 11:50 UTC | Jul 7, 22:25 UTC | 10h 35m |
| 2026-07-06 | IBE0264 | - | Jul 6, 14:45 UTC | Jul 7, 08:55 UTC | 18h 10m |
| 2026-07-05 | IBE0258 | PTY → MAD | Jul 5, 22:40 UTC | Jul 6, 11:55 UTC | 13h 15m |
| 2026-07-05 | IBE0258 | PTY → MAD | Jul 5, 15:50 UTC | Jul 6, 11:55 UTC | 20h 5m |
| 2026-07-05 | IBE0258 | PTY → MAD | Jul 5, 14:50 UTC | Jul 6, 11:55 UTC | 21h 5m |
| 2026-07-05 | IBE0306 | MTY → MAD | Jul 5, 03:05 UTC | Jul 5, 12:30 UTC | 9h 25m |
| 2026-07-04 | IBE0305 | - | Jul 4, 14:05 UTC | Jul 5, 00:45 UTC | 10h 40m |
| 2026-07-03 | IBE02CR | - | Jul 3, 23:15 UTC | Jul 4, 09:20 UTC | 10h 5m |
| 2026-07-03 | IBE02SJ | - | Jul 3, 10:00 UTC | Jul 3, 19:55 UTC | 9h 55m |
| 2026-07-02 | IBE0132 | GYE → MAD | Jul 2, 08:10 UTC | Jul 3, 03:20 UTC | 19h 10m |
| 2026-07-01 | IBE0131 | - | Jul 1, 23:50 UTC | Jul 2, 18:00 UTC | 18h 10m |
| 2026-07-01 | IBE0131 | - | Jul 1, 22:40 UTC | Jul 2, 18:00 UTC | 19h 20m |
| 2026-07-01 | IBE0306 | MEX → MAD | Jul 1, 01:00 UTC | Jul 1, 10:55 UTC | 9h 55m |
| 2026-06-30 | IBE0305 | MEX → MAD | Jun 30, 11:40 UTC | Jun 30, 22:25 UTC | 10h 45m |
| 2026-06-29 | IBE02CR | SJO → MAD | Jun 29, 22:49 UTC | Jun 30, 08:55 UTC | 10h 5m |
| 2026-06-29 | IBE02SJ | - | Jun 29, 09:54 UTC | Jun 29, 19:44 UTC | 9h 50m |
| 2026-06-28 | IBE0132 | GYE → MAD | Jun 28, 18:49 UTC | Jun 29, 03:25 UTC | 8h 35m |
| 2026-06-27 | IBE0132 | GYE → MAD | Jun 27, 23:50 UTC | Jun 28, 20:14 UTC | 20h 25m |
| 2026-06-27 | IBE0131 | - | Jun 27, 23:34 UTC | Jun 28, 20:14 UTC | 20h 40m |
| 2026-06-27 | IBE0306 | MEX → MAD | Jun 27, 00:55 UTC | Jun 27, 09:44 UTC | 8h 50m |
| 2026-06-26 | IBE0305 | MEX → MAD | Jun 26, 11:30 UTC | Jun 26, 22:34 UTC | 11h 5m |
| 2026-06-25 | IBE0244 | - | Jun 25, 18:15 UTC | Jun 26, 08:54 UTC | 14h 40m |
| 2026-06-25 | IBE02SJ | MAD → SJO | Jun 25, 10:20 UTC | Jun 26, 08:54 UTC | 22h 35m |
| 2026-06-23 | IBE0263 | MAD → MAD | Jun 23, 14:55 UTC | Jun 24, 09:05 UTC | 18h 10m |
| 2026-06-23 | IBE0222 | - | Jun 23, 02:45 UTC | Jun 23, 12:25 UTC | 9h 40m |
| 2026-06-23 | IBE0222 | - | Jun 23, 00:04 UTC | Jun 23, 00:19 UTC | 15m |
| 2026-06-22 | IBE0221 | AGP → MAD | Jun 22, 11:35 UTC | Jun 22, 22:15 UTC | 10h 40m |
| 2026-06-22 | IBE03PB | SJU → MAD | Jun 22, 00:44 UTC | Jun 22, 08:19 UTC | 7h 35m |
| 2026-06-21 | IBE03AE | MAD → SJU | Jun 21, 14:34 UTC | Jun 21, 22:24 UTC | 7h 50m |
| 2026-06-21 | IBE0306 | MEX → MAD | Jun 21, 00:59 UTC | Jun 21, 10:25 UTC | 9h 25m |
| 2026-06-20 | IBE0305 | MEX → MAD | Jun 20, 11:49 UTC | Jun 20, 22:59 UTC | 11h 10m |
| 2026-06-20 | IBE03PB | - | Jun 20, 00:54 UTC | Jun 20, 08:25 UTC | 7h 30m |
| 2026-06-19 | IBE03AE | MAD → SJU | Jun 19, 14:34 UTC | Jun 19, 22:55 UTC | 8h 20m |
| 2026-06-19 | IBE0170 | - | Jun 19, 01:59 UTC | Jun 19, 12:19 UTC | 10h 20m |
| 2026-06-18 | IBE0169 | XRY → MAD | Jun 18, 10:15 UTC | Jun 18, 20:50 UTC | 10h 35m |
| 2026-06-17 | IBE0132 | GYE → MAD | Jun 17, 08:10 UTC | Jun 18, 03:20 UTC | 19h 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-MNL page for operator, model, and routing details .