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
- 150
- Distinct callsigns
- 20
- Country
- IE
- Last broadcast
- Jul 26, 19:55 UTC
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 | - | 12 | 2026-07-11 |
| ITY678 | ITA Airways | 9 | 2026-07-26 |
| ITY672 | - | 9 | 2026-07-03 |
| ITY675 | ITA Airways | 8 | 2026-07-25 |
| ITY674 | ITA Airways | 8 | 2026-07-25 |
| ITY679 | - | 7 | 2026-07-16 |
| ITY641 | - | 7 | 2026-07-13 |
| ITY640 | - | 7 | 2026-07-13 |
| ITY630 | ITA Airways | 7 | 2026-07-21 |
| ITY615 | - | 7 | 2026-07-19 |
| ITY614 | ITA Airways | 7 | 2026-07-19 |
| ITY6MO | ITA Airways | 6 | 2026-07-22 |
| ITY6KC | - | 5 | 2026-06-25 |
| ITY610 | - | 5 | 2026-06-24 |
| ITY651 | - | 4 | 2026-07-07 |
| ITY603 | ITA Airways | 4 | 2026-06-01 |
| ITY602 | ITA Airways | 4 | 2026-06-01 |
| ITY650 | - | 3 | 2026-07-07 |
| ITY8012 | ITA Airways | 2 | 2026-06-30 |
| ITY770 | - | 2 | 2026-07-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | ITY678 | FCO → GRU | Jul 26, 08:30 UTC | Jul 26, 19:55 UTC | 11h 25m |
| 2026-07-25 | ITY675 | GRU → FCO | Jul 25, 17:20 UTC | Jul 26, 04:20 UTC | 11h 0m |
| 2026-07-25 | ITY674 | FCO → GRU | Jul 25, 02:45 UTC | Jul 25, 09:30 UTC | 6h 45m |
| 2026-07-24 | RYR81SV | STN → DUB | Jul 24, 23:45 UTC | Jul 24, 23:55 UTC | 10m |
| 2026-07-24 | ITY674 | FCO → GRU | Jul 24, 22:10 UTC | Jul 24, 23:00 UTC | 50m |
| 2026-07-22 | ITY6MO | MIA → FCO | Jul 22, 00:45 UTC | Jul 22, 10:25 UTC | 9h 40m |
| 2026-07-21 | ITY630 | FCO → MIA | Jul 21, 12:25 UTC | Jul 21, 22:20 UTC | 9h 55m |
| 2026-07-21 | ITY6MO | MIA → FCO | Jul 21, 00:10 UTC | Jul 21, 09:45 UTC | 9h 35m |
| 2026-07-20 | ITY630 | FCO → MIA | Jul 20, 10:20 UTC | Jul 20, 20:20 UTC | 10h 0m |
| 2026-07-19 | ITY615 | BOS → FCO | Jul 19, 21:45 UTC | Jul 20, 05:15 UTC | 7h 30m |
| 2026-07-19 | ITY614 | FCO → BOS | Jul 19, 10:45 UTC | Jul 19, 19:20 UTC | 8h 35m |
| 2026-07-18 | ITY6MO | MIA → FCO | Jul 18, 22:15 UTC | Jul 19, 07:55 UTC | 9h 40m |
| 2026-07-18 | ITY630 | FCO → MIA | Jul 18, 09:15 UTC | Jul 18, 19:45 UTC | 10h 30m |
| 2026-07-17 | ITY769 | DEL → FCO | Jul 17, 22:25 UTC | Jul 18, 06:05 UTC | 7h 41m |
| 2026-07-17 | ITY770 | - | Jul 17, 13:00 UTC | Jul 17, 20:10 UTC | 7h 10m |
| 2026-07-16 | ITY679 | - | Jul 16, 22:10 UTC | Jul 17, 08:54 UTC | 10h 45m |
| 2026-07-16 | ITY678 | - | Jul 16, 08:25 UTC | Jul 16, 19:40 UTC | 11h 15m |
| 2026-07-15 | ITY675 | - | Jul 15, 17:25 UTC | Jul 16, 04:20 UTC | 10h 55m |
| 2026-07-14 | ITY674 | FCO → GRU | Jul 14, 20:30 UTC | Jul 15, 07:45 UTC | 11h 14m |
| 2026-07-13 | ITY641 | SFO → FCO | Jul 13, 23:15 UTC | Jul 14, 10:15 UTC | 11h 0m |
| 2026-07-13 | ITY640 | - | Jul 13, 08:20 UTC | Jul 13, 21:05 UTC | 12h 45m |
| 2026-07-12 | ITY629 | - | Jul 12, 20:20 UTC | Jul 13, 05:25 UTC | 9h 5m |
| 2026-07-12 | ITY628 | - | Jul 12, 07:50 UTC | Jul 12, 17:30 UTC | 9h 40m |
| 2026-07-11 | ITY673 | - | Jul 11, 17:35 UTC | Jul 12, 03:55 UTC | 10h 20m |
| 2026-07-10 | ITY8672 | - | Jul 10, 20:45 UTC | Jul 11, 07:55 UTC | 11h 10m |
| 2026-07-10 | ITY633 | MIA → FCO | Jul 10, 03:50 UTC | Jul 10, 13:30 UTC | 9h 40m |
| 2026-07-09 | ITY632 | - | Jul 9, 13:35 UTC | Jul 9, 23:55 UTC | 10h 20m |
| 2026-07-08 | ITY641 | - | Jul 8, 23:35 UTC | Jul 9, 10:55 UTC | 11h 20m |
| 2026-07-08 | ITY640 | - | Jul 8, 08:40 UTC | Jul 8, 20:55 UTC | 12h 15m |
| 2026-07-07 | ITY651 | YYZ → FCO | Jul 7, 21:25 UTC | Jul 8, 05:45 UTC | 8h 20m |
| 2026-07-07 | ITY650 | - | Jul 7, 09:40 UTC | Jul 7, 18:10 UTC | 8h 30m |
| 2026-07-07 | ITY651 | - | Jul 7, 04:50 UTC | Jul 7, 06:20 UTC | 1h 30m |
| 2026-07-06 | ITY651 | - | Jul 6, 22:30 UTC | Jul 7, 04:45 UTC | 6h 15m |
| 2026-07-06 | ITY650 | - | Jul 6, 10:45 UTC | Jul 6, 19:45 UTC | 9h 0m |
| 2026-07-05 | ITY629 | - | Jul 5, 20:55 UTC | Jul 6, 05:15 UTC | 8h 20m |
| 2026-07-05 | ITY628 | - | Jul 5, 08:30 UTC | Jul 5, 18:40 UTC | 10h 10m |
| 2026-07-04 | ITY673 | GIG → FCO | Jul 4, 17:45 UTC | Jul 5, 04:15 UTC | 10h 30m |
| 2026-07-03 | ITY672 | FCO → GIG | Jul 3, 22:30 UTC | Jul 4, 09:30 UTC | 11h 0m |
| 2026-07-03 | ITY759 | - | Jul 3, 05:40 UTC | Jul 3, 17:10 UTC | 11h 30m |
| 2026-07-02 | ITY758 | - | Jul 2, 14:05 UTC | Jul 3, 01:00 UTC | 10h 55m |
| 2026-07-01 | ITY641 | SFO → FCO | Jul 1, 23:45 UTC | Jul 2, 11:05 UTC | 11h 20m |
| 2026-07-01 | ITY640 | - | Jul 1, 09:15 UTC | Jul 1, 21:10 UTC | 11h 55m |
| 2026-06-30 | ITY8012 | FCO → NAP | Jun 30, 16:35 UTC | Jun 30, 17:00 UTC | 25m |
| 2026-06-27 | ITY8006 | - | Jun 27, 15:39 UTC | Jun 27, 16:04 UTC | 25m |
| 2026-06-26 | ITY633 | MIA → FCO | Jun 26, 03:24 UTC | Jun 26, 12:55 UTC | 9h 30m |
| 2026-06-25 | ITY632 | FCO → MIA | Jun 25, 13:24 UTC | Jun 25, 23:34 UTC | 10h 10m |
| 2026-06-25 | ITY6KC | - | Jun 25, 02:10 UTC | Jun 25, 09:59 UTC | 7h 50m |
| 2026-06-24 | ITY610 | - | Jun 24, 14:20 UTC | Jun 24, 23:54 UTC | 9h 35m |
| 2026-06-24 | ITY6KC | - | Jun 24, 01:55 UTC | Jun 24, 09:45 UTC | 7h 50m |
| 2026-06-23 | ITY610 | - | Jun 23, 13:39 UTC | Jun 23, 22:34 UTC | 8h 55m |
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 .