sensors Mode-S transponder
4CAD46
ICAO 24-bit transponder address · allocated to Ireland
Currently assigned to EI-IFC · AIRBUS A-350-900
- Hex
- 4CAD46
- Octal
- 23126506
- Decimal
- 5,025,094
- Country
- IE
- Tail
- EI-IFC
- Type
- A359
- Flights observed
- 85
- Distinct callsigns
- 8
- Country
- IE
- Last broadcast
- 5h ago
Last known position
Country allocation
The ICAO 24-bit address 4CAD46 falls within the block assigned to Ireland (IE) by ICAO Annex 10, Volume III. Every aircraft registered in Ireland 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 8 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| ITY793 | ITA Airways | 20 | 2026-05-29 |
| ITY680 | ITA Airways | 20 | 2026-05-29 |
| ITY681 | ITA Airways | 18 | 2026-05-26 |
| ITY792 | ITA Airways | 17 | 2026-05-28 |
| ITY621 | ITA Airways | 4 | 2026-05-27 |
| ITY620 | ITA Airways | 4 | 2026-05-27 |
| ITY683 | ITA Airways | 1 | 2026-05-02 |
| ITY682 | ITA Airways | 1 | 2026-05-01 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | ITY680 | FCO → EZE | May 29, 21:55 UTC | May 30, 00:15 UTC | 2h 20m |
| 2026-05-29 | ITY793 | HND → FCO | May 29, 04:40 UTC | May 29, 19:05 UTC | 14h 25m |
| 2026-05-28 | ITY792 | FCO → HND | May 28, 13:35 UTC | May 29, 00:55 UTC | 11h 20m |
| 2026-05-27 | ITY621 | LAX → FCO | May 27, 22:30 UTC | May 28, 09:45 UTC | 11h 15m |
| 2026-05-27 | ITY620 | FCO → LAX | May 27, 08:15 UTC | May 27, 20:20 UTC | 12h 5m |
| 2026-05-26 | ITY681 | EZE → FCO | May 26, 15:54 UTC | May 27, 04:14 UTC | 12h 20m |
| 2026-05-25 | ITY680 | FCO → EZE | May 25, 20:50 UTC | May 26, 10:20 UTC | 13h 30m |
| 2026-05-25 | ITY793 | HND → FCO | May 25, 04:10 UTC | May 25, 17:35 UTC | 13h 25m |
| 2026-05-24 | ITY792 | FCO → HND | May 24, 13:35 UTC | May 24, 23:46 UTC | 10h 11m |
| 2026-05-23 | ITY793 | HND → FCO | May 23, 04:00 UTC | May 23, 17:40 UTC | 13h 40m |
| 2026-05-22 | ITY792 | FCO → HND | May 22, 13:20 UTC | May 23, 01:20 UTC | 12h 0m |
| 2026-05-21 | ITY621 | LAX → FCO | May 21, 22:20 UTC | May 22, 09:35 UTC | 11h 15m |
| 2026-05-21 | ITY620 | FCO → LAX | May 21, 08:10 UTC | May 21, 20:00 UTC | 11h 50m |
| 2026-05-20 | ITY681 | EZE → FCO | May 20, 15:50 UTC | May 21, 04:05 UTC | 12h 15m |
| 2026-05-19 | ITY680 | FCO → EZE | May 19, 21:00 UTC | May 20, 10:25 UTC | 13h 26m |
| 2026-05-19 | ITY793 | HND → FCO | May 19, 04:05 UTC | May 19, 18:05 UTC | 14h 0m |
| 2026-05-18 | ITY792 | FCO → HND | May 18, 13:20 UTC | May 19, 01:15 UTC | 11h 54m |
| 2026-05-17 | ITY681 | EZE → FCO | May 17, 15:50 UTC | May 18, 03:45 UTC | 11h 55m |
| 2026-05-16 | ITY680 | FCO → EZE | May 16, 21:10 UTC | May 17, 11:01 UTC | 13h 50m |
| 2026-05-16 | ITY793 | HND → FCO | May 16, 03:55 UTC | May 16, 17:30 UTC | 13h 36m |
| 2026-05-15 | ITY792 | FCO → HND | May 15, 13:30 UTC | May 16, 01:45 UTC | 12h 14m |
| 2026-05-14 | ITY681 | EZE → FCO | May 14, 15:55 UTC | May 15, 03:45 UTC | 11h 50m |
| 2026-05-13 | ITY680 | FCO → EZE | May 13, 21:20 UTC | May 14, 11:15 UTC | 13h 55m |
| 2026-05-13 | ITY793 | HND → FCO | May 13, 03:50 UTC | May 13, 17:40 UTC | 13h 50m |
| 2026-05-12 | ITY792 | FCO → HND | May 12, 13:15 UTC | May 13, 01:15 UTC | 12h 0m |
| 2026-05-10 | ITY681 | EZE → FCO | May 10, 15:55 UTC | May 11, 03:45 UTC | 11h 50m |
| 2026-05-09 | ITY680 | FCO → EZE | May 9, 21:05 UTC | May 10, 10:40 UTC | 13h 35m |
| 2026-05-09 | ITY793 | HND → FCO | May 9, 04:00 UTC | May 9, 18:15 UTC | 14h 15m |
| 2026-05-08 | ITY792 | FCO → HND | May 8, 13:15 UTC | May 9, 00:50 UTC | 11h 35m |
| 2026-05-07 | ITY621 | LAX → FCO | May 7, 22:20 UTC | May 8, 09:59 UTC | 11h 40m |
| 2026-05-07 | ITY620 | FCO → LAX | May 7, 07:55 UTC | May 7, 19:35 UTC | 11h 40m |
| 2026-05-06 | ITY681 | EZE → FCO | May 6, 15:40 UTC | May 7, 03:15 UTC | 11h 34m |
| 2026-05-05 | ITY680 | FCO → EZE | May 5, 22:01 UTC | May 6, 12:10 UTC | 14h 10m |
| 2026-05-05 | ITY793 | HND → FCO | May 5, 04:15 UTC | May 5, 18:20 UTC | 14h 5m |
| 2026-05-04 | ITY792 | FCO → HND | May 4, 13:20 UTC | May 5, 01:20 UTC | 12h 1m |
| 2026-05-03 | ITY681 | EZE → FCO | May 3, 15:55 UTC | May 4, 03:54 UTC | 12h 0m |
| 2026-05-02 | ITY680 | FCO → EZE | May 2, 20:40 UTC | May 3, 10:05 UTC | 13h 24m |
| 2026-05-02 | ITY683 | EZE → FCO | May 2, 04:20 UTC | May 2, 16:35 UTC | 12h 15m |
| 2026-05-01 | ITY682 | FCO → EZE | May 1, 12:25 UTC | May 2, 02:30 UTC | 14h 5m |
| 2026-04-26 | ITY793 | HND → FCO | Apr 26, 04:05 UTC | Apr 26, 18:30 UTC | 14h 25m |
| 2026-04-25 | ITY792 | FCO → HND | Apr 25, 13:10 UTC | Apr 26, 00:50 UTC | 11h 40m |
| 2026-04-24 | ITY621 | LAX → FCO | Apr 24, 22:25 UTC | Apr 25, 09:35 UTC | 11h 10m |
| 2026-04-24 | ITY620 | FCO → LAX | Apr 24, 08:00 UTC | Apr 24, 19:45 UTC | 11h 45m |
| 2026-04-23 | ITY681 | EZE → FCO | Apr 23, 15:45 UTC | Apr 24, 03:45 UTC | 12h 0m |
| 2026-04-22 | ITY680 | FCO → EZE | Apr 22, 20:55 UTC | Apr 23, 10:30 UTC | 13h 35m |
| 2026-04-22 | ITY793 | HND → FCO | Apr 22, 04:10 UTC | Apr 22, 18:35 UTC | 14h 25m |
| 2026-04-21 | ITY792 | FCO → HND | Apr 21, 13:20 UTC | Apr 22, 01:00 UTC | 11h 40m |
| 2026-04-20 | ITY681 | EZE → FCO | Apr 20, 15:55 UTC | Apr 21, 03:50 UTC | 11h 55m |
| 2026-04-19 | ITY680 | FCO → EZE | Apr 19, 21:05 UTC | Apr 20, 10:35 UTC | 13h 30m |
| 2026-04-19 | ITY793 | HND → FCO | Apr 19, 04:10 UTC | Apr 19, 18:10 UTC | 14h 0m |
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 EI-IFC page for operator, model, and routing details .