sensors Mode-S transponder
300A86
ICAO 24-bit transponder address · allocated to Italy
- Hex
- 300A86
- Octal
- 14005206
- Decimal
- 3,148,422
- Country
- IT
- Flights observed
- 75
- Distinct callsigns
- 20
- Country
- IT
- Last broadcast
- 15d ago
Last known position
Country allocation
The ICAO 24-bit address 300A86 falls within the block assigned to Italy (IT) by ICAO Annex 10, Volume III. Every aircraft registered in Italy 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 |
|---|---|---|---|
| ITY1773 | ITA Airways | 3 | 2026-05-21 |
| ITY1772 | ITA Airways | 3 | 2026-05-21 |
| ITY1297 | ITA Airways | 3 | 2026-05-20 |
| ITY1278 | ITA Airways | 3 | 2026-05-21 |
| ITY1365 | ITA Airways | 2 | 2026-04-29 |
| ITY1363 | ITA Airways | 2 | 2026-04-28 |
| ITY1360 | ITA Airways | 2 | 2026-04-29 |
| ITY1358 | ITA Airways | 2 | 2026-04-28 |
| ITY1357 | ITA Airways | 2 | 2026-04-28 |
| ITY1356 | ITA Airways | 2 | 2026-04-29 |
| ITY1319 | ITA Airways | 2 | 2026-04-28 |
| ITY1318 | ITA Airways | 2 | 2026-04-28 |
| ITY8008 | ITA Airways | 1 | 2026-05-23 |
| ITY7CI | ITA Airways | 1 | 2026-04-28 |
| ITY4LI | ITA Airways | 1 | 2026-04-25 |
| ITY453 | ITA Airways | 1 | 2026-05-22 |
| ITY452 | ITA Airways | 1 | 2026-05-22 |
| ITY437 | ITA Airways | 1 | 2026-04-27 |
| ITY432 | ITA Airways | 1 | 2026-04-27 |
| ITY358 | ITA Airways | 1 | 2026-05-21 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-23 | ITY8008 | LIN → LIN | May 23, 08:00 UTC | May 23, 09:10 UTC | 1h 10m |
| 2026-05-22 | ITY453 | MUC → LIN | May 22, 18:10 UTC | May 22, 19:00 UTC | 50m |
| 2026-05-22 | ITY452 | LIN → MUC | May 22, 16:00 UTC | May 22, 16:45 UTC | 45m |
| 2026-05-22 | ITY227 | LCY → LIN | May 22, 13:15 UTC | May 22, 14:40 UTC | 1h 25m |
| 2026-05-22 | ITY226 | LIN → LCY | May 22, 10:40 UTC | May 22, 12:10 UTC | 1h 30m |
| 2026-05-22 | ITY305 | CDG → LIN | May 22, 08:30 UTC | May 22, 09:30 UTC | 1h 0m |
| 2026-05-22 | ITY300 | LIN → CDG | May 22, 05:45 UTC | May 22, 06:55 UTC | 1h 10m |
| 2026-05-21 | ITY311 | CDG → LIN | May 21, 19:50 UTC | May 21, 20:50 UTC | 1h 0m |
| 2026-05-21 | ITY358 | LIN → CDG | May 21, 17:25 UTC | May 21, 18:35 UTC | 1h 10m |
| 2026-05-21 | ITY313 | CDG → LIN | May 21, 15:15 UTC | May 21, 16:10 UTC | 55m |
| 2026-05-21 | ITY312 | LIN → CDG | May 21, 12:40 UTC | May 21, 13:50 UTC | 1h 10m |
| 2026-05-21 | ITY1772 | PMO → LIN | May 21, 09:15 UTC | May 21, 10:35 UTC | 1h 20m |
| 2026-05-21 | ITY1773 | LIN → PMO | May 21, 06:40 UTC | May 21, 07:40 UTC | 1h 0m |
| 2026-05-21 | ITY1278 | NAP → LIN | May 21, 04:30 UTC | May 21, 05:30 UTC | 1h 0m |
| 2026-05-20 | ITY1297 | LIN → NAP | May 20, 19:20 UTC | May 20, 20:10 UTC | 50m |
| 2026-05-20 | ITY2050 | FCO → LIN | May 20, 16:20 UTC | May 20, 17:15 UTC | 55m |
| 2026-05-20 | ITY2059 | LIN → FCO | May 20, 14:05 UTC | May 20, 15:00 UTC | 55m |
| 2026-05-20 | ITY1772 | PMO → LIN | May 20, 09:45 UTC | May 20, 11:00 UTC | 1h 15m |
| 2026-05-20 | ITY1773 | LIN → PMO | May 20, 06:45 UTC | May 20, 07:55 UTC | 1h 10m |
| 2026-05-20 | ITY1278 | NAP → LIN | May 20, 04:40 UTC | May 20, 05:40 UTC | 1h 0m |
| 2026-05-19 | ITY1297 | LIN → NAP | May 19, 19:25 UTC | May 19, 20:25 UTC | 1h 0m |
| 2026-05-19 | ITY1282 | NAP → LIN | May 19, 16:55 UTC | May 19, 17:55 UTC | 1h 0m |
| 2026-05-19 | ITY1281 | LIN → NAP | May 19, 14:30 UTC | May 19, 15:15 UTC | 45m |
| 2026-05-19 | ITY1288 | NAP → LIN | May 19, 11:05 UTC | May 19, 12:10 UTC | 1h 5m |
| 2026-05-19 | ITY1299 | LIN → NAP | May 19, 08:05 UTC | May 19, 09:00 UTC | 55m |
| 2026-05-19 | ITY2014 | FCO → LIN | May 19, 05:00 UTC | May 19, 05:50 UTC | 50m |
| 2026-04-30 | ITY1386 | GOA → FCO | Apr 30, 13:50 UTC | Apr 30, 14:30 UTC | 40m |
| 2026-04-30 | ITY1395 | FCO → GOA | Apr 30, 12:10 UTC | Apr 30, 12:50 UTC | 40m |
| 2026-04-29 | ITY1712 | CTA → FCO | Apr 29, 17:25 UTC | Apr 29, 18:25 UTC | 1h 0m |
| 2026-04-29 | ITY1733 | FCO → CTA | Apr 29, 15:35 UTC | Apr 29, 16:25 UTC | 50m |
| 2026-04-29 | ITY1360 | TRS → FCO | Apr 29, 13:25 UTC | Apr 29, 14:00 UTC | 35m |
| 2026-04-29 | ITY1365 | FCO → TRS | Apr 29, 12:00 UTC | Apr 29, 12:45 UTC | 45m |
| 2026-04-29 | ITY1624 | BDS → FCO | Apr 29, 09:45 UTC | Apr 29, 10:35 UTC | 50m |
| 2026-04-29 | ITY1621 | FCO → BDS | Apr 29, 07:55 UTC | Apr 29, 08:45 UTC | 50m |
| 2026-04-29 | ITY1356 | TRS → FCO | Apr 29, 04:39 UTC | Apr 29, 05:25 UTC | 45m |
| 2026-04-28 | ITY1363 | FCO → TRS | Apr 28, 19:55 UTC | Apr 28, 20:40 UTC | 45m |
| 2026-04-28 | ITY1170 | SUF → FCO | Apr 28, 17:20 UTC | Apr 28, 18:10 UTC | 50m |
| 2026-04-28 | ITY7CI | FCO → SUF | Apr 28, 15:40 UTC | Apr 28, 16:25 UTC | 45m |
| 2026-04-28 | ITY1318 | BLQ → FCO | Apr 28, 13:45 UTC | Apr 28, 14:20 UTC | 35m |
| 2026-04-28 | ITY1319 | FCO → BLQ | Apr 28, 12:10 UTC | Apr 28, 12:50 UTC | 40m |
| 2026-04-28 | ITY1358 | TRS → FCO | Apr 28, 09:15 UTC | Apr 28, 10:00 UTC | 45m |
| 2026-04-28 | ITY1357 | FCO → TRS | Apr 28, 07:30 UTC | Apr 28, 08:15 UTC | 45m |
| 2026-04-28 | ITY1380 | GOA → FCO | Apr 28, 04:55 UTC | Apr 28, 05:35 UTC | 40m |
| 2026-04-27 | ITY1391 | FCO → GOA | Apr 27, 15:50 UTC | Apr 27, 16:35 UTC | 45m |
| 2026-04-27 | ITY1318 | BLQ → FCO | Apr 27, 13:45 UTC | Apr 27, 14:15 UTC | 30m |
| 2026-04-27 | ITY1319 | FCO → BLQ | Apr 27, 12:00 UTC | Apr 27, 12:40 UTC | 40m |
| 2026-04-27 | ITY437 | MUC → FCO | Apr 27, 09:25 UTC | Apr 27, 10:30 UTC | 1h 5m |
| 2026-04-27 | ITY432 | FCO → MUC | Apr 27, 07:00 UTC | Apr 27, 08:10 UTC | 1h 10m |
| 2026-04-27 | ITY1PR | NAP → FCO | Apr 27, 05:00 UTC | Apr 27, 05:40 UTC | 40m |
| 2026-04-26 | ITY1267 | FCO → NAP | Apr 26, 20:05 UTC | Apr 26, 20:30 UTC | 25m |
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.