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
- 79
- Distinct callsigns
- 20
- Country
- IE
- Last broadcast
- 4h ago
Current 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 |
|---|---|---|---|
| ITY651 | ITA Airways | 6 | 2026-05-15 |
| ITY641 | ITA Airways | 6 | 2026-05-29 |
| ITY640 | ITA Airways | 6 | 2026-05-29 |
| ITY603 | ITA Airways | 6 | 2026-05-05 |
| ITY602 | ITA Airways | 6 | 2026-05-05 |
| ITY673 | ITA Airways | 5 | 2026-05-25 |
| ITY672 | ITA Airways | 5 | 2026-05-24 |
| ITY650 | ITA Airways | 5 | 2026-05-15 |
| ITY770 | ITA Airways | 4 | 2026-04-27 |
| ITY769 | ITA Airways | 4 | 2026-04-27 |
| ITY6KC | ITA Airways | 3 | 2026-05-31 |
| ITY610 | ITA Airways | 3 | 2026-05-30 |
| ITY6MO | ITA Airways | 2 | 2026-04-30 |
| ITY630 | ITA Airways | 2 | 2026-04-30 |
| ITY609 | ITA Airways | 2 | 2026-06-01 |
| ITY608 | ITA Airways | 2 | 2026-06-01 |
| ITY759 | ITA Airways | 1 | 2026-04-20 |
| ITY758 | ITA Airways | 1 | 2026-04-19 |
| ITY675 | ITA Airways | 1 | 2026-05-28 |
| ITY674 | ITA Airways | 1 | 2026-05-27 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | ITY629 | ORD → FCO | Jun 2, 20:15 UTC | Jun 2, 22:25 UTC | 2h 10m |
| 2026-06-02 | ITY628 | FCO → ORD | Jun 2, 07:40 UTC | Jun 2, 17:00 UTC | 9h 20m |
| 2026-06-01 | ITY609 | JFK → FCO | Jun 1, 20:20 UTC | Jun 2, 03:40 UTC | 7h 20m |
| 2026-06-01 | ITY608 | FCO → JFK | Jun 1, 08:55 UTC | Jun 1, 17:40 UTC | 8h 45m |
| 2026-05-31 | ITY6KC | JFK → FCO | May 31, 08:25 UTC | May 31, 09:45 UTC | 1h 20m |
| 2026-05-30 | ITY610 | FCO → JFK | May 30, 13:40 UTC | May 30, 22:35 UTC | 8h 55m |
| 2026-05-29 | ITY641 | SFO → FCO | May 29, 23:15 UTC | May 30, 10:55 UTC | 11h 40m |
| 2026-05-29 | ITY640 | FCO → SFO | May 29, 07:45 UTC | May 29, 20:20 UTC | 12h 35m |
| 2026-05-28 | ITY675 | GRU → FCO | May 28, 17:25 UTC | May 29, 04:05 UTC | 10h 40m |
| 2026-05-27 | ITY674 | FCO → GRU | May 27, 20:40 UTC | May 28, 08:15 UTC | 11h 35m |
| 2026-05-26 | ITY641 | SFO → FCO | May 26, 22:44 UTC | May 27, 10:15 UTC | 11h 31m |
| 2026-05-26 | ITY640 | FCO → SFO | May 26, 08:50 UTC | May 26, 19:50 UTC | 11h 0m |
| 2026-05-26 | ITY640 | FCO → SFO | May 26, 07:29 UTC | May 26, 08:45 UTC | 1h 15m |
| 2026-05-25 | ITY673 | GIG → FCO | May 25, 17:45 UTC | May 26, 04:10 UTC | 10h 25m |
| 2026-05-24 | ITY672 | FCO → GIG | May 24, 20:40 UTC | May 25, 07:50 UTC | 11h 10m |
| 2026-05-17 | ITY637 | IAH → FCO | May 17, 23:40 UTC | May 18, 09:50 UTC | 10h 10m |
| 2026-05-17 | ITY636 | FCO → IAH | May 17, 08:45 UTC | May 17, 20:35 UTC | 11h 50m |
| 2026-05-16 | ITY609 | JFK → FCO | May 16, 22:05 UTC | May 17, 05:45 UTC | 7h 40m |
| 2026-05-16 | ITY608 | FCO → JFK | May 16, 08:36 UTC | May 16, 17:35 UTC | 9h 0m |
| 2026-05-15 | ITY651 | YYZ → FCO | May 15, 21:20 UTC | May 16, 05:20 UTC | 8h 0m |
| 2026-05-15 | ITY650 | FCO → YYZ | May 15, 08:40 UTC | May 15, 17:35 UTC | 8h 54m |
| 2026-05-14 | ITY673 | GIG → FCO | May 14, 17:30 UTC | May 15, 03:20 UTC | 9h 50m |
| 2026-05-13 | ITY672 | FCO → GIG | May 13, 20:45 UTC | May 14, 08:30 UTC | 11h 45m |
| 2026-05-13 | ITY641 | SFO → FCO | May 13, 08:15 UTC | May 13, 10:05 UTC | 1h 50m |
| 2026-05-12 | ITY641 | SFO → FCO | May 12, 23:01 UTC | May 13, 08:10 UTC | 9h 10m |
| 2026-05-12 | ITY640 | FCO → SFO | May 12, 07:35 UTC | May 12, 20:15 UTC | 12h 40m |
| 2026-05-11 | ITY673 | GIG → FCO | May 11, 17:40 UTC | May 12, 03:45 UTC | 10h 5m |
| 2026-05-10 | ITY672 | FCO → GIG | May 10, 20:54 UTC | May 11, 08:25 UTC | 11h 30m |
| 2026-05-10 | ITY6KC | JFK → FCO | May 10, 01:45 UTC | May 10, 09:50 UTC | 8h 5m |
| 2026-05-09 | ITY610 | FCO → JFK | May 9, 13:40 UTC | May 9, 22:15 UTC | 8h 35m |
| 2026-05-08 | ITY641 | SFO → FCO | May 8, 22:45 UTC | May 9, 10:20 UTC | 11h 35m |
| 2026-05-08 | ITY640 | FCO → SFO | May 8, 07:50 UTC | May 8, 20:05 UTC | 12h 15m |
| 2026-05-07 | ITY673 | GIG → FCO | May 7, 17:45 UTC | May 8, 04:00 UTC | 10h 15m |
| 2026-05-06 | ITY672 | FCO → GIG | May 6, 21:10 UTC | May 7, 08:55 UTC | 11h 45m |
| 2026-05-05 | ITY603 | JFK → FCO | May 5, 22:01 UTC | May 6, 05:55 UTC | 7h 54m |
| 2026-05-05 | ITY602 | FCO → JFK | May 5, 07:55 UTC | May 5, 16:40 UTC | 8h 45m |
| 2026-05-04 | ITY615 | BOS → FCO | May 4, 21:30 UTC | May 5, 04:55 UTC | 7h 25m |
| 2026-05-04 | ITY614 | FCO → BOS | May 4, 08:50 UTC | May 4, 17:15 UTC | 8h 25m |
| 2026-05-03 | ITY603 | JFK → FCO | May 3, 21:44 UTC | May 4, 05:45 UTC | 8h 0m |
| 2026-05-03 | ITY602 | FCO → JFK | May 3, 08:05 UTC | May 3, 16:55 UTC | 8h 50m |
| 2026-05-02 | ITY673 | GIG → FCO | May 2, 17:40 UTC | May 3, 04:10 UTC | 10h 29m |
| 2026-05-01 | ITY672 | FCO → GIG | May 1, 20:40 UTC | May 2, 07:50 UTC | 11h 11m |
| 2026-04-30 | ITY6MO | MIA → FCO | Apr 30, 23:00 UTC | May 1, 08:25 UTC | 9h 25m |
| 2026-04-30 | ITY630 | FCO → MIA | Apr 30, 09:30 UTC | Apr 30, 20:05 UTC | 10h 35m |
| 2026-04-27 | ITY769 | DEL → FCO | Apr 27, 22:25 UTC | Apr 28, 06:25 UTC | 8h 0m |
| 2026-04-27 | ITY770 | FCO → DEL | Apr 27, 12:30 UTC | Apr 27, 20:00 UTC | 7h 30m |
| 2026-04-27 | ITY6KC | JFK → FCO | Apr 27, 01:30 UTC | Apr 27, 09:40 UTC | 8h 10m |
| 2026-04-26 | ITY610 | FCO → JFK | Apr 26, 13:25 UTC | Apr 26, 22:00 UTC | 8h 35m |
| 2026-04-25 | ITY769 | DEL → FCO | Apr 25, 22:05 UTC | Apr 26, 06:30 UTC | 8h 25m |
| 2026-04-25 | ITY770 | FCO → DEL | Apr 25, 12:20 UTC | Apr 25, 19:30 UTC | 7h 10m |
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 .