sensors Mode-S transponder
3455C1
ICAO 24-bit transponder address · allocated to Spain
Currently assigned to EC-MSY · AIRBUS A-330-200
- Hex
- 3455C1
- Octal
- 15052701
- Decimal
- 3,429,825
- Country
- ES
- Tail
- EC-MSY
- Type
- A332
- Flights observed
- 183
- Distinct callsigns
- 20
- Country
- ES
- Last broadcast
- 2h ago
Current position
Country allocation
The ICAO 24-bit address 3455C1 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 | - | 26 | 2026-07-12 |
| IBE0221 | - | 16 | 2026-07-11 |
| IBE0170 | - | 10 | 2026-06-27 |
| IBE0169 | Iberia Airlines | 8 | 2026-06-26 |
| IBE0124 | Iberia Airlines | 7 | 2026-05-19 |
| IBE0121 | Iberia Airlines | 6 | 2026-05-18 |
| IBE03TM | - | 5 | 2026-07-10 |
| IBE03AE | Iberia Airlines | 5 | 2026-06-20 |
| IBE02CR | Iberia Airlines | 5 | 2026-05-30 |
| IBE0244 | Iberia Airlines | 5 | 2026-04-22 |
| IBE0126 | Iberia Airlines | 5 | 2026-05-17 |
| IBE03TH | - | 4 | 2026-07-10 |
| IBE0356 | - | 4 | 2026-07-05 |
| IBE0355 | - | 4 | 2026-07-04 |
| IBE0339 | - | 4 | 2026-06-15 |
| IBE06YG | Iberia Airlines | 3 | 2026-04-19 |
| IBE06BB | Iberia Airlines | 3 | 2026-04-19 |
| IBE03PB | - | 3 | 2026-06-21 |
| IBE03GG | - | 3 | 2026-06-16 |
| IBE02SJ | Iberia Airlines | 3 | 2026-05-30 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | IBE5106 | - | Jul 13, 21:20 UTC | Jul 14, 08:45 UTC | 11h 25m |
| 2026-07-13 | IBE5105 | - | Jul 13, 07:10 UTC | Jul 13, 19:45 UTC | 12h 35m |
| 2026-07-12 | IBE0222 | - | Jul 12, 02:55 UTC | Jul 12, 12:45 UTC | 9h 50m |
| 2026-07-12 | IBE0222 | - | Jul 12, 00:05 UTC | Jul 12, 00:35 UTC | 30m |
| 2026-07-11 | IBE0221 | MAD → GUA | Jul 11, 11:55 UTC | Jul 11, 22:25 UTC | 10h 30m |
| 2026-07-10 | IBE03TH | - | Jul 10, 21:55 UTC | Jul 11, 06:30 UTC | 8h 35m |
| 2026-07-10 | IBE03TM | - | Jul 10, 11:00 UTC | Jul 10, 19:45 UTC | 8h 45m |
| 2026-07-09 | IBE0132 | GYE → MAD | Jul 9, 08:20 UTC | Jul 10, 02:55 UTC | 18h 35m |
| 2026-07-09 | IBE0132 | GYE → MAD | Jul 9, 06:20 UTC | Jul 10, 02:55 UTC | 20h 35m |
| 2026-07-09 | IBE0132 | GYE → MAD | Jul 9, 06:10 UTC | Jul 10, 02:55 UTC | 20h 45m |
| 2026-07-08 | IBE0131 | - | Jul 8, 22:40 UTC | Jul 9, 20:00 UTC | 21h 20m |
| 2026-07-08 | IBE0222 | - | Jul 8, 04:05 UTC | Jul 8, 12:15 UTC | 8h 10m |
| 2026-07-07 | IBE0222 | - | Jul 7, 23:00 UTC | Jul 7, 23:20 UTC | 20m |
| 2026-07-07 | IBE0221 | AGP → MAD | Jul 7, 10:35 UTC | Jul 7, 21:15 UTC | 10h 40m |
| 2026-07-06 | IBE0224 | - | Jul 6, 14:20 UTC | Jul 6, 15:30 UTC | 1h 10m |
| 2026-07-06 | IBE0224 | - | Jul 6, 02:25 UTC | Jul 6, 02:40 UTC | 15m |
| 2026-07-05 | IBE0221 | AGP → MAD | Jul 5, 14:40 UTC | Jul 6, 00:50 UTC | 10h 10m |
| 2026-07-05 | IBE0356 | - | Jul 5, 01:25 UTC | Jul 5, 12:10 UTC | 10h 45m |
| 2026-07-04 | IBE0355 | - | Jul 4, 11:00 UTC | Jul 4, 22:40 UTC | 11h 40m |
| 2026-07-03 | IBE1492 | - | Jul 3, 22:50 UTC | Jul 4, 06:30 UTC | 7h 40m |
| 2026-07-03 | IBE1491 | MAD → CPH | Jul 3, 06:15 UTC | Jul 3, 20:15 UTC | 14h 0m |
| 2026-07-02 | IBE07GF | - | Jul 2, 18:10 UTC | Jul 2, 20:00 UTC | 1h 50m |
| 2026-07-02 | IBE07MM | MAD → LHR | Jul 2, 14:15 UTC | Jul 2, 16:05 UTC | 1h 50m |
| 2026-07-01 | IBE0258 | PTY → MAD | Jul 1, 21:25 UTC | Jul 2, 12:20 UTC | 14h 55m |
| 2026-07-01 | IBE0257 | - | Jul 1, 14:25 UTC | Jul 2, 12:15 UTC | 21h 50m |
| 2026-07-01 | IBE03LW | - | Jul 1, 02:15 UTC | Jul 1, 10:40 UTC | 8h 25m |
| 2026-06-30 | IBE03GR | MAD → MIA | Jun 30, 15:05 UTC | Jun 30, 23:55 UTC | 8h 50m |
| 2026-06-30 | IBE0222 | - | Jun 30, 02:20 UTC | Jun 30, 12:00 UTC | 9h 40m |
| 2026-06-29 | IBE0222 | - | Jun 29, 23:05 UTC | Jun 29, 23:25 UTC | 20m |
| 2026-06-29 | IBE0221 | AGP → MAD | Jun 29, 10:55 UTC | Jun 29, 21:30 UTC | 10h 35m |
| 2026-06-28 | IBE0046 | SJO → MAD | Jun 28, 07:09 UTC | Jun 28, 23:25 UTC | 16h 15m |
| 2026-06-27 | IBE0045 | - | Jun 27, 18:20 UTC | Jun 28, 16:19 UTC | 22h 0m |
| 2026-06-27 | IBE0045 | - | Jun 27, 18:04 UTC | Jun 28, 07:29 UTC | 13h 25m |
| 2026-06-27 | IBE0170 | - | Jun 27, 03:25 UTC | Jun 27, 13:55 UTC | 10h 30m |
| 2026-06-26 | IBE0169 | XRY → MAD | Jun 26, 23:30 UTC | Jun 26, 23:55 UTC | 25m |
| 2026-06-26 | IBE0169 | XRY → MAD | Jun 26, 11:40 UTC | Jun 26, 22:34 UTC | 10h 55m |
| 2026-06-24 | IBE0170 | - | Jun 24, 19:20 UTC | Jun 25, 12:35 UTC | 17h 15m |
| 2026-06-24 | IBE0170 | - | Jun 24, 14:20 UTC | Jun 25, 12:35 UTC | 22h 15m |
| 2026-06-24 | IBE0170 | - | Jun 24, 14:09 UTC | Jun 25, 12:15 UTC | 22h 5m |
| 2026-06-24 | IBE0169 | XRY → MAD | Jun 24, 10:39 UTC | Jun 25, 10:15 UTC | 23h 35m |
| 2026-06-23 | IBE3268 | - | Jun 23, 17:15 UTC | Jun 24, 03:00 UTC | 9h 45m |
| 2026-06-22 | IBE3267 | - | Jun 22, 22:40 UTC | Jun 23, 08:30 UTC | 9h 50m |
| 2026-06-22 | IBE0222 | - | Jun 22, 02:19 UTC | Jun 22, 11:50 UTC | 9h 30m |
| 2026-06-22 | IBE0222 | - | Jun 22, 02:00 UTC | Jun 22, 02:10 UTC | 10m |
| 2026-06-21 | IBE0222 | - | Jun 21, 23:14 UTC | Jun 21, 23:30 UTC | 15m |
| 2026-06-21 | IBE0221 | AGP → MAD | Jun 21, 10:40 UTC | Jun 21, 21:34 UTC | 10h 55m |
| 2026-06-21 | IBE03PB | - | Jun 21, 00:49 UTC | Jun 21, 08:25 UTC | 7h 35m |
| 2026-06-20 | IBE03AE | MAD → SJU | Jun 20, 22:20 UTC | Jun 20, 22:39 UTC | 20m |
| 2026-06-20 | IBE03AE | MAD → SJU | Jun 20, 14:35 UTC | Jun 20, 15:54 UTC | 1h 20m |
| 2026-06-20 | IBE03HT | DFW → MAD | Jun 20, 03:44 UTC | Jun 20, 12:19 UTC | 8h 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-MSY page for operator, model, and routing details .