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