sensors Mode-S transponder
4D208A
ICAO 24-bit transponder address · allocated to Malta
Currently assigned to 9H-VJF · BOMBARDIER BD-700 Global 6000/6500
- Hex
- 4D208A
- Octal
- 23220212
- Decimal
- 5,054,602
- Country
- MT
- Tail
- 9H-VJF
- Type
- GLEX
- Flights observed
- 64
- Distinct callsigns
- 3
- Country
- MT
- Last broadcast
- 5h ago
Last known position
Country allocation
The ICAO 24-bit address 4D208A 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-06-02 | VJT754 | KGS → FAB | Jun 2, 16:50 UTC | Jun 2, 20:25 UTC | 3h 35m |
| 2026-06-02 | VJT754 | - | Jun 2, 14:05 UTC | Jun 2, 15:40 UTC | 1h 35m |
| 2026-06-01 | VJT754 | - | Jun 1, 16:35 UTC | Jun 2, 15:40 UTC | 23h 5m |
| 2026-06-01 | VJT754 | - | Jun 1, 14:35 UTC | Jun 2, 14:30 UTC | 23h 55m |
| 2026-06-01 | VJT754 | - | Jun 1, 11:35 UTC | Jun 1, 13:05 UTC | 1h 30m |
| 2026-05-31 | VJT754 | SEN → LTN | May 31, 18:45 UTC | May 31, 19:10 UTC | 25m |
| 2026-05-31 | VJT685R | - | May 31, 16:05 UTC | May 31, 18:00 UTC | 1h 55m |
| 2026-05-31 | VJT685R | - | May 31, 13:10 UTC | May 31, 15:10 UTC | 2h 0m |
| 2026-05-30 | VJT754 | - | May 30, 18:35 UTC | May 31, 01:11 UTC | 6h 36m |
| 2026-05-30 | VJT754 | - | May 30, 02:45 UTC | May 30, 05:35 UTC | 2h 50m |
| 2026-05-28 | VJT754 | - | May 28, 16:55 UTC | May 29, 01:55 UTC | 9h 0m |
| 2026-05-23 | VJT754 | IAD → FAB | May 23, 00:25 UTC | May 23, 07:10 UTC | 6h 44m |
| 2026-05-21 | VJT754 | - | May 21, 22:45 UTC | May 22, 00:30 UTC | 1h 45m |
| 2026-05-21 | VJT754 | - | May 21, 18:55 UTC | May 21, 21:00 UTC | 2h 5m |
| 2026-05-21 | VJT754 | - | May 21, 16:35 UTC | May 21, 17:05 UTC | 30m |
| 2026-05-20 | VJT754 | - | May 20, 14:15 UTC | May 21, 00:40 UTC | 10h 25m |
| 2026-05-20 | VJT754 | - | May 20, 09:10 UTC | May 20, 10:05 UTC | 55m |
| 2026-05-20 | VJT754 | BOS → GLA | May 20, 02:30 UTC | May 20, 08:00 UTC | 5h 31m |
| 2026-05-20 | VJT754 | - | May 20, 00:15 UTC | May 20, 00:55 UTC | 40m |
| 2026-05-19 | VJT754 | - | May 19, 13:40 UTC | May 19, 20:00 UTC | 6h 20m |
| 2026-05-19 | VJT754 | - | May 19, 11:20 UTC | May 19, 12:20 UTC | 1h 0m |
| 2026-05-17 | VJT129 | - | May 17, 17:40 UTC | May 18, 03:45 UTC | 10h 5m |
| 2026-05-17 | VJT129 | - | May 17, 15:35 UTC | May 17, 15:55 UTC | 20m |
| 2026-05-16 | VJT754 | GVA → BOM | May 16, 14:55 UTC | May 17, 00:30 UTC | 9h 35m |
| 2026-05-14 | VJT754 | - | May 14, 12:05 UTC | May 14, 13:15 UTC | 1h 10m |
| 2026-05-14 | VJT754 | - | May 14, 09:05 UTC | May 14, 11:01 UTC | 1h 55m |
| 2026-05-13 | VJT754 | - | May 13, 15:25 UTC | May 13, 17:05 UTC | 1h 40m |
| 2026-05-13 | VJT754 | - | May 13, 12:00 UTC | May 13, 14:15 UTC | 2h 15m |
| 2026-05-12 | VJT754 | - | May 12, 18:00 UTC | May 13, 10:35 UTC | 16h 35m |
| 2026-05-12 | VJT754 | - | May 12, 12:25 UTC | May 12, 16:15 UTC | 3h 50m |
| 2026-05-11 | VJT754 | - | May 11, 12:35 UTC | May 12, 12:30 UTC | 23h 56m |
| 2026-05-11 | VJT754 | - | May 11, 10:30 UTC | May 11, 13:20 UTC | 2h 50m |
| 2026-05-11 | VJT754 | - | May 11, 06:40 UTC | May 11, 07:55 UTC | 1h 15m |
| 2026-05-10 | VJT754 | YYZ → LBG | May 10, 00:24 UTC | May 10, 07:25 UTC | 7h 0m |
| 2026-05-07 | VJT754 | - | May 7, 11:05 UTC | May 7, 18:00 UTC | 6h 55m |
| 2026-05-07 | VJT754 | - | May 7, 08:50 UTC | May 7, 09:50 UTC | 1h 0m |
| 2026-05-05 | VJT754 | - | May 5, 03:20 UTC | May 5, 13:50 UTC | 10h 30m |
| 2026-05-04 | VJT754 | - | May 4, 16:50 UTC | May 4, 22:30 UTC | 5h 41m |
| 2026-05-03 | VJT754 | - | May 3, 21:24 UTC | May 4, 00:55 UTC | 3h 30m |
| 2026-05-03 | VJT754 | - | May 3, 18:25 UTC | May 3, 19:34 UTC | 1h 10m |
| 2026-05-02 | VJT754 | - | May 2, 18:35 UTC | May 3, 18:30 UTC | 23h 54m |
| 2026-05-01 | VJT754 | - | May 1, 12:25 UTC | May 1, 12:40 UTC | 15m |
| 2026-05-01 | VJT754 | - | May 1, 03:10 UTC | May 1, 11:50 UTC | 8h 40m |
| 2026-04-30 | VJT754 | - | Apr 30, 10:35 UTC | Apr 30, 11:55 UTC | 1h 20m |
| 2026-04-30 | VJT754 | - | Apr 30, 06:40 UTC | Apr 30, 09:05 UTC | 2h 25m |
| 2026-04-29 | VJT754 | - | Apr 29, 04:39 UTC | Apr 29, 09:00 UTC | 4h 21m |
| 2026-04-27 | VJT754 | - | Apr 27, 16:15 UTC | Apr 28, 02:05 UTC | 9h 50m |
| 2026-04-25 | VJT754 | - | Apr 25, 11:25 UTC | Apr 25, 20:00 UTC | 8h 35m |
| 2026-04-23 | VJT754 | - | Apr 23, 13:10 UTC | Apr 23, 20:25 UTC | 7h 15m |
| 2026-04-23 | VJT754 | - | Apr 23, 06:55 UTC | Apr 23, 12:01 UTC | 5h 5m |
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-VJF page for operator, model, and routing details .