sensors Mode-S transponder
4D20D7
ICAO 24-bit transponder address · allocated to Malta
Currently assigned to 9H-VJL · BOMBARDIER BD-700 Global 6000/6500
- Hex
- 4D20D7
- Octal
- 23220327
- Decimal
- 5,054,679
- Country
- MT
- Tail
- 9H-VJL
- Type
- GLEX
- Flights observed
- 99
- Distinct callsigns
- 6
- Country
- MT
- Last broadcast
- Jul 26, 16:00 UTC
Last known position
Country allocation
The ICAO 24-bit address 4D20D7 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 6 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | VJT842 | - | Jul 26, 13:40 UTC | Jul 26, 16:00 UTC | 2h 20m |
| 2026-07-25 | VJT842 | - | Jul 25, 16:35 UTC | Jul 25, 17:00 UTC | 25m |
| 2026-07-25 | VJT842 | - | Jul 25, 08:00 UTC | Jul 25, 09:35 UTC | 1h 35m |
| 2026-07-24 | VJT842 | - | Jul 24, 15:45 UTC | Jul 24, 17:00 UTC | 1h 15m |
| 2026-07-20 | VJT842 | - | Jul 20, 11:35 UTC | Jul 20, 14:05 UTC | 2h 30m |
| 2026-07-20 | VJT842 | - | Jul 20, 08:20 UTC | Jul 20, 10:05 UTC | 1h 45m |
| 2026-07-20 | VJT842 | NCE → LBG | Jul 20, 06:05 UTC | Jul 20, 07:20 UTC | 1h 15m |
| 2026-07-19 | VJT842 | - | Jul 19, 01:05 UTC | Jul 19, 02:05 UTC | 1h 0m |
| 2026-07-18 | VJT842 | - | Jul 18, 16:35 UTC | Jul 18, 23:30 UTC | 6h 55m |
| 2026-07-17 | VJT842 | VLC → TEB | Jul 17, 09:40 UTC | Jul 17, 17:30 UTC | 7h 50m |
| 2026-07-16 | VJT842 | - | Jul 16, 13:00 UTC | Jul 16, 14:00 UTC | 1h 0m |
| 2026-07-14 | VJT842 | - | Jul 14, 07:15 UTC | Jul 14, 08:10 UTC | 55m |
| 2026-07-13 | VJT842 | - | Jul 13, 09:00 UTC | Jul 13, 11:15 UTC | 2h 15m |
| 2026-06-28 | VJT842 | - | Jun 28, 15:34 UTC | Jun 28, 18:14 UTC | 2h 40m |
| 2026-06-28 | VJT842 | - | Jun 28, 09:15 UTC | Jun 28, 13:45 UTC | 4h 30m |
| 2026-06-27 | VJT842 | - | Jun 27, 06:35 UTC | Jun 27, 08:39 UTC | 2h 5m |
| 2026-06-26 | VJT167 | - | Jun 26, 18:29 UTC | Jun 26, 18:49 UTC | 20m |
| 2026-06-26 | VJT167 | - | Jun 26, 15:39 UTC | Jun 26, 16:54 UTC | 1h 15m |
| 2026-06-26 | VJT167 | - | Jun 26, 13:34 UTC | Jun 26, 13:49 UTC | 15m |
| 2026-06-26 | VJT167 | - | Jun 26, 04:00 UTC | Jun 26, 10:55 UTC | 6h 55m |
| 2026-06-21 | VJT842 | - | Jun 21, 08:54 UTC | Jun 21, 09:29 UTC | 35m |
| 2026-06-20 | VJT186 | - | Jun 20, 06:14 UTC | Jun 20, 07:00 UTC | 45m |
| 2026-06-19 | VJT186 | - | Jun 19, 07:54 UTC | Jun 19, 08:14 UTC | 20m |
| 2026-06-18 | VJT186 | - | Jun 18, 21:25 UTC | Jun 19, 04:39 UTC | 7h 14m |
| 2026-06-18 | VJT842 | - | Jun 18, 18:40 UTC | Jun 18, 19:35 UTC | 55m |
| 2026-06-17 | VJT842 | - | Jun 17, 22:30 UTC | Jun 17, 23:25 UTC | 55m |
| 2026-06-17 | VJT842 | - | Jun 17, 15:46 UTC | Jun 17, 21:45 UTC | 6h 0m |
| 2026-06-17 | VJT842 | DWC → DWC | Jun 17, 14:55 UTC | Jun 17, 15:05 UTC | 10m |
| 2026-06-11 | VJT842 | - | Jun 11, 09:05 UTC | Jun 11, 15:35 UTC | 6h 30m |
| 2026-06-11 | VJT842 | BQH → LTN | Jun 11, 06:50 UTC | Jun 11, 07:15 UTC | 25m |
| 2026-06-09 | VJT842 | YYZ → BQH | Jun 9, 01:40 UTC | Jun 9, 08:45 UTC | 7h 5m |
| 2026-06-08 | VJT842 | BUF → YYZ | Jun 8, 02:55 UTC | Jun 8, 03:10 UTC | 15m |
| 2026-06-07 | VJT842 | ZRH → BUF | Jun 7, 17:35 UTC | Jun 8, 01:25 UTC | 7h 50m |
| 2026-06-06 | VJT842 | NCE → ZRH | Jun 6, 04:20 UTC | Jun 6, 05:05 UTC | 45m |
| 2026-06-05 | VJT842 | - | Jun 5, 13:40 UTC | Jun 6, 03:20 UTC | 13h 40m |
| 2026-06-01 | VJT842 | - | Jun 1, 17:55 UTC | Jun 1, 19:55 UTC | 2h 0m |
| 2026-06-01 | VJT842 | LBG → TBS | Jun 1, 12:45 UTC | Jun 1, 16:50 UTC | 4h 5m |
| 2026-05-31 | VJT842 | - | May 31, 15:05 UTC | May 31, 16:00 UTC | 55m |
| 2026-05-31 | VJT842 | - | May 31, 12:00 UTC | May 31, 13:55 UTC | 1h 55m |
| 2026-05-30 | VJT842 | - | May 30, 22:30 UTC | May 30, 23:10 UTC | 40m |
| 2026-05-30 | VJT842 | - | May 30, 18:55 UTC | May 30, 20:45 UTC | 1h 50m |
| 2026-05-30 | VJT842 | EMA → FAB | May 30, 16:15 UTC | May 30, 16:45 UTC | 30m |
| 2026-05-29 | VJT842 | - | May 29, 12:35 UTC | May 29, 14:40 UTC | 2h 5m |
| 2026-05-29 | VJT842 | - | May 29, 08:05 UTC | May 29, 10:00 UTC | 1h 55m |
| 2026-05-28 | VJT842 | DEN → LTN | May 28, 18:45 UTC | May 29, 06:35 UTC | 11h 50m |
| 2026-05-27 | VJT842 | EDI → DEN | May 27, 12:05 UTC | May 27, 20:35 UTC | 8h 30m |
| 2026-05-27 | VJT842 | LTN → EDI | May 27, 07:55 UTC | May 27, 08:45 UTC | 50m |
| 2026-05-26 | VJT842 | - | May 26, 13:19 UTC | May 26, 15:35 UTC | 2h 15m |
| 2026-05-25 | VJT842 | - | May 25, 09:35 UTC | May 25, 11:55 UTC | 2h 20m |
| 2026-05-25 | VJT842 | NCE → LTN | May 25, 06:00 UTC | May 25, 07:40 UTC | 1h 40m |
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-VJL page for operator, model, and routing details .