sensors Mode-S transponder
300762
ICAO 24-bit transponder address · allocated to Italy
Currently assigned to I-AVNE · LEARJET 40
- Hex
- 300762
- Octal
- 14003542
- Decimal
- 3,147,618
- Country
- IT
- Tail
- I-AVNE
- Type
- LJ40
- Flights observed
- 94
- Distinct callsigns
- 2
- Country
- IT
- Last broadcast
- 11h ago
Last known position
Country allocation
The ICAO 24-bit address 300762 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-17 | VND008E | - | Jul 17, 13:10 UTC | Jul 17, 13:29 UTC | 20m |
| 2026-07-17 | VND008E | - | Jul 17, 12:15 UTC | Jul 17, 12:35 UTC | 20m |
| 2026-07-17 | VND008E | - | Jul 17, 10:10 UTC | Jul 17, 10:35 UTC | 25m |
| 2026-07-16 | VND008E | - | Jul 16, 03:05 UTC | Jul 16, 03:40 UTC | 35m |
| 2026-07-16 | VND008E | - | Jul 16, 01:20 UTC | Jul 16, 01:55 UTC | 35m |
| 2026-07-15 | VND008E | - | Jul 15, 23:45 UTC | Jul 16, 00:10 UTC | 25m |
| 2026-07-15 | VND008E | - | Jul 15, 05:05 UTC | Jul 15, 07:05 UTC | 2h 0m |
| 2026-07-14 | VND008E | - | Jul 14, 19:40 UTC | Jul 14, 21:30 UTC | 1h 50m |
| 2026-07-14 | VND008E | - | Jul 14, 18:15 UTC | Jul 14, 18:35 UTC | 20m |
| 2026-07-11 | VND008E | - | Jul 11, 04:45 UTC | Jul 11, 06:35 UTC | 1h 50m |
| 2026-07-10 | VND008E | - | Jul 10, 22:20 UTC | Jul 11, 00:05 UTC | 1h 45m |
| 2026-07-10 | VND008E | TRS → LIN | Jul 10, 09:10 UTC | Jul 10, 09:45 UTC | 35m |
| 2026-07-10 | VND008E | TRN → TRS | Jul 10, 07:35 UTC | Jul 10, 08:15 UTC | 40m |
| 2026-07-10 | VND008E | - | Jul 10, 01:30 UTC | Jul 10, 02:15 UTC | 45m |
| 2026-07-10 | VND008E | - | Jul 10, 00:05 UTC | Jul 10, 00:40 UTC | 35m |
| 2026-07-04 | VND008E | - | Jul 4, 12:50 UTC | Jul 4, 13:25 UTC | 35m |
| 2026-07-04 | VND008E | LIN → GVA | Jul 4, 03:50 UTC | Jul 4, 04:30 UTC | 40m |
| 2026-07-03 | VND008E | - | Jul 3, 12:35 UTC | Jul 3, 13:10 UTC | 35m |
| 2026-07-03 | VND008E | PEG → TRS | Jul 3, 11:10 UTC | Jul 3, 11:45 UTC | 35m |
| 2026-07-03 | VND008E | TRS → PEG | Jul 3, 05:10 UTC | Jul 3, 05:45 UTC | 35m |
| 2026-07-03 | VND008E | LIN → TRS | Jul 3, 03:45 UTC | Jul 3, 04:15 UTC | 30m |
| 2026-07-02 | VND008E | - | Jul 2, 14:50 UTC | Jul 2, 15:55 UTC | 1h 5m |
| 2026-07-02 | VND008E | - | Jul 2, 13:30 UTC | Jul 2, 14:05 UTC | 35m |
| 2026-07-02 | VND008E | - | Jul 2, 06:00 UTC | Jul 2, 06:45 UTC | 45m |
| 2026-07-02 | VND008E | - | Jul 2, 03:45 UTC | Jul 2, 05:00 UTC | 1h 15m |
| 2026-07-01 | VND008E | - | Jul 1, 02:10 UTC | Jul 1, 02:25 UTC | 15m |
| 2026-07-01 | VND008E | - | Jul 1, 00:30 UTC | Jul 1, 01:10 UTC | 40m |
| 2026-06-30 | VND008E | LIN → CIA | Jun 30, 23:05 UTC | Jun 30, 23:55 UTC | 50m |
| 2026-06-26 | VND008E | - | Jun 26, 14:05 UTC | Jun 26, 14:50 UTC | 45m |
| 2026-06-04 | VND008E | - | Jun 4, 04:50 UTC | Jun 4, 06:25 UTC | 1h 35m |
| 2026-06-03 | VND008E | - | Jun 3, 22:30 UTC | Jun 3, 23:50 UTC | 1h 20m |
| 2026-06-03 | VND008E | - | Jun 3, 07:10 UTC | Jun 3, 07:45 UTC | 35m |
| 2026-06-02 | VND008E | - | Jun 2, 09:35 UTC | Jun 2, 10:55 UTC | 1h 20m |
| 2026-06-02 | VND008E | - | Jun 2, 02:15 UTC | Jun 2, 03:30 UTC | 1h 15m |
| 2026-06-02 | VND008E | - | Jun 2, 00:50 UTC | Jun 2, 01:15 UTC | 25m |
| 2026-05-25 | VND008E | - | May 25, 11:50 UTC | May 25, 13:40 UTC | 1h 50m |
| 2026-05-25 | VND008E | - | May 25, 02:05 UTC | May 25, 03:05 UTC | 1h 0m |
| 2026-05-24 | VND008E | - | May 24, 12:55 UTC | May 24, 13:15 UTC | 20m |
| 2026-05-24 | VND008E | - | May 24, 11:25 UTC | May 24, 12:25 UTC | 1h 0m |
| 2026-05-24 | VND008E | - | May 24, 04:40 UTC | May 24, 05:40 UTC | 1h 0m |
| 2026-05-24 | VND008E | LIN → TRN | May 24, 03:40 UTC | May 24, 04:00 UTC | 20m |
| 2026-05-23 | VND008E | LIN → LIN | May 23, 04:20 UTC | May 23, 06:05 UTC | 1h 45m |
| 2026-05-22 | VND008E | - | May 22, 07:45 UTC | May 22, 09:00 UTC | 1h 15m |
| 2026-05-22 | VND008E | - | May 22, 05:50 UTC | May 22, 06:40 UTC | 50m |
| 2026-05-22 | VND008E | - | May 22, 00:05 UTC | May 22, 01:15 UTC | 1h 10m |
| 2026-05-21 | VND008E | - | May 21, 22:15 UTC | May 21, 22:50 UTC | 35m |
| 2026-05-20 | VND008E | - | May 20, 11:10 UTC | May 20, 13:25 UTC | 2h 15m |
| 2026-05-19 | VND008E | - | May 19, 22:50 UTC | May 20, 01:25 UTC | 2h 35m |
| 2026-05-19 | VND008E | - | May 19, 20:55 UTC | May 19, 22:00 UTC | 1h 5m |
| 2026-05-17 | VND008E | - | May 17, 04:35 UTC | May 17, 05:00 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.
Prefer a tail-number view? See the I-AVNE page for operator, model, and routing details .