sensors Mode-S transponder
300473
ICAO 24-bit transponder address · allocated to Italy
Currently assigned to I-JAMI · DASSAULT Falcon 7X
- Hex
- 300473
- Octal
- 14002163
- Decimal
- 3,146,867
- Country
- IT
- Tail
- I-JAMI
- Type
- FA7X
- Flights observed
- 78
- Distinct callsigns
- 2
- Country
- IT
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 300473 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 2 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-16 | SIO624 | IBZ → LIN | Jul 16, 09:40 UTC | Jul 16, 11:05 UTC | 1h 25m |
| 2026-07-15 | SIO624A | LIN → IBZ | Jul 15, 16:15 UTC | Jul 15, 18:05 UTC | 1h 50m |
| 2026-07-15 | SIO624 | - | Jul 15, 10:25 UTC | Jul 15, 11:15 UTC | 50m |
| 2026-07-15 | SIO624 | - | Jul 15, 08:10 UTC | Jul 15, 08:55 UTC | 45m |
| 2026-07-14 | SIO624 | - | Jul 14, 17:30 UTC | Jul 14, 18:15 UTC | 45m |
| 2026-07-13 | SIO624 | - | Jul 13, 16:25 UTC | Jul 13, 17:55 UTC | 1h 30m |
| 2026-07-13 | SIO624 | - | Jul 13, 14:20 UTC | Jul 13, 14:55 UTC | 35m |
| 2026-07-13 | SIO624 | - | Jul 13, 10:25 UTC | Jul 13, 11:20 UTC | 55m |
| 2026-07-12 | SIO624 | - | Jul 12, 15:30 UTC | Jul 12, 16:35 UTC | 1h 5m |
| 2026-07-12 | SIO624 | - | Jul 12, 13:40 UTC | Jul 12, 14:10 UTC | 30m |
| 2026-07-11 | SIO624 | - | Jul 11, 11:50 UTC | Jul 11, 12:30 UTC | 40m |
| 2026-07-11 | SIO624 | - | Jul 11, 10:15 UTC | Jul 11, 11:00 UTC | 45m |
| 2026-07-09 | SIO624 | LGW → LIN | Jul 9, 18:20 UTC | Jul 9, 21:05 UTC | 2h 45m |
| 2026-07-08 | SIO624 | TRN → LGW | Jul 8, 12:50 UTC | Jul 8, 14:15 UTC | 1h 25m |
| 2026-07-08 | SIO624 | LIN → TRN | Jul 8, 11:10 UTC | Jul 8, 11:35 UTC | 25m |
| 2026-07-05 | SIO624 | - | Jul 5, 15:45 UTC | Jul 5, 18:25 UTC | 2h 40m |
| 2026-07-05 | SIO624 | - | Jul 5, 13:00 UTC | Jul 5, 15:05 UTC | 2h 5m |
| 2026-07-05 | SIO624 | LIN → BLQ | Jul 5, 09:05 UTC | Jul 5, 09:35 UTC | 30m |
| 2026-07-01 | SIO624 | - | Jul 1, 18:55 UTC | Jul 1, 19:40 UTC | 45m |
| 2026-07-01 | SIO624 | - | Jul 1, 17:10 UTC | Jul 1, 18:00 UTC | 50m |
| 2026-06-30 | SIO624A | IBZ → LIN | Jun 30, 14:40 UTC | Jun 30, 16:15 UTC | 1h 35m |
| 2026-06-30 | SIO624A | LIN → IBZ | Jun 30, 12:20 UTC | Jun 30, 13:50 UTC | 1h 30m |
| 2026-06-26 | SIO624A | - | Jun 26, 16:54 UTC | Jun 26, 17:15 UTC | 20m |
| 2026-06-26 | SIO624A | - | Jun 26, 15:34 UTC | Jun 26, 16:20 UTC | 45m |
| 2026-06-26 | SIO624A | - | Jun 26, 14:05 UTC | Jun 26, 14:35 UTC | 30m |
| 2026-06-26 | SIO624 | - | Jun 26, 12:34 UTC | Jun 26, 13:19 UTC | 45m |
| 2026-06-26 | SIO624 | LIN → CIA | Jun 26, 05:44 UTC | Jun 26, 06:29 UTC | 45m |
| 2026-06-25 | SIO624 | BRU → LIN | Jun 25, 10:55 UTC | Jun 25, 12:04 UTC | 1h 10m |
| 2026-06-23 | SIO624 | LIN → BRU | Jun 23, 05:49 UTC | Jun 23, 07:05 UTC | 1h 15m |
| 2026-06-18 | SIO624 | - | Jun 18, 13:00 UTC | Jun 18, 13:35 UTC | 35m |
| 2026-06-18 | SIO624 | - | Jun 18, 10:40 UTC | Jun 18, 12:25 UTC | 1h 45m |
| 2026-06-18 | SIO624 | LIN → IBZ | Jun 18, 07:20 UTC | Jun 18, 08:45 UTC | 1h 25m |
| 2026-06-03 | SIO624 | - | Jun 3, 18:05 UTC | Jun 3, 19:45 UTC | 1h 40m |
| 2026-06-03 | SIO624 | - | Jun 3, 16:45 UTC | Jun 3, 17:15 UTC | 30m |
| 2026-06-03 | SIO624 | NCE → BLQ | Jun 3, 15:25 UTC | Jun 3, 16:00 UTC | 35m |
| 2026-06-03 | SIO624 | LIN → NCE | Jun 3, 12:25 UTC | Jun 3, 13:05 UTC | 40m |
| 2026-06-01 | SIO624 | - | Jun 1, 16:55 UTC | Jun 1, 17:50 UTC | 55m |
| 2026-06-01 | SIO624 | - | Jun 1, 15:00 UTC | Jun 1, 15:40 UTC | 40m |
| 2026-06-01 | SIO624 | LIN → BLQ | Jun 1, 13:10 UTC | Jun 1, 13:35 UTC | 25m |
| 2026-05-29 | SIO624 | NCE → LIN | May 29, 18:30 UTC | May 29, 19:00 UTC | 30m |
| 2026-05-29 | SIO624 | - | May 29, 17:00 UTC | May 29, 17:40 UTC | 40m |
| 2026-05-29 | SIO624 | - | May 29, 13:45 UTC | May 29, 14:15 UTC | 30m |
| 2026-05-24 | SIO624 | IBZ → LIN | May 24, 16:15 UTC | May 24, 19:00 UTC | 2h 45m |
| 2026-05-22 | SIO624 | LIN → IBZ | May 22, 14:25 UTC | May 22, 15:50 UTC | 1h 25m |
| 2026-05-22 | SIO624A | - | May 22, 10:10 UTC | May 22, 11:05 UTC | 55m |
| 2026-05-22 | SIO624A | LIN → PEG | May 22, 08:55 UTC | May 22, 09:35 UTC | 40m |
| 2026-05-14 | SIO624 | - | May 14, 13:45 UTC | May 14, 15:01 UTC | 1h 15m |
| 2026-05-14 | SIO624 | - | May 14, 05:35 UTC | May 14, 06:55 UTC | 1h 20m |
| 2026-05-12 | SIO624 | - | May 12, 14:05 UTC | May 12, 16:20 UTC | 2h 15m |
| 2026-05-11 | SIO624 | - | May 11, 08:55 UTC | May 11, 10:10 UTC | 1h 15m |
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 I-JAMI page for operator, model, and routing details .