sensors Mode-S transponder
4D20E3
ICAO 24-bit transponder address · allocated to Malta
Currently assigned to 9H-VFH · BOMBARDIER CL-600 Challenger
- Hex
- 4D20E3
- Octal
- 23220343
- Decimal
- 5,054,691
- Country
- MT
- Tail
- 9H-VFH
- Type
- CL60
- Flights observed
- 66
- Distinct callsigns
- 6
- Country
- MT
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 4D20E3 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-06-01 | VJT534 | ZRH → FAB | Jun 1, 12:20 UTC | Jun 1, 13:45 UTC | 1h 25m |
| 2026-05-31 | VJT534 | - | May 31, 14:50 UTC | May 31, 16:10 UTC | 1h 20m |
| 2026-05-31 | VJT685R | VIE → FAB | May 31, 09:10 UTC | May 31, 11:15 UTC | 2h 5m |
| 2026-05-30 | VJT446Y | BUD → VIE | May 30, 14:40 UTC | May 30, 15:05 UTC | 25m |
| 2026-05-30 | VJT446Y | - | May 30, 10:55 UTC | May 30, 12:50 UTC | 1h 55m |
| 2026-05-30 | VJT534 | - | May 30, 07:00 UTC | May 30, 09:50 UTC | 2h 50m |
| 2026-05-29 | VJT754 | BMA → CPH | May 29, 08:30 UTC | May 29, 09:20 UTC | 50m |
| 2026-05-29 | VJT754 | - | May 29, 05:30 UTC | May 29, 07:10 UTC | 1h 40m |
| 2026-05-28 | VJT534 | - | May 28, 07:35 UTC | May 28, 08:20 UTC | 45m |
| 2026-05-28 | VJT534 | - | May 28, 04:30 UTC | May 28, 06:20 UTC | 1h 50m |
| 2026-05-28 | VJT534 | - | May 28, 02:00 UTC | May 28, 03:15 UTC | 1h 15m |
| 2026-05-18 | VJT534 | - | May 18, 03:25 UTC | May 18, 03:45 UTC | 20m |
| 2026-05-17 | VJT534 | - | May 17, 07:30 UTC | May 17, 08:45 UTC | 1h 15m |
| 2026-05-15 | VJT534 | - | May 15, 08:15 UTC | May 15, 16:30 UTC | 8h 14m |
| 2026-05-14 | VJT534 | - | May 14, 11:25 UTC | May 14, 11:55 UTC | 30m |
| 2026-05-13 | VJT534 | - | May 13, 15:00 UTC | May 13, 17:20 UTC | 2h 20m |
| 2026-05-13 | VJT534 | BOD → GVA | May 13, 10:50 UTC | May 13, 11:55 UTC | 1h 5m |
| 2026-05-13 | VJT534 | - | May 13, 08:30 UTC | May 13, 09:45 UTC | 1h 15m |
| 2026-05-13 | VJT534 | OBF → LUX | May 13, 06:35 UTC | May 13, 07:30 UTC | 55m |
| 2026-05-12 | VJT534 | - | May 12, 16:40 UTC | May 12, 18:00 UTC | 1h 20m |
| 2026-05-12 | VJT534 | - | May 12, 11:45 UTC | May 12, 13:30 UTC | 1h 45m |
| 2026-05-12 | VJT534 | - | May 12, 09:30 UTC | May 12, 10:20 UTC | 50m |
| 2026-05-11 | VJT534 | - | May 11, 14:40 UTC | May 11, 15:15 UTC | 35m |
| 2026-05-11 | VJT534 | - | May 11, 11:30 UTC | May 11, 12:40 UTC | 1h 10m |
| 2026-05-11 | VJT534 | BOD → FAB | May 11, 08:40 UTC | May 11, 09:55 UTC | 1h 15m |
| 2026-05-10 | VJT534 | CIA → BOD | May 10, 19:05 UTC | May 10, 20:50 UTC | 1h 45m |
| 2026-05-10 | VJT534 | - | May 10, 13:05 UTC | May 10, 15:05 UTC | 2h 0m |
| 2026-05-09 | VJT534 | - | May 9, 09:55 UTC | May 9, 11:25 UTC | 1h 30m |
| 2026-05-06 | VJT534 | SZG → OBF | May 6, 09:20 UTC | May 6, 09:45 UTC | 25m |
| 2026-05-06 | VJT534 | STR → SZG | May 6, 07:25 UTC | May 6, 08:01 UTC | 35m |
| 2026-05-04 | VJT534 | VCE → STR | May 4, 14:30 UTC | May 4, 15:15 UTC | 45m |
| 2026-05-04 | VJT534 | - | May 4, 10:05 UTC | May 4, 13:20 UTC | 3h 15m |
| 2026-05-04 | VJT141 | - | May 4, 04:05 UTC | May 4, 07:45 UTC | 3h 40m |
| 2026-05-04 | VJT141 | - | May 4, 01:50 UTC | May 4, 02:04 UTC | 15m |
| 2026-05-03 | VJT141 | - | May 3, 14:50 UTC | May 3, 15:15 UTC | 25m |
| 2026-05-03 | VJT141 | - | May 3, 11:15 UTC | May 3, 13:30 UTC | 2h 15m |
| 2026-05-03 | VJT141 | - | May 3, 09:00 UTC | May 3, 09:10 UTC | 10m |
| 2026-05-03 | VJT534 | - | May 3, 06:20 UTC | May 3, 06:45 UTC | 25m |
| 2026-04-30 | VJT534 | - | Apr 30, 10:50 UTC | Apr 30, 11:10 UTC | 20m |
| 2026-04-30 | VJT534 | - | Apr 30, 08:35 UTC | Apr 30, 09:10 UTC | 35m |
| 2026-04-30 | VJT534 | - | Apr 30, 02:40 UTC | Apr 30, 08:00 UTC | 5h 20m |
| 2026-04-29 | VJT534 | - | Apr 29, 08:15 UTC | Apr 29, 08:45 UTC | 30m |
| 2026-04-29 | VJT534 | - | Apr 29, 07:24 UTC | Apr 29, 07:35 UTC | 10m |
| 2026-04-28 | VJT534 | - | Apr 28, 09:35 UTC | Apr 28, 09:50 UTC | 15m |
| 2026-04-28 | VJT534 | - | Apr 28, 08:15 UTC | Apr 28, 08:50 UTC | 35m |
| 2026-04-28 | VJT534 | - | Apr 28, 05:55 UTC | Apr 28, 06:15 UTC | 20m |
| 2026-04-28 | VJT534 | - | Apr 28, 03:40 UTC | Apr 28, 04:15 UTC | 35m |
| 2026-04-26 | VJT534 | - | Apr 26, 04:50 UTC | Apr 26, 08:00 UTC | 3h 10m |
| 2026-04-23 | VJT534 | - | Apr 23, 09:50 UTC | Apr 23, 10:20 UTC | 30m |
| 2026-04-23 | VJT534 | - | Apr 23, 06:50 UTC | Apr 23, 08:05 UTC | 1h 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-VFH page for operator, model, and routing details .