sensors Mode-S transponder
4CADC6
ICAO 24-bit transponder address · allocated to Ireland
Currently assigned to EI-HJN · AIRBUS A-330-900
- Hex
- 4CADC6
- Octal
- 23126706
- Decimal
- 5,025,222
- Country
- IE
- Tail
- EI-HJN
- Type
- A339
- Flights observed
- 72
- Distinct callsigns
- 20
- Country
- IE
- Last broadcast
- 3h ago
Last known position
Country allocation
The ICAO 24-bit address 4CADC6 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 | 7 | 2026-05-30 |
| ITY675 | ITA Airways | 5 | 2026-05-21 |
| ITY672 | ITA Airways | 5 | 2026-05-29 |
| ITY615 | ITA Airways | 5 | 2026-05-15 |
| ITY614 | ITA Airways | 5 | 2026-05-15 |
| ITY678 | ITA Airways | 4 | 2026-05-16 |
| ITY674 | ITA Airways | 4 | 2026-05-20 |
| ITY603 | ITA Airways | 4 | 2026-06-01 |
| ITY602 | ITA Airways | 4 | 2026-06-01 |
| ITY679 | ITA Airways | 3 | 2026-05-16 |
| ITY641 | ITA Airways | 3 | 2026-05-28 |
| ITY640 | ITA Airways | 3 | 2026-05-28 |
| ITY630 | ITA Airways | 3 | 2026-06-02 |
| ITY6MO | ITA Airways | 2 | 2026-06-03 |
| ITY6KC | ITA Airways | 2 | 2026-05-07 |
| ITY610 | ITA Airways | 2 | 2026-05-06 |
| ITY8631 | ITA Airways | 1 | 2026-04-21 |
| ITY8012 | ITA Airways | 1 | 2026-05-25 |
| ITY8010 | ITA Airways | 1 | 2026-05-22 |
| ITY770 | ITA Airways | 1 | 2026-04-24 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-03 | ITY6MO | MIA → FCO | Jun 3, 00:45 UTC | Jun 3, 01:15 UTC | 30m |
| 2026-06-02 | ITY630 | FCO → MIA | Jun 2, 09:35 UTC | Jun 2, 20:05 UTC | 10h 30m |
| 2026-06-01 | ITY603 | JFK → FCO | Jun 1, 22:05 UTC | Jun 2, 05:30 UTC | 7h 25m |
| 2026-06-01 | ITY602 | FCO → JFK | Jun 1, 08:15 UTC | Jun 1, 17:00 UTC | 8h 45m |
| 2026-05-31 | ITY651 | YYZ → FCO | May 31, 21:25 UTC | Jun 1, 05:25 UTC | 8h 0m |
| 2026-05-31 | ITY650 | FCO → YYZ | May 31, 08:55 UTC | May 31, 17:45 UTC | 8h 50m |
| 2026-05-30 | ITY673 | GIG → FCO | May 30, 03:50 UTC | May 30, 14:25 UTC | 10h 35m |
| 2026-05-29 | ITY672 | FCO → GIG | May 29, 14:20 UTC | May 30, 01:35 UTC | 11h 15m |
| 2026-05-28 | ITY641 | SFO → FCO | May 28, 22:20 UTC | May 29, 10:05 UTC | 11h 45m |
| 2026-05-28 | ITY640 | FCO → SFO | May 28, 07:30 UTC | May 28, 19:50 UTC | 12h 20m |
| 2026-05-27 | ITY609 | JFK → FCO | May 27, 20:50 UTC | May 28, 04:45 UTC | 7h 55m |
| 2026-05-27 | ITY608 | FCO → JFK | May 27, 09:30 UTC | May 27, 17:50 UTC | 8h 20m |
| 2026-05-26 | ITY603 | JFK → FCO | May 26, 22:25 UTC | May 27, 06:25 UTC | 8h 0m |
| 2026-05-26 | ITY602 | FCO → JFK | May 26, 07:59 UTC | May 26, 16:30 UTC | 8h 30m |
| 2026-05-25 | ITY8012 | FCO → NAP | May 25, 14:45 UTC | May 25, 16:20 UTC | 1h 35m |
| 2026-05-22 | ITY8010 | CAG → AHO | May 22, 08:30 UTC | May 22, 10:25 UTC | 1h 55m |
| 2026-05-21 | ITY675 | GRU → FCO | May 21, 17:30 UTC | May 22, 04:25 UTC | 10h 55m |
| 2026-05-20 | ITY674 | FCO → GRU | May 20, 21:10 UTC | May 21, 08:55 UTC | 11h 45m |
| 2026-05-19 | ITY641 | SFO → FCO | May 19, 22:35 UTC | May 20, 09:55 UTC | 11h 21m |
| 2026-05-19 | ITY640 | FCO → SFO | May 19, 07:40 UTC | May 19, 19:55 UTC | 12h 15m |
| 2026-05-18 | ITY675 | GRU → FCO | May 18, 17:45 UTC | May 19, 04:35 UTC | 10h 49m |
| 2026-05-17 | ITY674 | FCO → GRU | May 17, 20:25 UTC | May 18, 08:05 UTC | 11h 40m |
| 2026-05-16 | ITY679 | GRU → FCO | May 16, 22:30 UTC | May 17, 09:05 UTC | 10h 35m |
| 2026-05-16 | ITY678 | FCO → GRU | May 16, 08:26 UTC | May 16, 20:05 UTC | 11h 40m |
| 2026-05-15 | ITY615 | BOS → FCO | May 15, 21:15 UTC | May 16, 04:25 UTC | 7h 10m |
| 2026-05-15 | ITY614 | FCO → BOS | May 15, 08:55 UTC | May 15, 17:40 UTC | 8h 44m |
| 2026-05-10 | ITY679 | GRU → FCO | May 10, 00:15 UTC | May 10, 10:55 UTC | 10h 40m |
| 2026-05-09 | ITY678 | FCO → GRU | May 9, 18:50 UTC | May 9, 20:15 UTC | 1h 25m |
| 2026-05-09 | ITY678 | FCO → GRU | May 9, 08:10 UTC | May 9, 14:10 UTC | 6h 0m |
| 2026-05-08 | ITY673 | GIG → FCO | May 8, 17:40 UTC | May 9, 04:00 UTC | 10h 20m |
| 2026-05-07 | ITY672 | FCO → GIG | May 7, 20:55 UTC | May 8, 08:34 UTC | 11h 40m |
| 2026-05-07 | ITY6KC | JFK → FCO | May 7, 01:55 UTC | May 7, 09:55 UTC | 8h 0m |
| 2026-05-06 | ITY610 | FCO → JFK | May 6, 13:30 UTC | May 6, 22:25 UTC | 8h 54m |
| 2026-05-05 | ITY615 | BOS → FCO | May 5, 21:20 UTC | May 6, 04:55 UTC | 7h 35m |
| 2026-05-05 | ITY614 | FCO → BOS | May 5, 08:50 UTC | May 5, 17:10 UTC | 8h 20m |
| 2026-05-04 | ITY675 | GRU → FCO | May 4, 17:35 UTC | May 5, 03:45 UTC | 10h 11m |
| 2026-05-03 | ITY674 | FCO → GRU | May 3, 20:30 UTC | May 4, 08:40 UTC | 12h 10m |
| 2026-05-03 | ITY6KC | JFK → FCO | May 3, 01:20 UTC | May 3, 09:15 UTC | 7h 54m |
| 2026-05-02 | ITY610 | FCO → JFK | May 2, 13:40 UTC | May 2, 22:30 UTC | 8h 50m |
| 2026-05-01 | ITY641 | SFO → FCO | May 1, 22:55 UTC | May 2, 10:20 UTC | 11h 25m |
| 2026-05-01 | ITY640 | FCO → SFO | May 1, 07:45 UTC | May 1, 20:10 UTC | 12h 25m |
| 2026-04-30 | ITY615 | BOS → FCO | Apr 30, 21:30 UTC | May 1, 05:15 UTC | 7h 45m |
| 2026-04-30 | ITY614 | FCO → BOS | Apr 30, 09:05 UTC | Apr 30, 17:15 UTC | 8h 10m |
| 2026-04-29 | ITY603 | JFK → FCO | Apr 29, 22:05 UTC | Apr 30, 06:15 UTC | 8h 9m |
| 2026-04-29 | ITY602 | FCO → JFK | Apr 29, 08:40 UTC | Apr 29, 17:10 UTC | 8h 31m |
| 2026-04-28 | ITY675 | GRU → FCO | Apr 28, 18:20 UTC | Apr 29, 04:10 UTC | 9h 50m |
| 2026-04-28 | ITY675 | GRU → FCO | Apr 28, 17:35 UTC | Apr 28, 17:45 UTC | 10m |
| 2026-04-27 | ITY674 | FCO → GRU | Apr 27, 20:45 UTC | Apr 28, 08:40 UTC | 11h 55m |
| 2026-04-26 | ITY603 | JFK → FCO | Apr 26, 22:00 UTC | Apr 27, 06:05 UTC | 8h 5m |
| 2026-04-26 | ITY602 | FCO → JFK | Apr 26, 08:10 UTC | Apr 26, 17:10 UTC | 9h 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-HJN page for operator, model, and routing details .