sensors Mode-S transponder
4D20D8
ICAO 24-bit transponder address · allocated to Malta
Currently assigned to 9H-VJK · BOMBARDIER BD-700 Global 6000/6500
- Hex
- 4D20D8
- Octal
- 23220330
- Decimal
- 5,054,680
- Country
- MT
- Tail
- 9H-VJK
- Type
- GLEX
- Flights observed
- 104
- Distinct callsigns
- 7
- Country
- MT
- Last broadcast
- 17h ago
Last known position
Country allocation
The ICAO 24-bit address 4D20D8 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-07-17 | VJT242 | - | Jul 17, 06:15 UTC | Jul 17, 08:59 UTC | 2h 45m |
| 2026-07-17 | VJT836 | - | Jul 17, 03:30 UTC | Jul 17, 04:10 UTC | 40m |
| 2026-07-16 | VJT836 | - | Jul 16, 04:30 UTC | Jul 17, 03:59 UTC | 23h 30m |
| 2026-07-15 | VJT836 | - | Jul 15, 20:15 UTC | Jul 16, 04:30 UTC | 8h 15m |
| 2026-07-15 | VJT836 | - | Jul 15, 09:50 UTC | Jul 15, 11:15 UTC | 1h 25m |
| 2026-07-14 | VJT836 | - | Jul 14, 23:25 UTC | Jul 15, 08:25 UTC | 9h 0m |
| 2026-07-13 | VJT836 | - | Jul 13, 14:05 UTC | Jul 13, 16:20 UTC | 2h 15m |
| 2026-07-12 | VJT836 | BQH → TEB | Jul 12, 20:25 UTC | Jul 13, 03:20 UTC | 6h 55m |
| 2026-07-12 | VJT836 | EDI → BQH | Jul 12, 12:55 UTC | Jul 12, 14:15 UTC | 1h 20m |
| 2026-07-12 | VJT836 | - | Jul 12, 06:45 UTC | Jul 12, 11:30 UTC | 4h 45m |
| 2026-07-12 | VJT836 | - | Jul 12, 01:25 UTC | Jul 12, 06:35 UTC | 5h 10m |
| 2026-07-11 | VJT836 | - | Jul 11, 23:15 UTC | Jul 12, 00:01 UTC | 45m |
| 2026-07-09 | VJT836 | - | Jul 9, 07:30 UTC | Jul 9, 17:15 UTC | 9h 45m |
| 2026-07-08 | VJT836 | - | Jul 8, 16:25 UTC | Jul 9, 06:15 UTC | 13h 50m |
| 2026-07-08 | VJT836 | - | Jul 8, 08:05 UTC | Jul 9, 06:15 UTC | 22h 10m |
| 2026-07-08 | VJT836 | - | Jul 8, 06:10 UTC | Jul 9, 06:00 UTC | 23h 50m |
| 2026-07-07 | VJT836 | - | Jul 7, 12:20 UTC | Jul 7, 13:45 UTC | 1h 25m |
| 2026-07-06 | VJT836 | - | Jul 6, 01:15 UTC | Jul 6, 09:50 UTC | 8h 35m |
| 2026-07-05 | VJT836 | - | Jul 5, 22:35 UTC | Jul 6, 00:15 UTC | 1h 40m |
| 2026-07-03 | VJT836 | - | Jul 3, 19:20 UTC | Jul 3, 19:30 UTC | 10m |
| 2026-07-03 | VJT836 | - | Jul 3, 06:45 UTC | Jul 3, 15:35 UTC | 8h 50m |
| 2026-07-02 | VJT836 | MLA → LBG | Jul 2, 13:40 UTC | Jul 2, 16:00 UTC | 2h 20m |
| 2026-07-01 | VJT836 | - | Jul 1, 15:10 UTC | Jul 1, 16:50 UTC | 1h 40m |
| 2026-07-01 | VJT836 | - | Jul 1, 10:25 UTC | Jul 1, 12:50 UTC | 2h 25m |
| 2026-06-27 | VJT836 | - | Jun 27, 07:59 UTC | Jun 27, 10:10 UTC | 2h 10m |
| 2026-06-25 | VJT836 | - | Jun 25, 10:20 UTC | Jun 25, 16:20 UTC | 6h 0m |
| 2026-06-25 | VJT836 | ACH → NCE | Jun 25, 07:09 UTC | Jun 25, 07:59 UTC | 50m |
| 2026-06-24 | VJT277 | BOM → ACH | Jun 24, 05:44 UTC | Jun 24, 14:09 UTC | 8h 25m |
| 2026-06-23 | VJT277 | - | Jun 23, 13:19 UTC | Jun 23, 16:05 UTC | 2h 45m |
| 2026-06-23 | VJT836 | ATH → DWC | Jun 23, 07:49 UTC | Jun 23, 11:59 UTC | 4h 10m |
| 2026-06-21 | VJT836 | - | Jun 21, 19:39 UTC | Jun 21, 20:34 UTC | 55m |
| 2026-06-21 | VJT836 | - | Jun 21, 16:34 UTC | Jun 21, 18:14 UTC | 1h 40m |
| 2026-06-21 | VJT836 | - | Jun 21, 11:20 UTC | Jun 21, 13:34 UTC | 2h 15m |
| 2026-06-18 | VJT836 | - | Jun 18, 20:45 UTC | Jun 18, 21:25 UTC | 40m |
| 2026-06-18 | VJT836 | - | Jun 18, 08:55 UTC | Jun 18, 19:05 UTC | 10h 10m |
| 2026-06-16 | VJT836 | - | Jun 16, 21:25 UTC | Jun 17, 01:35 UTC | 4h 10m |
| 2026-06-15 | VJT696W | - | Jun 15, 08:20 UTC | Jun 15, 17:40 UTC | 9h 20m |
| 2026-06-14 | VJT836 | - | Jun 14, 15:10 UTC | Jun 14, 16:05 UTC | 55m |
| 2026-06-14 | VJT836 | - | Jun 14, 12:35 UTC | Jun 14, 13:35 UTC | 1h 0m |
| 2026-06-13 | VJT836 | - | Jun 13, 20:35 UTC | Jun 14, 04:40 UTC | 8h 5m |
| 2026-06-13 | VJT836 | - | Jun 13, 03:30 UTC | Jun 13, 03:50 UTC | 20m |
| 2026-06-13 | VJT836 | - | Jun 13, 00:40 UTC | Jun 13, 01:15 UTC | 35m |
| 2026-06-11 | VJT836 | RSW → TEB | Jun 11, 20:35 UTC | Jun 11, 22:55 UTC | 2h 20m |
| 2026-06-11 | VJT836 | - | Jun 11, 10:25 UTC | Jun 11, 19:20 UTC | 8h 55m |
| 2026-05-31 | VJT836 | - | May 31, 14:10 UTC | May 31, 17:45 UTC | 3h 35m |
| 2026-05-31 | VJT836 | BQH → ATH | May 31, 09:25 UTC | May 31, 12:20 UTC | 2h 55m |
| 2026-05-30 | VJT836 | RIX → BQH | May 30, 15:45 UTC | May 30, 18:00 UTC | 2h 15m |
| 2026-05-30 | VJT836 | - | May 30, 07:35 UTC | May 30, 14:30 UTC | 6h 55m |
| 2026-05-29 | VJT836 | - | May 29, 16:05 UTC | May 30, 14:30 UTC | 22h 25m |
| 2026-05-29 | VJT836 | - | May 29, 15:25 UTC | May 30, 14:00 UTC | 22h 35m |
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-VJK page for operator, model, and routing details .