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