sensors Mode-S transponder
34520B
ICAO 24-bit transponder address · allocated to Spain
Currently assigned to EC-MLB · AIRBUS A-330-200
- Hex
- 34520B
- Octal
- 15051013
- Decimal
- 3,428,875
- Country
- ES
- Tail
- EC-MLB
- Type
- A332
- Flights observed
- 140
- Distinct callsigns
- 20
- Country
- ES
- Last broadcast
- 50m ago
Last known position
Country allocation
The ICAO 24-bit address 34520B 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 | - | 13 | 2026-06-29 |
| IBE0258 | - | 11 | 2026-07-08 |
| IBE0257 | Iberia Airlines | 7 | 2026-06-17 |
| IBE03AE | Iberia Airlines | 6 | 2026-06-30 |
| IBE02SJ | - | 6 | 2026-07-13 |
| IBE0169 | Iberia Airlines | 6 | 2026-06-21 |
| IBE02CR | - | 5 | 2026-07-13 |
| IBE0244 | Iberia Airlines | 5 | 2026-04-26 |
| IBE0221 | Iberia Airlines | 5 | 2026-06-28 |
| IBE0170 | - | 5 | 2026-06-21 |
| IBE0132 | Iberia Airlines | 5 | 2026-07-05 |
| IBE03TM | - | 4 | 2026-07-12 |
| IBE03TH | - | 4 | 2026-07-12 |
| IBE03SY | - | 4 | 2026-04-15 |
| IBE03PB | - | 4 | 2026-07-01 |
| IBE03GG | - | 3 | 2026-06-30 |
| IBE0339 | - | 3 | 2026-06-29 |
| IBE0268 | Iberia Airlines | 3 | 2026-04-15 |
| IBE0267 | Iberia Airlines | 3 | 2026-04-14 |
| IBE0131 | - | 3 | 2026-07-04 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | IBE02CR | - | Jul 13, 23:10 UTC | Jul 14, 08:45 UTC | 9h 35m |
| 2026-07-13 | IBE02SJ | - | Jul 13, 20:10 UTC | Jul 13, 21:00 UTC | 50m |
| 2026-07-13 | IBE02SJ | - | Jul 13, 10:05 UTC | Jul 13, 11:20 UTC | 1h 15m |
| 2026-07-12 | IBE03TH | - | Jul 12, 21:20 UTC | Jul 13, 05:25 UTC | 8h 5m |
| 2026-07-12 | IBE03TM | MAD → MIA | Jul 12, 10:01 UTC | Jul 12, 18:45 UTC | 8h 45m |
| 2026-07-11 | IBE0212 | JFK → MAD | Jul 11, 22:25 UTC | Jul 12, 05:10 UTC | 6h 45m |
| 2026-07-11 | IBE02DA | MAD → JFK | Jul 11, 11:50 UTC | Jul 11, 19:35 UTC | 7h 45m |
| 2026-07-10 | IBE5102 | - | Jul 10, 15:40 UTC | Jul 11, 02:55 UTC | 11h 15m |
| 2026-07-10 | IBE5103 | - | Jul 10, 09:10 UTC | Jul 10, 11:05 UTC | 1h 55m |
| 2026-07-09 | IBE5103 | - | Jul 9, 22:20 UTC | Jul 10, 09:05 UTC | 10h 45m |
| 2026-07-08 | IBE0258 | - | Jul 8, 22:55 UTC | Jul 9, 13:00 UTC | 14h 5m |
| 2026-07-08 | IBE0258 | - | Jul 8, 16:50 UTC | Jul 9, 13:00 UTC | 20h 10m |
| 2026-07-08 | IBE0258 | - | Jul 8, 15:20 UTC | Jul 9, 13:00 UTC | 21h 40m |
| 2026-07-08 | IBE0356 | - | Jul 8, 02:10 UTC | Jul 8, 12:25 UTC | 10h 15m |
| 2026-07-07 | IBE0355 | - | Jul 7, 12:15 UTC | Jul 7, 23:55 UTC | 11h 40m |
| 2026-07-06 | IBE02CR | - | Jul 6, 22:55 UTC | Jul 7, 08:40 UTC | 9h 45m |
| 2026-07-06 | IBE02SJ | - | Jul 6, 09:55 UTC | Jul 6, 11:20 UTC | 1h 25m |
| 2026-07-05 | IBE0132 | GYE → MAD | Jul 5, 18:10 UTC | Jul 6, 03:15 UTC | 9h 5m |
| 2026-07-05 | IBE0132 | GYE → MAD | Jul 5, 06:20 UTC | Jul 6, 03:15 UTC | 20h 55m |
| 2026-07-04 | IBE0131 | - | Jul 4, 22:50 UTC | Jul 5, 18:10 UTC | 19h 20m |
| 2026-07-04 | IBE0306 | - | Jul 4, 00:55 UTC | Jul 4, 11:00 UTC | 10h 5m |
| 2026-07-03 | IBE0305 | MAD → MTY | Jul 3, 12:00 UTC | Jul 3, 22:45 UTC | 10h 45m |
| 2026-07-03 | IBE02CR | - | Jul 3, 08:05 UTC | Jul 3, 09:10 UTC | 1h 5m |
| 2026-07-02 | IBE02CR | - | Jul 2, 23:15 UTC | Jul 3, 02:00 UTC | 2h 45m |
| 2026-07-02 | IBE02SJ | - | Jul 2, 09:55 UTC | Jul 2, 19:45 UTC | 9h 50m |
| 2026-07-01 | IBE03PB | - | Jul 1, 00:45 UTC | Jul 1, 08:40 UTC | 7h 55m |
| 2026-06-30 | IBE03AE | MAD → SJU | Jun 30, 14:45 UTC | Jun 30, 22:25 UTC | 7h 40m |
| 2026-06-30 | IBE03GG | MCO → MAD | Jun 30, 02:30 UTC | Jun 30, 10:45 UTC | 8h 15m |
| 2026-06-29 | IBE0339 | MAD → MCO | Jun 29, 15:04 UTC | Jun 30, 00:20 UTC | 9h 15m |
| 2026-06-29 | IBE0222 | - | Jun 29, 02:00 UTC | Jun 29, 11:45 UTC | 9h 45m |
| 2026-06-28 | IBE0222 | - | Jun 28, 22:45 UTC | Jun 28, 23:04 UTC | 20m |
| 2026-06-28 | IBE0221 | AGP → MAD | Jun 28, 10:30 UTC | Jun 28, 21:04 UTC | 10h 35m |
| 2026-06-27 | IBE0124 | - | Jun 27, 17:39 UTC | Jun 28, 03:40 UTC | 10h 0m |
| 2026-06-27 | IBE0124 | - | Jun 27, 08:10 UTC | Jun 28, 03:40 UTC | 19h 30m |
| 2026-06-26 | IBE0123 | MAD → LIM | Jun 26, 22:49 UTC | Jun 27, 17:55 UTC | 19h 5m |
| 2026-06-26 | IBE0123 | MAD → LIM | Jun 26, 22:29 UTC | Jun 27, 17:55 UTC | 19h 25m |
| 2026-06-26 | IBE07GF | - | Jun 26, 18:29 UTC | Jun 26, 20:34 UTC | 2h 5m |
| 2026-06-26 | IBE07MM | MAD → LHR | Jun 26, 14:19 UTC | Jun 26, 16:05 UTC | 1h 45m |
| 2026-06-26 | IBE03PB | SJU → MAD | Jun 26, 00:45 UTC | Jun 26, 08:30 UTC | 7h 45m |
| 2026-06-25 | IBE03AE | MAD → SJU | Jun 25, 14:39 UTC | Jun 25, 22:34 UTC | 7h 55m |
| 2026-06-25 | IBE0222 | - | Jun 25, 10:39 UTC | Jun 25, 11:50 UTC | 1h 10m |
| 2026-06-24 | IBE0222 | - | Jun 24, 23:29 UTC | Jun 24, 23:50 UTC | 20m |
| 2026-06-24 | IBE0221 | AGP → MAD | Jun 24, 11:14 UTC | Jun 24, 21:44 UTC | 10h 30m |
| 2026-06-23 | IBE03GG | MCO → MAD | Jun 23, 02:34 UTC | Jun 23, 10:49 UTC | 8h 15m |
| 2026-06-22 | IBE0339 | MAD → MCO | Jun 22, 15:29 UTC | Jun 23, 00:24 UTC | 8h 55m |
| 2026-06-21 | IBE0170 | - | Jun 21, 19:05 UTC | Jun 22, 12:49 UTC | 17h 45m |
| 2026-06-21 | IBE0170 | - | Jun 21, 13:54 UTC | Jun 22, 12:44 UTC | 22h 50m |
| 2026-06-21 | IBE0169 | XRY → MAD | Jun 21, 10:49 UTC | Jun 22, 10:44 UTC | 23h 55m |
| 2026-06-21 | IBE0169 | XRY → MAD | Jun 21, 10:19 UTC | Jun 22, 03:24 UTC | 17h 5m |
| 2026-06-19 | IBE03PB | - | Jun 19, 00:55 UTC | Jun 19, 08:14 UTC | 7h 20m |
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-MLB page for operator, model, and routing details .