sensors Mode-S transponder
34520E
ICAO 24-bit transponder address · allocated to Spain
Currently assigned to EC-MMG · AIRBUS A-330-200
- Hex
- 34520E
- Octal
- 15051016
- Decimal
- 3,428,878
- Country
- ES
- Tail
- EC-MMG
- Type
- A332
- Flights observed
- 182
- Distinct callsigns
- 20
- Country
- ES
- Last broadcast
- 2h ago
Last known position
Country allocation
The ICAO 24-bit address 34520E 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 |
|---|---|---|---|
| IBE0170 | - | 18 | 2026-07-11 |
| IBE0169 | - | 16 | 2026-07-10 |
| IBE0222 | - | 12 | 2026-07-09 |
| IBE02CR | - | 7 | 2026-07-05 |
| IBE0221 | - | 7 | 2026-07-08 |
| IBE0131 | - | 7 | 2026-07-11 |
| IBE0124 | - | 7 | 2026-07-04 |
| IBE02SJ | - | 6 | 2026-07-05 |
| IBE0132 | - | 6 | 2026-07-12 |
| IBE0123 | - | 6 | 2026-07-13 |
| IBE03AE | Iberia Airlines | 5 | 2026-06-23 |
| IBE03PB | - | 4 | 2026-06-24 |
| IBE03CY | Iberia Airlines | 4 | 2026-04-24 |
| IBE0356 | - | 4 | 2026-07-03 |
| IBE0355 | - | 4 | 2026-07-02 |
| IBE0265 | - | 4 | 2026-04-13 |
| IBE5107 | - | 3 | 2026-06-27 |
| IBE03ZB | - | 3 | 2026-07-06 |
| IBE03LW | Iberia Airlines | 3 | 2026-06-10 |
| IBE03GR | Iberia Airlines | 3 | 2026-06-09 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | IBE0123 | - | Jul 13, 22:45 UTC | Jul 14, 09:10 UTC | 10h 25m |
| 2026-07-12 | IBE0132 | - | Jul 12, 08:35 UTC | Jul 13, 02:50 UTC | 18h 15m |
| 2026-07-11 | IBE0131 | - | Jul 11, 23:35 UTC | Jul 12, 19:35 UTC | 20h 0m |
| 2026-07-11 | IBE0131 | - | Jul 11, 22:40 UTC | Jul 12, 19:35 UTC | 20h 55m |
| 2026-07-11 | IBE0170 | - | Jul 11, 02:30 UTC | Jul 11, 13:15 UTC | 10h 45m |
| 2026-07-10 | IBE0169 | - | Jul 10, 11:15 UTC | Jul 10, 23:45 UTC | 12h 30m |
| 2026-07-09 | IBE0222 | - | Jul 9, 11:10 UTC | Jul 9, 12:20 UTC | 1h 10m |
| 2026-07-08 | IBE0222 | - | Jul 8, 23:50 UTC | Jul 9, 00:10 UTC | 20m |
| 2026-07-08 | IBE0221 | MAD → GUA | Jul 8, 11:35 UTC | Jul 8, 22:15 UTC | 10h 40m |
| 2026-07-07 | IBE0263 | - | Jul 7, 14:50 UTC | Jul 8, 09:05 UTC | 18h 15m |
| 2026-07-07 | IBE0352 | - | Jul 7, 00:55 UTC | Jul 7, 12:00 UTC | 11h 5m |
| 2026-07-06 | IBE03ZB | - | Jul 6, 11:00 UTC | Jul 6, 22:35 UTC | 11h 35m |
| 2026-07-05 | IBE02CR | - | Jul 5, 22:35 UTC | Jul 6, 08:30 UTC | 9h 55m |
| 2026-07-05 | IBE02SJ | - | Jul 5, 10:15 UTC | Jul 5, 20:10 UTC | 9h 55m |
| 2026-07-04 | IBE0124 | - | Jul 4, 17:30 UTC | Jul 5, 03:25 UTC | 9h 55m |
| 2026-07-03 | IBE0123 | - | Jul 3, 22:25 UTC | Jul 4, 09:45 UTC | 11h 20m |
| 2026-07-03 | IBE0356 | SFO → MAD | Jul 3, 01:25 UTC | Jul 3, 12:15 UTC | 10h 50m |
| 2026-07-02 | IBE0355 | MAD → SFO | Jul 2, 11:15 UTC | Jul 2, 23:05 UTC | 11h 50m |
| 2026-07-01 | IBE02CR | - | Jul 1, 22:40 UTC | Jul 2, 08:55 UTC | 10h 15m |
| 2026-07-01 | IBE02SJ | - | Jul 1, 09:55 UTC | Jul 1, 19:55 UTC | 10h 0m |
| 2026-06-30 | IBE0124 | - | Jun 30, 17:15 UTC | Jul 1, 03:25 UTC | 10h 10m |
| 2026-06-29 | IBE0124 | - | Jun 29, 23:34 UTC | Jun 30, 18:05 UTC | 18h 31m |
| 2026-06-29 | IBE0123 | MAD → LIM | Jun 29, 22:24 UTC | Jun 30, 18:05 UTC | 19h 41m |
| 2026-06-29 | IBE5110 | - | Jun 29, 06:29 UTC | Jun 29, 18:10 UTC | 11h 40m |
| 2026-06-28 | IBE5109 | MAD → EZE | Jun 28, 16:19 UTC | Jun 29, 04:45 UTC | 12h 25m |
| 2026-06-28 | IBE5108 | - | Jun 28, 00:30 UTC | Jun 28, 12:15 UTC | 11h 45m |
| 2026-06-27 | IBE5107 | MAD → EZE | Jun 27, 10:19 UTC | Jun 27, 22:25 UTC | 12h 5m |
| 2026-06-26 | IBE5102 | - | Jun 26, 15:25 UTC | Jun 27, 03:09 UTC | 11h 45m |
| 2026-06-25 | IBE5103 | MAD → EZE | Jun 25, 22:39 UTC | Jun 26, 11:05 UTC | 12h 25m |
| 2026-06-25 | IBE0352 | LAX → MAD | Jun 25, 03:10 UTC | Jun 25, 13:24 UTC | 10h 15m |
| 2026-06-24 | IBE03ZB | MAD → LAX | Jun 24, 12:44 UTC | Jun 25, 00:24 UTC | 11h 40m |
| 2026-06-24 | IBE03PB | - | Jun 24, 01:39 UTC | Jun 24, 09:19 UTC | 7h 40m |
| 2026-06-23 | IBE03AE | MAD → SJU | Jun 23, 15:15 UTC | Jun 23, 22:55 UTC | 7h 40m |
| 2026-06-22 | IBE0170 | - | Jun 22, 17:50 UTC | Jun 23, 12:45 UTC | 18h 55m |
| 2026-06-22 | IBE0170 | - | Jun 22, 11:35 UTC | Jun 23, 11:29 UTC | 23h 55m |
| 2026-06-22 | IBE0169 | XRY → MAD | Jun 22, 10:30 UTC | Jun 23, 05:45 UTC | 19h 15m |
| 2026-06-21 | IBE5108 | EZE → MAD | Jun 21, 02:50 UTC | Jun 21, 14:30 UTC | 11h 40m |
| 2026-06-20 | IBE5107 | - | Jun 20, 21:34 UTC | Jun 20, 22:25 UTC | 50m |
| 2026-06-20 | IBE5107 | - | Jun 20, 10:25 UTC | Jun 20, 20:49 UTC | 10h 25m |
| 2026-06-19 | IBE0124 | - | Jun 19, 08:50 UTC | Jun 20, 03:19 UTC | 18h 30m |
| 2026-06-18 | IBE0123 | MAD → LIM | Jun 18, 23:35 UTC | Jun 19, 20:04 UTC | 20h 29m |
| 2026-06-18 | IBE0123 | MAD → LIM | Jun 18, 23:15 UTC | Jun 19, 20:04 UTC | 20h 49m |
| 2026-06-18 | IBE07GF | - | Jun 18, 18:15 UTC | Jun 18, 20:05 UTC | 1h 50m |
| 2026-06-18 | IBE07MM | MAD → MAD | Jun 18, 14:45 UTC | Jun 18, 16:25 UTC | 1h 40m |
| 2026-06-17 | IBE0352 | - | Jun 17, 04:20 UTC | Jun 17, 15:00 UTC | 10h 40m |
| 2026-06-16 | IBE03ZB | - | Jun 16, 14:25 UTC | Jun 17, 01:55 UTC | 11h 31m |
| 2026-06-16 | IBE0224 | - | Jun 16, 10:30 UTC | Jun 16, 11:40 UTC | 1h 10m |
| 2026-06-15 | IBE0224 | - | Jun 15, 23:09 UTC | Jun 15, 23:30 UTC | 20m |
| 2026-06-15 | IBE0221 | AGP → MAD | Jun 15, 11:00 UTC | Jun 15, 21:35 UTC | 10h 35m |
| 2026-06-14 | IBE0676 | MXP → MAD | Jun 14, 18:00 UTC | Jun 14, 19:50 UTC | 1h 50m |
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-MMG page for operator, model, and routing details .