sensors Mode-S transponder
4CACB9
ICAO 24-bit transponder address · allocated to Ireland
Currently assigned to EI-TYG · AIRBUS A-330-900
- Hex
- 4CACB9
- Octal
- 23126271
- Decimal
- 5,024,953
- Country
- IE
- Tail
- EI-TYG
- Type
- A339
- Flights observed
- 90
- Distinct callsigns
- 20
- Country
- IE
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address 4CACB9 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 |
|---|---|---|---|
| ITY674 | ITA Airways | 11 | 2026-05-22 |
| ITY675 | ITA Airways | 7 | 2026-05-23 |
| ITY630 | ITA Airways | 7 | 2026-05-18 |
| ITY678 | ITA Airways | 6 | 2026-05-25 |
| ITY759 | ITA Airways | 5 | 2026-04-17 |
| ITY758 | - | 5 | 2026-04-16 |
| ITY6MO | ITA Airways | 5 | 2026-05-19 |
| ITY641 | ITA Airways | 5 | 2026-05-21 |
| ITY640 | ITA Airways | 5 | 2026-05-21 |
| ITY6KC | ITA Airways | 4 | 2026-05-30 |
| ITY679 | ITA Airways | 4 | 2026-05-25 |
| ITY610 | ITA Airways | 4 | 2026-05-29 |
| ITY673 | ITA Airways | 3 | 2026-04-29 |
| ITY672 | ITA Airways | 2 | 2026-04-27 |
| ITY618 | ITA Airways | 2 | 2026-05-17 |
| ITY603 | ITA Airways | 2 | 2026-05-08 |
| ITY602 | ITA Airways | 2 | 2026-05-08 |
| ITY770 | ITA Airways | 1 | 2026-04-20 |
| ITY769 | ITA Airways | 1 | 2026-04-20 |
| ITY683 | ITA Airways | 1 | 2026-05-20 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | ITY6KC | JFK → FCO | May 30, 01:55 UTC | May 30, 03:35 UTC | 1h 40m |
| 2026-05-29 | ITY610 | FCO → JFK | May 29, 13:35 UTC | May 29, 22:10 UTC | 8h 35m |
| 2026-05-29 | ITY6KC | JFK → FCO | May 29, 01:55 UTC | May 29, 09:45 UTC | 7h 50m |
| 2026-05-28 | ITY610 | FCO → JFK | May 28, 13:45 UTC | May 28, 22:25 UTC | 8h 40m |
| 2026-05-28 | ITY6KC | JFK → FCO | May 28, 01:40 UTC | May 28, 09:35 UTC | 7h 55m |
| 2026-05-27 | ITY610 | FCO → JFK | May 27, 13:30 UTC | May 27, 22:00 UTC | 8h 30m |
| 2026-05-27 | ITY6KC | JFK → FCO | May 27, 01:39 UTC | May 27, 09:40 UTC | 8h 0m |
| 2026-05-26 | ITY610 | FCO → JFK | May 26, 13:45 UTC | May 26, 22:15 UTC | 8h 30m |
| 2026-05-25 | ITY679 | GRU → FCO | May 25, 22:30 UTC | May 26, 09:19 UTC | 10h 50m |
| 2026-05-25 | ITY678 | FCO → GRU | May 25, 08:35 UTC | May 25, 20:24 UTC | 11h 50m |
| 2026-05-24 | ITY651 | YYZ → FCO | May 24, 21:20 UTC | May 25, 05:40 UTC | 8h 20m |
| 2026-05-24 | ITY650 | FCO → YYZ | May 24, 08:50 UTC | May 24, 17:45 UTC | 8h 55m |
| 2026-05-23 | ITY675 | GRU → FCO | May 23, 17:10 UTC | May 24, 04:10 UTC | 11h 1m |
| 2026-05-22 | ITY674 | FCO → GRU | May 22, 20:45 UTC | May 23, 08:35 UTC | 11h 49m |
| 2026-05-21 | ITY641 | SFO → FCO | May 21, 22:50 UTC | May 22, 10:15 UTC | 11h 25m |
| 2026-05-21 | ITY640 | FCO → SFO | May 21, 08:10 UTC | May 21, 20:20 UTC | 12h 10m |
| 2026-05-20 | ITY683 | EZE → FCO | May 20, 04:40 UTC | May 20, 17:30 UTC | 12h 50m |
| 2026-05-19 | ITY682 | FCO → EZE | May 19, 12:15 UTC | May 20, 02:10 UTC | 13h 55m |
| 2026-05-19 | ITY6MO | MIA → FCO | May 19, 00:30 UTC | May 19, 09:55 UTC | 9h 25m |
| 2026-05-18 | ITY630 | FCO → MIA | May 18, 09:55 UTC | May 18, 20:25 UTC | 10h 29m |
| 2026-05-17 | ITY619 | IAD → FCO | May 17, 23:15 UTC | May 18, 07:15 UTC | 8h 0m |
| 2026-05-17 | ITY618 | FCO → IAD | May 17, 18:50 UTC | May 17, 20:40 UTC | 1h 50m |
| 2026-05-17 | ITY618 | FCO → IAD | May 17, 11:10 UTC | May 17, 18:40 UTC | 7h 30m |
| 2026-05-16 | ITY675 | GRU → FCO | May 16, 17:45 UTC | May 17, 04:20 UTC | 10h 35m |
| 2026-05-15 | ITY674 | FCO → GRU | May 15, 21:20 UTC | May 16, 09:31 UTC | 12h 11m |
| 2026-05-15 | ITY6MO | MIA → FCO | May 15, 00:05 UTC | May 15, 09:10 UTC | 9h 5m |
| 2026-05-14 | ITY630 | FCO → MIA | May 14, 09:15 UTC | May 14, 20:15 UTC | 11h 0m |
| 2026-05-13 | ITY675 | GRU → FCO | May 13, 17:25 UTC | May 14, 03:40 UTC | 10h 15m |
| 2026-05-12 | ITY674 | FCO → GRU | May 12, 20:50 UTC | May 13, 09:15 UTC | 12h 25m |
| 2026-05-12 | ITY621 | LAX → FCO | May 12, 07:20 UTC | May 12, 10:00 UTC | 2h 40m |
| 2026-05-11 | ITY620 | FCO → LAX | May 11, 07:55 UTC | May 11, 20:45 UTC | 12h 50m |
| 2026-05-09 | ITY641 | SFO → FCO | May 9, 23:35 UTC | May 10, 11:20 UTC | 11h 45m |
| 2026-05-09 | ITY640 | FCO → SFO | May 9, 08:50 UTC | May 9, 21:09 UTC | 12h 20m |
| 2026-05-08 | ITY603 | JFK → FCO | May 8, 21:55 UTC | May 9, 06:00 UTC | 8h 5m |
| 2026-05-08 | ITY602 | FCO → JFK | May 8, 08:29 UTC | May 8, 17:45 UTC | 9h 15m |
| 2026-05-02 | ITY679 | GRU → FCO | May 2, 22:15 UTC | May 3, 09:00 UTC | 10h 44m |
| 2026-05-02 | ITY678 | FCO → GRU | May 2, 08:05 UTC | May 2, 19:45 UTC | 11h 40m |
| 2026-05-01 | ITY675 | GRU → FCO | May 1, 17:30 UTC | May 2, 04:25 UTC | 10h 55m |
| 2026-04-30 | ITY674 | FCO → GRU | Apr 30, 20:25 UTC | May 1, 08:05 UTC | 11h 40m |
| 2026-04-29 | ITY641 | SFO → FCO | Apr 29, 22:35 UTC | Apr 30, 10:15 UTC | 11h 39m |
| 2026-04-29 | ITY640 | FCO → SFO | Apr 29, 07:50 UTC | Apr 29, 20:00 UTC | 12h 11m |
| 2026-04-29 | ITY673 | GIG → FCO | Apr 29, 02:24 UTC | Apr 29, 04:10 UTC | 1h 45m |
| 2026-04-28 | ITY673 | GIG → FCO | Apr 28, 17:45 UTC | Apr 28, 23:54 UTC | 6h 10m |
| 2026-04-27 | ITY672 | FCO → GIG | Apr 27, 20:35 UTC | Apr 28, 07:55 UTC | 11h 20m |
| 2026-04-26 | ITY641 | SFO → FCO | Apr 26, 22:40 UTC | Apr 27, 09:50 UTC | 11h 10m |
| 2026-04-26 | ITY640 | FCO → SFO | Apr 26, 07:50 UTC | Apr 26, 20:10 UTC | 12h 20m |
| 2026-04-25 | ITY609 | JFK → FCO | Apr 25, 20:40 UTC | Apr 26, 04:40 UTC | 8h 0m |
| 2026-04-25 | ITY608 | FCO → JFK | Apr 25, 08:35 UTC | Apr 25, 17:00 UTC | 8h 25m |
| 2026-04-24 | ITY603 | JFK → FCO | Apr 24, 22:05 UTC | Apr 25, 06:05 UTC | 8h 0m |
| 2026-04-24 | ITY602 | FCO → JFK | Apr 24, 08:20 UTC | Apr 24, 16:55 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 EI-TYG page for operator, model, and routing details .