sensors Mode-S transponder
4CA4B0
ICAO 24-bit transponder address · allocated to Ireland
- Hex
- 4CA4B0
- Octal
- 23122260
- Decimal
- 5,022,896
- Country
- IE
- Flights observed
- 80
- Distinct callsigns
- 20
- Country
- IE
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address 4CA4B0 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 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| ITY673 | ITA Airways | 8 | 2026-04-26 |
| ITY679 | ITA Airways | 7 | 2026-05-03 |
| ITY675 | ITA Airways | 7 | 2026-04-29 |
| ITY672 | ITA Airways | 7 | 2026-04-25 |
| ITY6KC | ITA Airways | 6 | 2026-05-18 |
| ITY678 | ITA Airways | 6 | 2026-05-03 |
| ITY674 | ITA Airways | 4 | 2026-04-28 |
| ITY615 | ITA Airways | 4 | 2026-05-12 |
| ITY610 | ITA Airways | 4 | 2026-05-17 |
| ITY651 | ITA Airways | 3 | 2026-05-20 |
| ITY650 | ITA Airways | 3 | 2026-05-20 |
| ITY614 | ITA Airways | 3 | 2026-05-12 |
| ITY603 | ITA Airways | 3 | 2026-05-28 |
| ITY602 | ITA Airways | 3 | 2026-05-28 |
| ITY619 | ITA Airways | 2 | 2026-05-29 |
| ITY618 | ITA Airways | 2 | 2026-05-29 |
| EIX04N | - | 2 | 2026-05-19 |
| ITY641 | ITA Airways | 1 | 2026-05-22 |
| ITY640 | ITA Airways | 1 | 2026-05-22 |
| ITY629 | ITA Airways | 1 | 2026-05-02 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | ITY619 | IAD → FCO | May 29, 20:45 UTC | May 30, 04:00 UTC | 7h 15m |
| 2026-05-29 | ITY618 | FCO → IAD | May 29, 09:05 UTC | May 29, 18:15 UTC | 9h 10m |
| 2026-05-28 | ITY603 | JFK → FCO | May 28, 22:35 UTC | May 29, 06:30 UTC | 7h 55m |
| 2026-05-28 | ITY602 | FCO → JFK | May 28, 08:10 UTC | May 28, 16:35 UTC | 8h 25m |
| 2026-05-22 | ITY641 | SFO → FCO | May 22, 22:35 UTC | May 23, 10:10 UTC | 11h 35m |
| 2026-05-22 | ITY640 | FCO → SFO | May 22, 07:25 UTC | May 22, 19:35 UTC | 12h 10m |
| 2026-05-21 | ITY609 | JFK → FCO | May 21, 21:20 UTC | May 22, 04:50 UTC | 7h 30m |
| 2026-05-21 | ITY608 | FCO → JFK | May 21, 08:30 UTC | May 21, 17:30 UTC | 9h 0m |
| 2026-05-20 | ITY651 | YYZ → FCO | May 20, 21:10 UTC | May 21, 05:10 UTC | 8h 0m |
| 2026-05-20 | ITY650 | FCO → YYZ | May 20, 08:20 UTC | May 20, 18:25 UTC | 10h 5m |
| 2026-05-19 | ITY619 | IAD → FCO | May 19, 20:45 UTC | May 20, 05:05 UTC | 8h 21m |
| 2026-05-19 | EIX04N | - | May 19, 18:25 UTC | May 19, 18:45 UTC | 20m |
| 2026-05-19 | EIX04N | BXO → IAD | May 19, 15:05 UTC | May 19, 18:10 UTC | 3h 5m |
| 2026-05-19 | ITY618 | FCO → IAD | May 19, 08:55 UTC | May 19, 12:00 UTC | 3h 5m |
| 2026-05-18 | ITY6KC | JFK → FCO | May 18, 02:50 UTC | May 18, 10:15 UTC | 7h 25m |
| 2026-05-18 | ITY6KC | JFK → FCO | May 18, 01:35 UTC | May 18, 02:45 UTC | 1h 10m |
| 2026-05-17 | ITY610 | FCO → JFK | May 17, 13:35 UTC | May 17, 23:05 UTC | 9h 30m |
| 2026-05-16 | ITY6KC | JFK → FCO | May 16, 01:45 UTC | May 16, 10:35 UTC | 8h 51m |
| 2026-05-15 | ITY610 | FCO → JFK | May 15, 14:05 UTC | May 15, 23:10 UTC | 9h 4m |
| 2026-05-15 | ITY6KC | JFK → FCO | May 15, 02:30 UTC | May 15, 11:05 UTC | 8h 35m |
| 2026-05-14 | ITY610 | FCO → JFK | May 14, 14:20 UTC | May 14, 23:55 UTC | 9h 35m |
| 2026-05-14 | ITY6KC | JFK → FCO | May 14, 07:15 UTC | May 14, 11:05 UTC | 3h 50m |
| 2026-05-14 | ITY6KC | JFK → FCO | May 14, 02:45 UTC | May 14, 04:05 UTC | 1h 20m |
| 2026-05-13 | ITY610 | FCO → JFK | May 13, 13:31 UTC | May 13, 23:40 UTC | 10h 10m |
| 2026-05-12 | ITY615 | BOS → FCO | May 12, 21:25 UTC | May 13, 05:25 UTC | 8h 0m |
| 2026-05-12 | ITY614 | FCO → BOS | May 12, 09:25 UTC | May 12, 18:45 UTC | 9h 20m |
| 2026-05-12 | ITY603 | JFK → FCO | May 12, 03:00 UTC | May 12, 06:40 UTC | 3h 40m |
| 2026-05-11 | ITY602 | FCO → JFK | May 11, 07:50 UTC | May 11, 17:35 UTC | 9h 45m |
| 2026-05-11 | ITY615 | BOS → FCO | May 11, 01:30 UTC | May 11, 05:30 UTC | 4h 0m |
| 2026-05-10 | ITY615 | BOS → FCO | May 10, 21:30 UTC | May 10, 22:30 UTC | 1h 0m |
| 2026-05-10 | ITY614 | FCO → BOS | May 10, 08:54 UTC | May 10, 18:05 UTC | 9h 10m |
| 2026-05-09 | ITY651 | YYZ → FCO | May 9, 21:14 UTC | May 10, 05:45 UTC | 8h 30m |
| 2026-05-09 | ITY650 | FCO → YYZ | May 9, 08:40 UTC | May 9, 18:05 UTC | 9h 25m |
| 2026-05-07 | ITY603 | JFK → FCO | May 7, 22:15 UTC | May 8, 06:14 UTC | 8h 0m |
| 2026-05-07 | ITY602 | FCO → JFK | May 7, 08:05 UTC | May 7, 17:15 UTC | 9h 10m |
| 2026-05-06 | ITY615 | BOS → FCO | May 6, 21:15 UTC | May 7, 04:50 UTC | 7h 35m |
| 2026-05-06 | ITY614 | FCO → BOS | May 6, 08:50 UTC | May 6, 17:05 UTC | 8h 15m |
| 2026-05-03 | ITY679 | GRU → FCO | May 3, 22:39 UTC | May 4, 09:05 UTC | 10h 25m |
| 2026-05-03 | ITY678 | FCO → GRU | May 3, 08:30 UTC | May 3, 20:25 UTC | 11h 55m |
| 2026-05-02 | ITY629 | ORD → FCO | May 2, 20:35 UTC | May 3, 05:40 UTC | 9h 4m |
| 2026-05-02 | ITY628 | FCO → ORD | May 2, 08:00 UTC | May 2, 17:45 UTC | 9h 45m |
| 2026-04-30 | ITY679 | GRU → FCO | Apr 30, 22:15 UTC | May 1, 09:05 UTC | 10h 50m |
| 2026-04-30 | ITY678 | FCO → GRU | Apr 30, 08:20 UTC | Apr 30, 20:05 UTC | 11h 45m |
| 2026-04-29 | ITY675 | GRU → FCO | Apr 29, 17:55 UTC | Apr 30, 04:35 UTC | 10h 39m |
| 2026-04-28 | ITY674 | FCO → GRU | Apr 28, 20:20 UTC | Apr 29, 07:59 UTC | 11h 40m |
| 2026-04-27 | ITY679 | GRU → FCO | Apr 27, 23:00 UTC | Apr 28, 09:40 UTC | 10h 40m |
| 2026-04-27 | ITY678 | FCO → GRU | Apr 27, 08:15 UTC | Apr 27, 19:45 UTC | 11h 30m |
| 2026-04-26 | ITY673 | GIG → FCO | Apr 26, 17:35 UTC | Apr 27, 04:00 UTC | 10h 25m |
| 2026-04-25 | ITY672 | FCO → GIG | Apr 25, 20:35 UTC | Apr 26, 07:45 UTC | 11h 10m |
| 2026-04-24 | ITY679 | GRU → FCO | Apr 24, 22:25 UTC | Apr 25, 09:25 UTC | 11h 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.