sensors Mode-S transponder
4D20F8
ICAO 24-bit transponder address · allocated to Malta
Currently assigned to 9H-VJP · BOMBARDIER BD-700 Global 6000/6500
- Hex
- 4D20F8
- Octal
- 23220370
- Decimal
- 5,054,712
- Country
- MT
- Tail
- 9H-VJP
- Type
- GLEX
- Flights observed
- 49
- Distinct callsigns
- 1
- Country
- MT
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 4D20F8 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 1 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| VJT895 | - | 49 | 2026-06-01 |
Recent flights last 49
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-01 | VJT895 | - | Jun 1, 13:40 UTC | Jun 1, 20:45 UTC | 7h 5m |
| 2026-05-31 | VJT895 | - | May 31, 20:05 UTC | Jun 1, 20:00 UTC | 23h 55m |
| 2026-05-31 | VJT895 | - | May 31, 14:05 UTC | Jun 1, 13:50 UTC | 23h 45m |
| 2026-05-30 | VJT895 | - | May 30, 15:50 UTC | May 30, 18:50 UTC | 3h 0m |
| 2026-05-29 | VJT895 | - | May 29, 15:20 UTC | May 29, 16:50 UTC | 1h 30m |
| 2026-05-29 | VJT895 | - | May 29, 13:40 UTC | May 29, 13:50 UTC | 10m |
| 2026-05-27 | VJT895 | - | May 27, 13:45 UTC | May 27, 15:25 UTC | 1h 40m |
| 2026-05-27 | VJT895 | - | May 27, 02:54 UTC | May 27, 11:50 UTC | 8h 55m |
| 2026-05-25 | VJT895 | - | May 25, 14:40 UTC | May 26, 00:49 UTC | 10h 10m |
| 2026-05-24 | VJT895 | - | May 24, 11:15 UTC | May 24, 21:10 UTC | 9h 55m |
| 2026-05-23 | VJT895 | - | May 23, 12:40 UTC | May 23, 21:20 UTC | 8h 41m |
| 2026-05-23 | VJT895 | - | May 23, 07:05 UTC | May 23, 08:20 UTC | 1h 15m |
| 2026-05-22 | VJT895 | - | May 22, 02:15 UTC | May 22, 09:00 UTC | 6h 45m |
| 2026-05-20 | VJT895 | - | May 20, 21:15 UTC | May 21, 04:30 UTC | 7h 15m |
| 2026-05-20 | VJT895 | - | May 20, 10:30 UTC | May 20, 11:00 UTC | 30m |
| 2026-05-18 | VJT895 | LAS → FAB | May 18, 06:35 UTC | May 18, 15:35 UTC | 9h 0m |
| 2026-05-18 | VJT895 | - | May 18, 01:15 UTC | May 18, 05:15 UTC | 4h 0m |
| 2026-05-15 | VJT895 | - | May 15, 17:00 UTC | May 15, 20:30 UTC | 3h 30m |
| 2026-05-15 | VJT895 | - | May 15, 05:55 UTC | May 15, 15:45 UTC | 9h 49m |
| 2026-05-12 | VJT895 | - | May 12, 17:05 UTC | May 13, 01:10 UTC | 8h 5m |
| 2026-05-12 | VJT895 | - | May 12, 09:35 UTC | May 12, 15:55 UTC | 6h 20m |
| 2026-05-10 | VJT895 | - | May 10, 21:54 UTC | May 10, 23:35 UTC | 1h 40m |
| 2026-05-10 | VJT895 | - | May 10, 14:14 UTC | May 10, 20:30 UTC | 6h 15m |
| 2026-05-07 | VJT895 | - | May 7, 11:25 UTC | May 7, 16:55 UTC | 5h 30m |
| 2026-05-07 | VJT895 | - | May 7, 09:10 UTC | May 7, 09:55 UTC | 45m |
| 2026-05-06 | VJT895 | - | May 6, 15:30 UTC | May 6, 16:35 UTC | 1h 5m |
| 2026-05-06 | VJT895 | - | May 6, 08:35 UTC | May 6, 14:30 UTC | 5h 55m |
| 2026-05-05 | VJT895 | - | May 5, 14:25 UTC | May 5, 15:15 UTC | 50m |
| 2026-05-05 | VJT895 | MAD → FAB | May 5, 11:40 UTC | May 5, 13:20 UTC | 1h 40m |
| 2026-05-05 | VJT895 | LTN → MAD | May 5, 07:55 UTC | May 5, 10:05 UTC | 2h 10m |
| 2026-05-03 | VJT895 | - | May 3, 09:35 UTC | May 3, 17:29 UTC | 7h 55m |
| 2026-05-02 | VJT895 | - | May 2, 16:45 UTC | May 2, 17:15 UTC | 30m |
| 2026-05-01 | VJT895 | - | May 1, 05:35 UTC | May 1, 10:50 UTC | 5h 15m |
| 2026-05-01 | VJT895 | ATH → ATH | May 1, 05:00 UTC | May 1, 05:05 UTC | 5m |
| 2026-04-30 | VJT895 | - | Apr 30, 22:40 UTC | May 1, 03:45 UTC | 5h 5m |
| 2026-04-29 | VJT895 | - | Apr 29, 10:45 UTC | Apr 29, 16:30 UTC | 5h 45m |
| 2026-04-26 | VJT895 | - | Apr 26, 22:25 UTC | Apr 27, 05:40 UTC | 7h 15m |
| 2026-04-26 | VJT895 | - | Apr 26, 16:25 UTC | Apr 26, 20:55 UTC | 4h 30m |
| 2026-04-25 | VJT895 | - | Apr 25, 08:50 UTC | Apr 25, 19:15 UTC | 10h 25m |
| 2026-04-24 | VJT895 | - | Apr 24, 13:00 UTC | Apr 24, 13:25 UTC | 25m |
| 2026-04-24 | VJT895 | - | Apr 24, 06:40 UTC | Apr 24, 12:05 UTC | 5h 25m |
| 2026-04-24 | VJT895 | - | Apr 24, 03:40 UTC | Apr 24, 06:35 UTC | 2h 55m |
| 2026-04-22 | VJT895 | - | Apr 22, 12:35 UTC | Apr 22, 21:50 UTC | 9h 15m |
| 2026-04-19 | VJT895 | - | Apr 19, 00:35 UTC | Apr 19, 08:00 UTC | 7h 25m |
| 2026-04-18 | VJT895 | - | Apr 18, 18:55 UTC | Apr 18, 21:35 UTC | 2h 40m |
| 2026-04-17 | VJT895 | - | Apr 17, 18:40 UTC | Apr 17, 19:05 UTC | 25m |
| 2026-04-17 | VJT895 | - | Apr 17, 09:20 UTC | Apr 17, 10:45 UTC | 1h 25m |
| 2026-04-17 | VJT895 | - | Apr 17, 07:20 UTC | Apr 17, 07:50 UTC | 30m |
| 2026-04-17 | VJT895 | - | Apr 17, 06:45 UTC | Apr 17, 07:15 UTC | 30m |
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-VJP page for operator, model, and routing details .