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