sensors Mode-S transponder
4CAD48
ICAO 24-bit transponder address · allocated to Ireland
Currently assigned to EI-IFE · AIRBUS A-350-900
- Hex
- 4CAD48
- Octal
- 23126510
- Decimal
- 5,025,096
- Country
- IE
- Tail
- EI-IFE
- Type
- A359
- Flights observed
- 69
- Distinct callsigns
- 14
- Country
- IE
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address 4CAD48 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 14 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| ITY681 | - | 13 | 2026-07-09 |
| ITY680 | - | 12 | 2026-07-08 |
| ITY793 | - | 9 | 2026-07-08 |
| ITY792 | - | 9 | 2026-07-07 |
| ITY620 | - | 9 | 2026-07-10 |
| ITY621 | - | 8 | 2026-07-06 |
| ITY682 | ITA Airways | 2 | 2026-05-30 |
| ITY683 | ITA Airways | 1 | 2026-05-30 |
| ITY679 | ITA Airways | 1 | 2026-06-01 |
| ITY678 | ITA Airways | 1 | 2026-06-01 |
| ITY641 | - | 1 | 2026-06-21 |
| ITY640 | - | 1 | 2026-06-21 |
| ITY609 | - | 1 | 2026-06-27 |
| ITY608 | - | 1 | 2026-06-27 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-10 | ITY620 | - | Jul 10, 09:00 UTC | Jul 10, 20:00 UTC | 11h 0m |
| 2026-07-09 | ITY681 | - | Jul 9, 15:50 UTC | Jul 10, 04:05 UTC | 12h 15m |
| 2026-07-08 | ITY680 | - | Jul 8, 20:50 UTC | Jul 9, 10:05 UTC | 13h 15m |
| 2026-07-08 | ITY793 | HND → FCO | Jul 8, 03:55 UTC | Jul 8, 17:50 UTC | 13h 55m |
| 2026-07-07 | ITY792 | - | Jul 7, 13:25 UTC | Jul 7, 15:20 UTC | 1h 55m |
| 2026-07-06 | ITY621 | - | Jul 6, 22:30 UTC | Jul 7, 09:30 UTC | 11h 0m |
| 2026-07-06 | ITY620 | - | Jul 6, 07:55 UTC | Jul 6, 20:25 UTC | 12h 30m |
| 2026-07-05 | ITY681 | - | Jul 5, 16:05 UTC | Jul 6, 04:05 UTC | 12h 0m |
| 2026-07-04 | ITY680 | - | Jul 4, 21:00 UTC | Jul 5, 10:30 UTC | 13h 30m |
| 2026-07-04 | ITY793 | HND → FCO | Jul 4, 03:45 UTC | Jul 4, 17:20 UTC | 13h 35m |
| 2026-07-03 | ITY792 | - | Jul 3, 13:40 UTC | Jul 4, 01:15 UTC | 11h 35m |
| 2026-07-02 | ITY621 | - | Jul 2, 23:10 UTC | Jul 3, 10:00 UTC | 10h 50m |
| 2026-07-02 | ITY620 | - | Jul 2, 08:50 UTC | Jul 2, 20:50 UTC | 12h 0m |
| 2026-07-01 | ITY681 | - | Jul 1, 16:05 UTC | Jul 2, 04:25 UTC | 12h 20m |
| 2026-06-30 | ITY680 | - | Jun 30, 20:50 UTC | Jul 1, 10:25 UTC | 13h 35m |
| 2026-06-28 | ITY621 | - | Jun 28, 22:39 UTC | Jun 29, 09:34 UTC | 10h 55m |
| 2026-06-28 | ITY620 | - | Jun 28, 07:54 UTC | Jun 28, 19:29 UTC | 11h 35m |
| 2026-06-27 | ITY609 | JFK → FCO | Jun 27, 20:39 UTC | Jun 28, 03:55 UTC | 7h 15m |
| 2026-06-27 | ITY608 | - | Jun 27, 09:00 UTC | Jun 27, 17:25 UTC | 8h 25m |
| 2026-06-26 | ITY681 | - | Jun 26, 16:05 UTC | Jun 27, 04:39 UTC | 12h 35m |
| 2026-06-25 | ITY680 | - | Jun 25, 21:29 UTC | Jun 26, 10:35 UTC | 13h 5m |
| 2026-06-25 | ITY621 | - | Jun 25, 00:09 UTC | Jun 25, 11:30 UTC | 11h 20m |
| 2026-06-24 | ITY620 | - | Jun 24, 09:45 UTC | Jun 24, 21:40 UTC | 11h 55m |
| 2026-06-23 | ITY793 | HND → FCO | Jun 23, 04:09 UTC | Jun 23, 18:10 UTC | 14h 0m |
| 2026-06-22 | ITY792 | - | Jun 22, 14:10 UTC | Jun 23, 01:54 UTC | 11h 45m |
| 2026-06-21 | ITY641 | - | Jun 21, 23:24 UTC | Jun 22, 10:30 UTC | 11h 5m |
| 2026-06-21 | ITY640 | - | Jun 21, 08:40 UTC | Jun 21, 20:45 UTC | 12h 5m |
| 2026-06-21 | ITY681 | - | Jun 21, 03:49 UTC | Jun 21, 04:39 UTC | 50m |
| 2026-06-20 | ITY681 | - | Jun 20, 15:54 UTC | Jun 21, 00:19 UTC | 8h 25m |
| 2026-06-19 | ITY680 | - | Jun 19, 20:49 UTC | Jun 20, 09:49 UTC | 13h 0m |
| 2026-06-19 | ITY793 | HND → FCO | Jun 19, 04:04 UTC | Jun 19, 17:49 UTC | 13h 45m |
| 2026-06-18 | ITY792 | - | Jun 18, 13:30 UTC | Jun 19, 01:19 UTC | 11h 49m |
| 2026-06-17 | ITY621 | LAX → FCO | Jun 17, 22:25 UTC | Jun 18, 09:45 UTC | 11h 20m |
| 2026-06-17 | ITY620 | - | Jun 17, 07:55 UTC | Jun 17, 19:55 UTC | 12h 0m |
| 2026-06-16 | ITY681 | - | Jun 16, 16:10 UTC | Jun 17, 04:10 UTC | 12h 1m |
| 2026-06-15 | ITY680 | - | Jun 15, 20:59 UTC | Jun 16, 10:45 UTC | 13h 45m |
| 2026-06-15 | ITY793 | - | Jun 15, 04:04 UTC | Jun 15, 17:54 UTC | 13h 50m |
| 2026-06-14 | ITY792 | - | Jun 14, 13:20 UTC | Jun 15, 01:04 UTC | 11h 45m |
| 2026-06-13 | ITY621 | - | Jun 13, 23:30 UTC | Jun 14, 10:35 UTC | 11h 5m |
| 2026-06-13 | ITY620 | - | Jun 13, 09:25 UTC | Jun 13, 21:20 UTC | 11h 55m |
| 2026-06-12 | ITY681 | EZE → FCO | Jun 12, 17:40 UTC | Jun 13, 06:15 UTC | 12h 34m |
| 2026-06-11 | ITY680 | - | Jun 11, 21:10 UTC | Jun 12, 15:05 UTC | 17h 56m |
| 2026-06-09 | ITY621 | LAX → FCO | Jun 9, 22:35 UTC | Jun 10, 09:25 UTC | 10h 50m |
| 2026-06-09 | ITY620 | FCO → LAX | Jun 9, 08:00 UTC | Jun 9, 20:40 UTC | 12h 40m |
| 2026-06-08 | ITY681 | EZE → FCO | Jun 8, 16:00 UTC | Jun 9, 04:15 UTC | 12h 15m |
| 2026-06-07 | ITY680 | FCO → EZE | Jun 7, 22:45 UTC | Jun 8, 12:10 UTC | 13h 25m |
| 2026-06-07 | ITY793 | HND → FCO | Jun 7, 04:05 UTC | Jun 7, 14:00 UTC | 9h 55m |
| 2026-06-06 | ITY792 | FCO → HND | Jun 6, 13:34 UTC | Jun 7, 01:15 UTC | 11h 40m |
| 2026-06-05 | ITY621 | LAX → FCO | Jun 5, 22:20 UTC | Jun 6, 09:30 UTC | 11h 10m |
| 2026-06-05 | ITY620 | FCO → LAX | Jun 5, 07:50 UTC | Jun 5, 19:35 UTC | 11h 45m |
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-IFE page for operator, model, and routing details .