sensors Mode-S transponder
4D20F8
ICAO 24-bit transponder address · allocated to Malta
Currently assigned to 9H-VJP · BOMBARDIER BD-700 Global 6000/6500
- Hex
- 4D20F8
- Octal
- 23220370
- Decimal
- 5,054,712
- Country
- MT
- Tail
- 9H-VJP
- Type
- GLEX
- Flights observed
- 95
- Distinct callsigns
- 9
- Country
- MT
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 4D20F8 falls within the block assigned to Malta (MT) by ICAO Annex 10, Volume III. Every aircraft registered in Malta 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 9 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-16 | VJT895 | - | Jul 16, 12:14 UTC | Jul 16, 19:20 UTC | 7h 5m |
| 2026-07-15 | VJT895 | - | Jul 15, 11:55 UTC | Jul 15, 14:30 UTC | 2h 35m |
| 2026-07-15 | VJT895 | - | Jul 15, 06:35 UTC | Jul 15, 09:00 UTC | 2h 25m |
| 2026-07-14 | VJT895 | - | Jul 14, 07:30 UTC | Jul 14, 15:05 UTC | 7h 35m |
| 2026-07-13 | VJT285 | - | Jul 13, 10:15 UTC | Jul 13, 10:25 UTC | 10m |
| 2026-07-13 | VJT285 | - | Jul 13, 07:30 UTC | Jul 13, 08:45 UTC | 1h 15m |
| 2026-07-10 | VJT895 | - | Jul 10, 22:40 UTC | Jul 11, 07:15 UTC | 8h 35m |
| 2026-07-10 | VJT895 | HND → HKG | Jul 10, 06:20 UTC | Jul 10, 10:30 UTC | 4h 10m |
| 2026-07-09 | VJT294 | - | Jul 9, 05:45 UTC | Jul 9, 14:55 UTC | 9h 10m |
| 2026-07-08 | VJT895 | - | Jul 8, 03:50 UTC | Jul 8, 04:35 UTC | 45m |
| 2026-07-07 | VJT241 | - | Jul 7, 07:00 UTC | Jul 7, 12:40 UTC | 5h 40m |
| 2026-07-07 | VJT241 | - | Jul 7, 03:05 UTC | Jul 7, 05:10 UTC | 2h 5m |
| 2026-07-05 | VJT276 | - | Jul 5, 20:20 UTC | Jul 5, 20:55 UTC | 35m |
| 2026-07-05 | VJT276 | ZRH → BOM | Jul 5, 10:35 UTC | Jul 5, 19:00 UTC | 8h 25m |
| 2026-07-03 | VJT895 | - | Jul 3, 17:25 UTC | Jul 3, 19:00 UTC | 1h 35m |
| 2026-07-03 | VJT895 | - | Jul 3, 13:40 UTC | Jul 3, 16:40 UTC | 3h 0m |
| 2026-07-03 | VJT895 | - | Jul 3, 06:35 UTC | Jul 3, 12:05 UTC | 5h 30m |
| 2026-07-03 | VJT895 | - | Jul 3, 01:20 UTC | Jul 3, 01:35 UTC | 15m |
| 2026-07-02 | VJT216 | - | Jul 2, 07:35 UTC | Jul 2, 11:50 UTC | 4h 15m |
| 2026-06-29 | VJT895 | - | Jun 29, 18:49 UTC | Jun 30, 01:14 UTC | 6h 25m |
| 2026-06-29 | VJT895 | - | Jun 29, 06:34 UTC | Jun 29, 16:44 UTC | 10h 10m |
| 2026-06-28 | VJT895 | YVR → SAN | Jun 28, 13:29 UTC | Jun 28, 15:55 UTC | 2h 25m |
| 2026-06-27 | VJT895 | - | Jun 27, 07:10 UTC | Jun 27, 15:19 UTC | 8h 10m |
| 2026-06-27 | VJT895 | GMP → NRT | Jun 27, 02:55 UTC | Jun 27, 04:39 UTC | 1h 45m |
| 2026-06-26 | VJT895 | PUS → GMP | Jun 26, 04:14 UTC | Jun 26, 04:50 UTC | 35m |
| 2026-06-26 | VJT895 | HND → PUS | Jun 26, 01:24 UTC | Jun 26, 03:05 UTC | 1h 40m |
| 2026-06-25 | VJT895 | TSA → HND | Jun 25, 03:15 UTC | Jun 25, 05:50 UTC | 2h 35m |
| 2026-06-25 | VJT895 | - | Jun 25, 01:35 UTC | Jun 25, 01:59 UTC | 25m |
| 2026-06-24 | VJT895 | - | Jun 24, 16:19 UTC | Jun 25, 00:05 UTC | 7h 45m |
| 2026-06-23 | VJT170 | - | Jun 23, 15:19 UTC | Jun 23, 21:39 UTC | 6h 20m |
| 2026-06-22 | VJT895 | - | Jun 22, 12:10 UTC | Jun 22, 14:45 UTC | 2h 35m |
| 2026-06-21 | VJT369K | - | Jun 21, 07:29 UTC | Jun 21, 13:09 UTC | 5h 40m |
| 2026-06-21 | VJT895 | - | Jun 21, 04:10 UTC | Jun 21, 05:20 UTC | 1h 10m |
| 2026-06-16 | VJT895 | - | Jun 16, 08:00 UTC | Jun 16, 09:20 UTC | 1h 20m |
| 2026-06-16 | VJT895 | BOS → FAB | Jun 16, 00:45 UTC | Jun 16, 06:35 UTC | 5h 50m |
| 2026-06-15 | VJT895 | - | Jun 15, 22:20 UTC | Jun 15, 22:49 UTC | 30m |
| 2026-06-13 | VJT895 | - | Jun 13, 16:35 UTC | Jun 13, 18:05 UTC | 1h 30m |
| 2026-06-13 | VJT895 | - | Jun 13, 08:45 UTC | Jun 13, 15:55 UTC | 7h 10m |
| 2026-06-13 | VJT895 | - | Jun 13, 07:00 UTC | Jun 13, 07:25 UTC | 25m |
| 2026-06-11 | VJT288 | BOM → LTN | Jun 11, 20:55 UTC | Jun 12, 06:40 UTC | 9h 45m |
| 2026-06-11 | VJT288 | - | Jun 11, 18:15 UTC | Jun 11, 19:10 UTC | 55m |
| 2026-06-10 | VJT288 | - | Jun 10, 20:55 UTC | Jun 11, 19:10 UTC | 22h 15m |
| 2026-06-10 | VJT895 | - | Jun 10, 14:10 UTC | Jun 10, 21:30 UTC | 7h 20m |
| 2026-06-10 | VJT895 | - | Jun 10, 10:45 UTC | Jun 10, 11:45 UTC | 1h 0m |
| 2026-06-05 | VJT895 | - | Jun 5, 12:35 UTC | Jun 5, 17:15 UTC | 4h 40m |
| 2026-06-03 | VJT895 | - | Jun 3, 13:50 UTC | Jun 3, 20:20 UTC | 6h 30m |
| 2026-06-01 | VJT895 | - | Jun 1, 13:40 UTC | Jun 1, 20:45 UTC | 7h 5m |
| 2026-05-31 | VJT895 | - | May 31, 20:05 UTC | Jun 1, 20:00 UTC | 23h 55m |
| 2026-05-31 | VJT895 | - | May 31, 14:05 UTC | Jun 1, 13:50 UTC | 23h 45m |
| 2026-05-30 | VJT895 | - | May 30, 15:50 UTC | May 30, 18:50 UTC | 3h 0m |
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 9H-VJP page for operator, model, and routing details .