sensors Mode-S transponder
4D20F9
ICAO 24-bit transponder address · allocated to Malta
Currently assigned to 9H-VJQ · BOMBARDIER BD-700 Global 6000/6500
- Hex
- 4D20F9
- Octal
- 23220371
- Decimal
- 5,054,713
- Country
- MT
- Tail
- 9H-VJQ
- Type
- GLEX
- Flights observed
- 56
- Distinct callsigns
- 7
- Country
- MT
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 4D20F9 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 7 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-28 | VJT809 | - | May 28, 11:10 UTC | May 28, 13:20 UTC | 2h 10m |
| 2026-05-27 | VJT809 | - | May 27, 17:10 UTC | May 27, 20:00 UTC | 2h 50m |
| 2026-05-26 | VJT809 | - | May 26, 13:10 UTC | May 26, 15:20 UTC | 2h 10m |
| 2026-05-25 | VJT809 | - | May 25, 12:15 UTC | May 25, 20:19 UTC | 8h 5m |
| 2026-05-24 | VJT809 | BOS → MLB | May 24, 16:40 UTC | May 24, 19:25 UTC | 2h 45m |
| 2026-05-23 | VJT809 | - | May 23, 14:55 UTC | May 23, 21:15 UTC | 6h 20m |
| 2026-05-23 | VJT809 | HKG → ANC | May 23, 03:40 UTC | May 23, 13:15 UTC | 9h 35m |
| 2026-05-22 | VJT809 | - | May 22, 06:25 UTC | May 22, 06:40 UTC | 15m |
| 2026-05-22 | VJT809 | - | May 22, 03:35 UTC | May 22, 05:50 UTC | 2h 15m |
| 2026-05-21 | WZZ32FV | VNO → KUT | May 21, 17:25 UTC | May 21, 17:40 UTC | 15m |
| 2026-05-15 | VJT809 | - | May 15, 03:00 UTC | May 15, 09:20 UTC | 6h 20m |
| 2026-05-14 | VJT809 | - | May 14, 08:20 UTC | May 15, 03:25 UTC | 19h 5m |
| 2026-05-14 | VJT809 | - | May 14, 08:00 UTC | May 15, 03:25 UTC | 19h 25m |
| 2026-05-14 | VJT809 | - | May 14, 04:05 UTC | May 14, 06:25 UTC | 2h 20m |
| 2026-05-13 | VJT809 | - | May 13, 11:45 UTC | May 13, 13:55 UTC | 2h 10m |
| 2026-05-12 | VJT809 | - | May 12, 02:50 UTC | May 12, 03:05 UTC | 15m |
| 2026-05-11 | VJT809 | - | May 11, 08:05 UTC | May 11, 08:15 UTC | 10m |
| 2026-05-11 | VJT809 | - | May 11, 07:05 UTC | May 11, 07:20 UTC | 15m |
| 2026-05-10 | VJT809 | - | May 10, 11:00 UTC | May 11, 07:20 UTC | 20h 20m |
| 2026-05-10 | VJT809 | - | May 10, 03:25 UTC | May 10, 09:55 UTC | 6h 30m |
| 2026-05-08 | VJT809 | - | May 8, 20:25 UTC | May 9, 05:30 UTC | 9h 5m |
| 2026-05-08 | VJT809 | MEL → AKL | May 8, 01:09 UTC | May 8, 04:09 UTC | 3h 0m |
| 2026-05-06 | VJT809 | - | May 6, 01:20 UTC | May 6, 07:05 UTC | 5h 45m |
| 2026-05-05 | VJT809 | - | May 5, 10:05 UTC | May 5, 10:15 UTC | 10m |
| 2026-05-05 | VJT809 | - | May 5, 03:45 UTC | May 5, 06:05 UTC | 2h 20m |
| 2026-05-04 | VJT958T | - | May 4, 11:20 UTC | May 4, 11:30 UTC | 10m |
| 2026-05-04 | VJT958T | - | May 4, 06:25 UTC | May 4, 08:00 UTC | 1h 35m |
| 2026-05-03 | VJT268 | - | May 3, 10:25 UTC | May 3, 12:15 UTC | 1h 50m |
| 2026-05-03 | VJT268 | - | May 3, 06:55 UTC | May 3, 09:25 UTC | 2h 30m |
| 2026-05-01 | VJT809 | - | May 1, 12:00 UTC | May 1, 12:15 UTC | 15m |
| 2026-05-01 | VJT809 | - | May 1, 08:50 UTC | May 1, 09:25 UTC | 35m |
| 2026-04-30 | VJT269 | - | Apr 30, 05:10 UTC | Apr 30, 07:30 UTC | 2h 20m |
| 2026-04-30 | VJT269 | - | Apr 30, 02:50 UTC | Apr 30, 03:30 UTC | 40m |
| 2026-04-28 | VJT809 | - | Apr 28, 11:00 UTC | Apr 28, 15:45 UTC | 4h 45m |
| 2026-04-28 | VJT809 | - | Apr 28, 04:20 UTC | Apr 28, 08:55 UTC | 4h 35m |
| 2026-04-21 | VJT809 | ATH → ATH | Apr 21, 20:40 UTC | Apr 21, 20:50 UTC | 10m |
| 2026-04-21 | VJT809 | - | Apr 21, 19:10 UTC | Apr 21, 20:35 UTC | 1h 25m |
| 2026-04-21 | VJT298 | - | Apr 21, 10:35 UTC | Apr 21, 18:05 UTC | 7h 30m |
| 2026-04-20 | VJT269Z | - | Apr 20, 08:25 UTC | Apr 20, 12:00 UTC | 3h 35m |
| 2026-04-18 | VJT269Z | - | Apr 18, 02:50 UTC | Apr 18, 03:20 UTC | 30m |
| 2026-04-17 | VJT269Z | - | Apr 17, 21:25 UTC | Apr 17, 22:00 UTC | 35m |
| 2026-04-17 | VJT269Z | - | Apr 17, 20:05 UTC | Apr 17, 21:20 UTC | 1h 15m |
| 2026-04-17 | VJT809 | - | Apr 17, 16:55 UTC | Apr 17, 17:15 UTC | 20m |
| 2026-04-17 | VJT809 | - | Apr 17, 11:20 UTC | Apr 17, 12:00 UTC | 40m |
| 2026-04-17 | VJT809 | - | Apr 17, 11:00 UTC | Apr 17, 11:15 UTC | 15m |
| 2026-04-17 | VJT809 | - | Apr 17, 07:20 UTC | Apr 17, 09:10 UTC | 1h 50m |
| 2026-04-17 | VJT809 | - | Apr 17, 06:35 UTC | Apr 17, 07:15 UTC | 40m |
| 2026-04-17 | VJT809 | - | Apr 17, 01:20 UTC | Apr 17, 02:50 UTC | 1h 30m |
| 2026-04-15 | VJT809 | - | Apr 15, 02:55 UTC | Apr 15, 04:00 UTC | 1h 5m |
| 2026-04-15 | VJT809 | - | Apr 15, 02:00 UTC | Apr 15, 02:50 UTC | 50m |
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-VJQ page for operator, model, and routing details .