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
- 150
- Distinct callsigns
- 20
- Country
- IE
- Last broadcast
- 1h ago
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 | - | 12 | 2026-07-12 |
| ITY641 | - | 9 | 2026-06-27 |
| ITY640 | - | 9 | 2026-06-27 |
| ITY674 | - | 8 | 2026-07-11 |
| ITY672 | - | 8 | 2026-07-07 |
| ITY602 | - | 8 | 2026-06-30 |
| ITY673 | - | 7 | 2026-07-08 |
| ITY758 | - | 6 | 2026-04-14 |
| ITY6MO | - | 6 | 2026-06-15 |
| ITY630 | ITA Airways | 6 | 2026-06-14 |
| ITY603 | - | 6 | 2026-06-30 |
| ITY759 | ITA Airways | 5 | 2026-04-15 |
| ITY6KC | - | 5 | 2026-07-07 |
| ITY610 | - | 5 | 2026-07-06 |
| ITY683 | - | 4 | 2026-07-11 |
| ITY682 | - | 4 | 2026-07-10 |
| ITY651 | - | 4 | 2026-07-13 |
| ITY650 | - | 4 | 2026-07-13 |
| ITY770 | ITA Airways | 3 | 2026-06-10 |
| ITY769 | ITA Airways | 3 | 2026-06-10 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | ITY618 | - | Jul 14, 09:15 UTC | Jul 14, 10:00 UTC | 45m |
| 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 |
| 2026-06-14 | ITY630 | FCO → MIA | Jun 14, 09:30 UTC | Jun 14, 19:50 UTC | 10h 20m |
| 2026-06-11 | ITY6MO | - | Jun 11, 23:50 UTC | Jun 12, 09:35 UTC | 9h 46m |
| 2026-06-11 | ITY630 | FCO → MIA | Jun 11, 09:10 UTC | Jun 11, 19:35 UTC | 10h 25m |
| 2026-06-10 | ITY769 | DEL → FCO | Jun 10, 22:00 UTC | Jun 11, 06:10 UTC | 8h 10m |
| 2026-06-10 | ITY770 | FCO → DEL | Jun 10, 12:25 UTC | Jun 10, 19:45 UTC | 7h 20m |
| 2026-06-09 | ITY6MO | MIA → FCO | Jun 9, 23:50 UTC | Jun 10, 09:15 UTC | 9h 25m |
| 2026-06-09 | ITY630 | FCO → MIA | Jun 9, 09:00 UTC | Jun 9, 20:30 UTC | 11h 30m |
| 2026-06-08 | ITY675 | GRU → FCO | Jun 8, 17:40 UTC | Jun 9, 04:40 UTC | 11h 0m |
| 2026-06-07 | ITY8674 | FCO → GRU | Jun 7, 20:40 UTC | Jun 8, 08:30 UTC | 11h 50m |
| 2026-06-06 | ITY683 | EZE → FCO | Jun 6, 04:55 UTC | Jun 6, 17:05 UTC | 12h 10m |
| 2026-06-05 | ITY682 | FCO → EZE | Jun 5, 13:00 UTC | Jun 6, 02:55 UTC | 13h 55m |
| 2026-06-05 | ITY6KC | JFK → FCO | Jun 5, 01:30 UTC | Jun 5, 09:15 UTC | 7h 45m |
| 2026-06-04 | ITY610 | FCO → JFK | Jun 4, 13:50 UTC | Jun 4, 22:50 UTC | 9h 0m |
| 2026-06-03 | ITY637 | IAH → FCO | Jun 3, 23:25 UTC | Jun 4, 09:20 UTC | 9h 55m |
| 2026-06-03 | ITY636 | FCO → IAH | Jun 3, 08:55 UTC | Jun 3, 20:45 UTC | 11h 50m |
| 2026-06-02 | ITY651 | YYZ → FCO | Jun 2, 21:25 UTC | Jun 3, 05:40 UTC | 8h 15m |
| 2026-06-02 | ITY650 | FCO → YYZ | Jun 2, 09:00 UTC | Jun 2, 17:35 UTC | 8h 35m |
| 2026-05-31 | ITY675 | GRU → FCO | May 31, 17:30 UTC | Jun 1, 04:05 UTC | 10h 35m |
| 2026-05-31 | ITY674 | FCO → GRU | May 31, 08:25 UTC | May 31, 08:40 UTC | 15m |
| 2026-05-30 | ITY674 | FCO → GRU | May 30, 21:05 UTC | May 30, 22:45 UTC | 1h 40m |
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 .