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