sensors Mode-S transponder
4D20FE
ICAO 24-bit transponder address · allocated to Malta
Currently assigned to 9H-VJZ · BOMBARDIER BD-700 Global 6000/6500
- Hex
- 4D20FE
- Octal
- 23220376
- Decimal
- 5,054,718
- Country
- MT
- Tail
- 9H-VJZ
- Type
- GLEX
- Flights observed
- 59
- Distinct callsigns
- 3
- Country
- MT
- Last broadcast
- 3h ago
Last known position
Country allocation
The ICAO 24-bit address 4D20FE 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 3 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | VJT981 | - | May 30, 07:30 UTC | May 30, 08:05 UTC | 35m |
| 2026-05-29 | VJT981 | - | May 29, 10:20 UTC | May 29, 11:10 UTC | 50m |
| 2026-05-28 | VJT981 | - | May 28, 08:30 UTC | May 28, 09:50 UTC | 1h 20m |
| 2026-05-27 | VJT981 | - | May 27, 11:15 UTC | May 27, 13:05 UTC | 1h 50m |
| 2026-05-27 | VJT981 | - | May 27, 07:30 UTC | May 27, 09:40 UTC | 2h 10m |
| 2026-05-25 | VJT981 | - | May 25, 22:34 UTC | May 26, 08:04 UTC | 9h 30m |
| 2026-05-25 | VJT981 | - | May 25, 20:50 UTC | May 25, 21:19 UTC | 30m |
| 2026-05-23 | VJT981 | - | May 23, 11:55 UTC | May 23, 22:10 UTC | 10h 16m |
| 2026-05-22 | VJT981 | - | May 22, 18:25 UTC | May 22, 20:15 UTC | 1h 50m |
| 2026-05-17 | VJT981 | VNY → FAB | May 17, 02:50 UTC | May 17, 12:55 UTC | 10h 5m |
| 2026-05-15 | VJT981 | - | May 15, 23:30 UTC | May 15, 23:45 UTC | 15m |
| 2026-05-15 | VJT981 | - | May 15, 17:10 UTC | May 15, 22:15 UTC | 5h 5m |
| 2026-05-15 | VJT981 | YYZ → YUL | May 15, 15:00 UTC | May 15, 16:05 UTC | 1h 5m |
| 2026-05-14 | VJT981 | VCE → YYZ | May 14, 11:55 UTC | May 14, 20:15 UTC | 8h 20m |
| 2026-05-14 | VJT981 | - | May 14, 09:40 UTC | May 14, 10:25 UTC | 45m |
| 2026-05-13 | VJT981 | PRG → NCE | May 13, 13:50 UTC | May 13, 15:25 UTC | 1h 35m |
| 2026-05-12 | VJT981 | BTS → PRG | May 12, 16:40 UTC | May 12, 17:20 UTC | 40m |
| 2026-05-12 | VJT981 | - | May 12, 13:20 UTC | May 12, 16:00 UTC | 2h 40m |
| 2026-05-11 | VJT981 | - | May 11, 11:55 UTC | May 11, 14:20 UTC | 2h 25m |
| 2026-05-11 | VJT981 | PRG → BTS | May 11, 10:25 UTC | May 11, 11:00 UTC | 35m |
| 2026-05-10 | VJT981 | - | May 10, 18:15 UTC | May 10, 19:24 UTC | 1h 10m |
| 2026-05-10 | VJT981 | - | May 10, 16:30 UTC | May 10, 17:15 UTC | 45m |
| 2026-05-08 | VJT981 | - | May 8, 15:00 UTC | May 8, 19:05 UTC | 4h 5m |
| 2026-05-06 | VJT981 | - | May 6, 15:20 UTC | May 6, 18:45 UTC | 3h 24m |
| 2026-05-06 | VJT981 | RHO → TLV | May 6, 12:50 UTC | May 6, 14:05 UTC | 1h 15m |
| 2026-05-06 | VJT981 | - | May 6, 10:10 UTC | May 6, 11:05 UTC | 55m |
| 2026-05-05 | VJT981 | - | May 5, 12:05 UTC | May 5, 14:00 UTC | 1h 55m |
| 2026-05-05 | VJT981 | - | May 5, 05:25 UTC | May 5, 11:10 UTC | 5h 45m |
| 2026-05-05 | VJT981 | - | May 5, 00:25 UTC | May 5, 05:20 UTC | 4h 55m |
| 2026-05-03 | VJT981 | - | May 3, 18:25 UTC | May 3, 21:29 UTC | 3h 5m |
| 2026-05-02 | VJT981 | - | May 2, 14:20 UTC | May 2, 23:50 UTC | 9h 30m |
| 2026-05-01 | VJT981 | - | May 1, 12:30 UTC | May 1, 13:55 UTC | 1h 25m |
| 2026-05-01 | VJT685R | - | May 1, 10:10 UTC | May 1, 11:45 UTC | 1h 35m |
| 2026-04-27 | VJT908W | - | Apr 27, 13:20 UTC | Apr 27, 14:55 UTC | 1h 35m |
| 2026-04-27 | VJT981 | GVA → KRS | Apr 27, 09:40 UTC | Apr 27, 11:25 UTC | 1h 45m |
| 2026-04-26 | VJT981 | - | Apr 26, 17:25 UTC | Apr 26, 18:40 UTC | 1h 15m |
| 2026-04-25 | VJT981 | TEB → LTN | Apr 25, 13:40 UTC | Apr 25, 20:15 UTC | 6h 35m |
| 2026-04-24 | VJT981 | - | Apr 24, 14:45 UTC | Apr 24, 22:30 UTC | 7h 45m |
| 2026-04-24 | VJT981 | - | Apr 24, 11:00 UTC | Apr 24, 12:40 UTC | 1h 40m |
| 2026-04-22 | VJT981 | - | Apr 22, 15:20 UTC | Apr 22, 15:50 UTC | 30m |
| 2026-04-22 | VJT981 | - | Apr 22, 11:35 UTC | Apr 22, 14:05 UTC | 2h 30m |
| 2026-04-21 | VJT981 | - | Apr 21, 11:55 UTC | Apr 21, 14:10 UTC | 2h 15m |
| 2026-04-21 | VJT981 | - | Apr 21, 09:45 UTC | Apr 21, 10:35 UTC | 50m |
| 2026-04-18 | VJT981 | - | Apr 18, 23:55 UTC | Apr 19, 10:40 UTC | 10h 45m |
| 2026-04-17 | VJT981 | - | Apr 17, 11:20 UTC | Apr 17, 12:10 UTC | 50m |
| 2026-04-17 | VJT981 | - | Apr 17, 09:20 UTC | Apr 17, 09:45 UTC | 25m |
| 2026-04-17 | VJT981 | - | Apr 17, 07:20 UTC | Apr 17, 09:15 UTC | 1h 55m |
| 2026-04-17 | VJT981 | - | Apr 17, 06:25 UTC | Apr 17, 07:15 UTC | 50m |
| 2026-04-16 | VJT981 | - | Apr 16, 22:34 UTC | Apr 16, 23:10 UTC | 35m |
| 2026-04-15 | VJT981 | - | Apr 15, 19:05 UTC | Apr 15, 19:20 UTC | 15m |
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-VJZ page for operator, model, and routing details .