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