sensors Mode-S transponder
4D22F5
ICAO 24-bit transponder address · allocated to Malta
Currently assigned to 9H-VIB · BOMBARDIER BD-700 Global 7000/7500
- Hex
- 4D22F5
- Octal
- 23221365
- Decimal
- 5,055,221
- Country
- MT
- Tail
- 9H-VIB
- Type
- GL7T
- Flights observed
- 95
- Distinct callsigns
- 6
- Country
- MT
- Last broadcast
- 17h ago
Last known position
Country allocation
The ICAO 24-bit address 4D22F5 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-07-17 | VJT783 | - | Jul 17, 00:04 UTC | Jul 17, 08:45 UTC | 8h 40m |
| 2026-07-16 | VJT783 | - | Jul 16, 06:00 UTC | Jul 16, 07:40 UTC | 1h 40m |
| 2026-07-15 | VJT783 | - | Jul 15, 00:40 UTC | Jul 15, 11:30 UTC | 10h 50m |
| 2026-07-13 | VJT783 | YYZ → EZE | Jul 13, 14:30 UTC | Jul 14, 01:40 UTC | 11h 10m |
| 2026-07-11 | VJT783 | - | Jul 11, 17:00 UTC | Jul 11, 22:20 UTC | 5h 20m |
| 2026-07-11 | VJT783 | - | Jul 11, 03:25 UTC | Jul 11, 15:40 UTC | 12h 15m |
| 2026-07-10 | VJT783 | - | Jul 10, 23:40 UTC | Jul 11, 00:55 UTC | 1h 15m |
| 2026-07-09 | VJT783 | - | Jul 9, 12:30 UTC | Jul 9, 17:45 UTC | 5h 15m |
| 2026-07-09 | VJT783 | - | Jul 9, 05:55 UTC | Jul 9, 07:25 UTC | 1h 30m |
| 2026-07-08 | VJT783 | - | Jul 8, 05:00 UTC | Jul 8, 05:15 UTC | 15m |
| 2026-07-07 | VJT783 | - | Jul 7, 19:00 UTC | Jul 7, 21:15 UTC | 2h 15m |
| 2026-07-06 | VJT783 | - | Jul 6, 11:40 UTC | Jul 6, 14:30 UTC | 2h 50m |
| 2026-07-06 | VJT783 | - | Jul 6, 09:50 UTC | Jul 6, 10:10 UTC | 20m |
| 2026-07-06 | VJT783 | - | Jul 6, 07:20 UTC | Jul 6, 09:45 UTC | 2h 25m |
| 2026-07-06 | VJT783 | - | Jul 6, 04:45 UTC | Jul 6, 05:40 UTC | 55m |
| 2026-07-03 | VJT783 | - | Jul 3, 17:15 UTC | Jul 4, 04:55 UTC | 11h 40m |
| 2026-07-03 | VJT783 | - | Jul 3, 14:35 UTC | Jul 3, 14:45 UTC | 10m |
| 2026-07-03 | VJT271 | - | Jul 3, 06:55 UTC | Jul 3, 11:10 UTC | 4h 15m |
| 2026-07-02 | VJT271 | - | Jul 2, 09:20 UTC | Jul 3, 07:35 UTC | 22h 15m |
| 2026-07-02 | VJT201 | - | Jul 2, 07:20 UTC | Jul 3, 07:15 UTC | 23h 55m |
| 2026-07-02 | VJT201 | - | Jul 2, 06:15 UTC | Jul 2, 09:50 UTC | 3h 35m |
| 2026-06-29 | VJT783 | - | Jun 29, 16:39 UTC | Jun 29, 19:09 UTC | 2h 30m |
| 2026-06-29 | VJT783 | MXP → NCE | Jun 29, 14:09 UTC | Jun 29, 14:50 UTC | 40m |
| 2026-06-28 | VJT783 | TEB → MXP | Jun 28, 13:04 UTC | Jun 28, 20:45 UTC | 7h 40m |
| 2026-06-27 | VJT783 | - | Jun 27, 16:00 UTC | Jun 27, 23:04 UTC | 7h 5m |
| 2026-06-27 | VJT783 | - | Jun 27, 12:55 UTC | Jun 27, 13:20 UTC | 25m |
| 2026-06-22 | VJT783 | DUB → FAB | Jun 22, 12:59 UTC | Jun 22, 13:49 UTC | 50m |
| 2026-06-22 | VJT783 | - | Jun 22, 03:14 UTC | Jun 22, 10:55 UTC | 7h 40m |
| 2026-06-20 | VJT783 | - | Jun 20, 21:44 UTC | Jun 20, 22:39 UTC | 55m |
| 2026-06-20 | VJT783 | - | Jun 20, 15:09 UTC | Jun 20, 20:09 UTC | 5h 0m |
| 2026-06-19 | VJT783 | MLA → TEB | Jun 19, 09:04 UTC | Jun 19, 18:30 UTC | 9h 25m |
| 2026-06-17 | VJT783 | - | Jun 17, 19:00 UTC | Jun 17, 19:25 UTC | 25m |
| 2026-06-17 | VJT783 | - | Jun 17, 09:40 UTC | Jun 17, 17:25 UTC | 7h 45m |
| 2026-06-16 | VJT783 | MSP → FRG | Jun 16, 16:55 UTC | Jun 16, 18:50 UTC | 1h 55m |
| 2026-06-15 | VJT783 | - | Jun 15, 09:40 UTC | Jun 15, 20:15 UTC | 10h 35m |
| 2026-06-15 | VJT783 | - | Jun 15, 03:05 UTC | Jun 15, 08:20 UTC | 5h 15m |
| 2026-06-14 | VJT783 | - | Jun 14, 06:05 UTC | Jun 14, 10:45 UTC | 4h 40m |
| 2026-06-14 | VJT783 | - | Jun 14, 02:15 UTC | Jun 14, 04:20 UTC | 2h 5m |
| 2026-06-13 | VJT783 | - | Jun 13, 10:05 UTC | Jun 13, 21:55 UTC | 11h 50m |
| 2026-06-12 | VJT783 | - | Jun 12, 16:55 UTC | Jun 12, 17:55 UTC | 1h 0m |
| 2026-06-10 | VJT783 | - | Jun 10, 13:15 UTC | Jun 10, 23:05 UTC | 9h 50m |
| 2026-06-10 | VJT783 | INN → LTN | Jun 10, 09:00 UTC | Jun 10, 10:30 UTC | 1h 30m |
| 2026-06-09 | VJT783 | IAD → INN | Jun 9, 09:40 UTC | Jun 9, 17:15 UTC | 7h 35m |
| 2026-06-09 | VJT783 | - | Jun 9, 07:30 UTC | Jun 9, 08:00 UTC | 30m |
| 2026-06-07 | VJT783 | - | Jun 7, 19:35 UTC | Jun 8, 02:50 UTC | 7h 15m |
| 2026-06-06 | VJT783 | - | Jun 6, 13:09 UTC | Jun 6, 17:40 UTC | 4h 30m |
| 2026-06-05 | VJT783 | - | Jun 5, 20:10 UTC | Jun 6, 17:40 UTC | 21h 30m |
| 2026-06-05 | VJT783 | - | Jun 5, 17:20 UTC | Jun 6, 17:15 UTC | 23h 55m |
| 2026-06-05 | VJT783 | - | Jun 5, 15:25 UTC | Jun 6, 15:15 UTC | 23h 50m |
| 2026-06-04 | VJT783 | NCE → LIN | Jun 4, 10:30 UTC | Jun 4, 11:05 UTC | 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-VIB page for operator, model, and routing details .