sensors Mode-S transponder
4CADC8
ICAO 24-bit transponder address · allocated to Ireland
Currently assigned to EI-HJP · AIRBUS A-330-900
- Hex
- 4CADC8
- Octal
- 23126710
- Decimal
- 5,025,224
- Country
- IE
- Tail
- EI-HJP
- Type
- A339
- Flights observed
- 170
- Distinct callsigns
- 20
- Country
- IE
- Last broadcast
- Jul 26, 20:45 UTC
Current position
Country allocation
The ICAO 24-bit address 4CADC8 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 |
|---|---|---|---|
| ITY675 | ITA Airways | 14 | 2026-07-23 |
| ITY641 | ITA Airways | 11 | 2026-07-17 |
| ITY640 | - | 11 | 2026-07-17 |
| ITY674 | ITA Airways | 10 | 2026-07-22 |
| ITY672 | - | 8 | 2026-07-07 |
| ITY602 | - | 8 | 2026-06-30 |
| ITY758 | ITA Airways | 7 | 2026-07-21 |
| ITY6MO | ITA Airways | 7 | 2026-07-24 |
| ITY673 | - | 7 | 2026-07-08 |
| ITY630 | ITA Airways | 7 | 2026-07-24 |
| ITY759 | ITA Airways | 6 | 2026-07-22 |
| ITY603 | - | 6 | 2026-06-30 |
| ITY770 | ITA Airways | 5 | 2026-07-26 |
| ITY6KC | - | 5 | 2026-07-07 |
| ITY651 | - | 5 | 2026-07-19 |
| ITY650 | ITA Airways | 5 | 2026-07-19 |
| ITY610 | - | 5 | 2026-07-06 |
| ITY769 | ITA Airways | 4 | 2026-07-18 |
| ITY683 | - | 4 | 2026-07-11 |
| ITY682 | - | 4 | 2026-07-10 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | ITY770 | FCO → DEL | Jul 26, 13:30 UTC | Jul 26, 20:30 UTC | 7h 0m |
| 2026-07-26 | ITY637 | IAH → FCO | Jul 26, 00:10 UTC | Jul 26, 10:30 UTC | 10h 21m |
| 2026-07-25 | ITY636 | FCO → IAH | Jul 25, 10:15 UTC | Jul 25, 21:35 UTC | 11h 20m |
| 2026-07-24 | ITY6MO | MIA → FCO | Jul 24, 20:50 UTC | Jul 25, 06:25 UTC | 9h 35m |
| 2026-07-24 | ITY630 | FCO → MIA | Jul 24, 08:10 UTC | Jul 24, 17:50 UTC | 9h 40m |
| 2026-07-23 | ITY675 | GRU → FCO | Jul 23, 17:30 UTC | Jul 24, 04:35 UTC | 11h 5m |
| 2026-07-22 | ITY674 | FCO → GRU | Jul 22, 20:50 UTC | Jul 23, 08:15 UTC | 11h 25m |
| 2026-07-22 | ITY759 | BKK → FCO | Jul 22, 11:10 UTC | Jul 22, 17:35 UTC | 6h 25m |
| 2026-07-21 | ITY758 | FCO → BKK | Jul 21, 13:50 UTC | Jul 22, 00:15 UTC | 10h 25m |
| 2026-07-20 | ITY675 | GRU → FCO | Jul 20, 23:05 UTC | Jul 21, 09:50 UTC | 10h 44m |
| 2026-07-20 | ITY674 | FCO → GRU | Jul 20, 09:10 UTC | Jul 20, 20:35 UTC | 11h 25m |
| 2026-07-19 | ITY651 | YYZ → FCO | Jul 19, 21:35 UTC | Jul 20, 05:50 UTC | 8h 15m |
| 2026-07-19 | ITY650 | FCO → YYZ | Jul 19, 10:05 UTC | Jul 19, 19:10 UTC | 9h 5m |
| 2026-07-18 | ITY769 | DEL → FCO | Jul 18, 22:25 UTC | Jul 19, 06:10 UTC | 7h 45m |
| 2026-07-18 | ITY770 | - | Jul 18, 12:45 UTC | Jul 18, 19:55 UTC | 7h 10m |
| 2026-07-17 | ITY641 | SFO → FCO | Jul 17, 23:10 UTC | Jul 18, 10:20 UTC | 11h 11m |
| 2026-07-17 | ITY640 | - | Jul 17, 08:15 UTC | Jul 17, 20:44 UTC | 12h 30m |
| 2026-07-15 | ITY641 | SFO → FCO | Jul 15, 22:45 UTC | Jul 16, 09:50 UTC | 11h 5m |
| 2026-07-15 | ITY640 | - | Jul 15, 08:00 UTC | Jul 15, 20:40 UTC | 12h 40m |
| 2026-07-14 | ITY619 | - | Jul 14, 20:55 UTC | Jul 15, 05:30 UTC | 8h 34m |
| 2026-07-14 | ITY618 | - | Jul 14, 09:15 UTC | Jul 14, 18:20 UTC | 9h 5m |
| 2026-07-13 | ITY651 | YYZ → FCO | Jul 13, 21:10 UTC | Jul 14, 05:40 UTC | 8h 30m |
| 2026-07-13 | ITY650 | - | Jul 13, 09:45 UTC | Jul 13, 18:40 UTC | 8h 55m |
| 2026-07-12 | ITY675 | - | Jul 12, 17:30 UTC | Jul 13, 04:20 UTC | 10h 50m |
| 2026-07-11 | ITY674 | - | Jul 11, 20:45 UTC | Jul 12, 08:25 UTC | 11h 40m |
| 2026-07-11 | ITY683 | - | Jul 11, 04:40 UTC | Jul 11, 17:00 UTC | 12h 20m |
| 2026-07-10 | ITY682 | FCO → EZE | Jul 10, 12:45 UTC | Jul 11, 02:40 UTC | 13h 55m |
| 2026-07-09 | ITY679 | - | Jul 9, 22:20 UTC | Jul 10, 09:10 UTC | 10h 50m |
| 2026-07-09 | ITY678 | - | Jul 9, 08:05 UTC | Jul 9, 19:40 UTC | 11h 35m |
| 2026-07-08 | ITY673 | - | Jul 8, 17:35 UTC | Jul 9, 04:10 UTC | 10h 35m |
| 2026-07-07 | ITY672 | - | Jul 7, 20:40 UTC | Jul 8, 07:40 UTC | 11h 0m |
| 2026-07-07 | ITY6KC | JFK → FCO | Jul 7, 02:10 UTC | Jul 7, 09:55 UTC | 7h 45m |
| 2026-07-06 | ITY610 | - | Jul 6, 13:50 UTC | Jul 6, 22:35 UTC | 8h 45m |
| 2026-07-05 | ITY637 | - | Jul 5, 23:35 UTC | Jul 6, 09:50 UTC | 10h 15m |
| 2026-07-05 | ITY636 | - | Jul 5, 09:20 UTC | Jul 5, 20:40 UTC | 11h 20m |
| 2026-07-04 | ITY629 | ORD → FCO | Jul 4, 20:45 UTC | Jul 5, 05:10 UTC | 8h 25m |
| 2026-07-04 | ITY628 | - | Jul 4, 07:45 UTC | Jul 4, 18:15 UTC | 10h 30m |
| 2026-07-03 | ITY629 | - | Jul 3, 20:35 UTC | Jul 4, 04:55 UTC | 8h 20m |
| 2026-07-03 | ITY628 | - | Jul 3, 07:45 UTC | Jul 3, 18:00 UTC | 10h 15m |
| 2026-07-02 | ITY619 | IAD → FCO | Jul 2, 21:15 UTC | Jul 3, 05:05 UTC | 7h 50m |
| 2026-07-02 | ITY618 | - | Jul 2, 09:00 UTC | Jul 2, 18:20 UTC | 9h 20m |
| 2026-07-01 | ITY651 | - | Jul 1, 21:15 UTC | Jul 2, 05:25 UTC | 8h 10m |
| 2026-07-01 | ITY650 | - | Jul 1, 08:55 UTC | Jul 1, 18:20 UTC | 9h 25m |
| 2026-06-30 | ITY603 | - | Jun 30, 22:35 UTC | Jul 1, 06:15 UTC | 7h 40m |
| 2026-06-30 | ITY602 | - | Jun 30, 08:05 UTC | Jun 30, 16:50 UTC | 8h 45m |
| 2026-06-29 | ITY675 | - | Jun 29, 17:34 UTC | Jun 30, 04:25 UTC | 10h 51m |
| 2026-06-28 | ITY674 | - | Jun 28, 20:39 UTC | Jun 29, 08:04 UTC | 11h 25m |
| 2026-06-27 | ITY641 | - | Jun 27, 22:45 UTC | Jun 28, 10:24 UTC | 11h 40m |
| 2026-06-27 | ITY640 | - | Jun 27, 07:59 UTC | Jun 27, 20:04 UTC | 12h 5m |
| 2026-06-15 | ITY6MO | - | Jun 15, 00:05 UTC | Jun 15, 09:30 UTC | 9h 25m |
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-HJP page for operator, model, and routing details .