sensors Mode-S transponder
4D22F7
ICAO 24-bit transponder address · allocated to Malta
Currently assigned to 9H-VIC · BOMBARDIER BD-700 Global 7000/7500
- Hex
- 4D22F7
- Octal
- 23221367
- Decimal
- 5,055,223
- Country
- MT
- Tail
- 9H-VIC
- Type
- GL7T
- Flights observed
- 73
- Distinct callsigns
- 8
- Country
- MT
- Last broadcast
- 4d ago
Current position
Country allocation
The ICAO 24-bit address 4D22F7 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 8 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | VJT749 | - | Jul 26, 00:15 UTC | Jul 26, 08:10 UTC | 7h 56m |
| 2026-07-25 | RYR72TB | NCE → DUB | Jul 25, 23:35 UTC | Jul 26, 00:10 UTC | 35m |
| 2026-07-25 | VJT749 | - | Jul 25, 22:10 UTC | Jul 25, 22:45 UTC | 35m |
| 2026-07-25 | VJT749 | - | Jul 25, 13:40 UTC | Jul 25, 21:05 UTC | 7h 25m |
| 2026-07-24 | VJT749 | - | Jul 24, 13:10 UTC | Jul 24, 13:20 UTC | 10m |
| 2026-07-24 | VJT749 | - | Jul 24, 10:55 UTC | Jul 24, 12:00 UTC | 1h 5m |
| 2026-07-24 | VJT749 | - | Jul 24, 06:45 UTC | Jul 24, 08:30 UTC | 1h 45m |
| 2026-07-23 | VJT749 | - | Jul 23, 11:10 UTC | Jul 23, 12:55 UTC | 1h 45m |
| 2026-07-23 | VJT749 | - | Jul 23, 07:15 UTC | Jul 23, 09:05 UTC | 1h 50m |
| 2026-07-13 | - | - | Jul 13, 12:15 UTC | Jul 13, 12:25 UTC | 10m |
| 2026-07-12 | - | - | Jul 12, 17:15 UTC | Jul 12, 17:25 UTC | 10m |
| 2026-07-12 | - | - | Jul 12, 14:15 UTC | Jul 12, 14:25 UTC | 10m |
| 2026-07-11 | - | - | Jul 11, 13:20 UTC | Jul 11, 13:35 UTC | 15m |
| 2026-07-03 | VJT749 | - | Jul 3, 12:10 UTC | Jul 3, 14:10 UTC | 2h 0m |
| 2026-07-03 | VJT749 | - | Jul 3, 09:15 UTC | Jul 3, 09:50 UTC | 35m |
| 2026-07-03 | VJT749 | - | Jul 3, 05:40 UTC | Jul 3, 07:45 UTC | 2h 5m |
| 2026-07-01 | VJT749 | - | Jul 1, 15:20 UTC | Jul 1, 17:30 UTC | 2h 10m |
| 2026-07-01 | VJT749 | - | Jul 1, 11:50 UTC | Jul 1, 13:25 UTC | 1h 35m |
| 2026-07-01 | VJT749 | - | Jul 1, 08:45 UTC | Jul 1, 10:30 UTC | 1h 45m |
| 2026-06-29 | VJT749 | SJC → NCE | Jun 29, 23:09 UTC | Jun 30, 09:50 UTC | 10h 41m |
| 2026-06-26 | VJT749 | - | Jun 26, 00:55 UTC | Jun 26, 05:30 UTC | 4h 35m |
| 2026-06-25 | VJT749 | - | Jun 25, 22:49 UTC | Jun 25, 23:09 UTC | 20m |
| 2026-06-24 | VJT749 | - | Jun 24, 05:20 UTC | Jun 24, 05:49 UTC | 30m |
| 2026-06-24 | VJT749 | - | Jun 24, 01:24 UTC | Jun 24, 04:00 UTC | 2h 35m |
| 2026-06-21 | VJT276 | CPH → HPH | Jun 21, 21:19 UTC | Jun 22, 08:40 UTC | 11h 20m |
| 2026-06-21 | VJT749 | - | Jun 21, 17:39 UTC | Jun 21, 19:05 UTC | 1h 25m |
| 2026-06-18 | VJT749 | - | Jun 18, 16:50 UTC | Jun 18, 18:00 UTC | 1h 10m |
| 2026-06-18 | VJT749 | - | Jun 18, 13:25 UTC | Jun 18, 14:40 UTC | 1h 15m |
| 2026-06-18 | VJT749 | - | Jun 18, 10:40 UTC | Jun 18, 11:45 UTC | 1h 5m |
| 2026-06-16 | VJT324V | ICN → LTN | Jun 16, 17:49 UTC | Jun 17, 07:35 UTC | 13h 46m |
| 2026-06-15 | VJT324V | - | Jun 15, 11:54 UTC | Jun 15, 13:50 UTC | 1h 55m |
| 2026-06-15 | VJT749 | - | Jun 15, 03:19 UTC | Jun 15, 09:54 UTC | 6h 35m |
| 2026-06-12 | VJT749 | - | Jun 12, 03:50 UTC | Jun 12, 10:15 UTC | 6h 25m |
| 2026-06-11 | VJT749 | SJC → NRT | Jun 11, 16:15 UTC | Jun 12, 02:40 UTC | 10h 26m |
| 2026-06-10 | VJT749 | - | Jun 10, 12:10 UTC | Jun 10, 21:05 UTC | 8h 55m |
| 2026-06-08 | VJT749 | - | Jun 8, 12:05 UTC | Jun 8, 22:05 UTC | 10h 0m |
| 2026-06-08 | VJT749 | - | Jun 8, 09:05 UTC | Jun 8, 10:55 UTC | 1h 50m |
| 2026-06-07 | VJT749 | - | Jun 7, 00:10 UTC | Jun 7, 09:55 UTC | 9h 45m |
| 2026-06-05 | VJT749 | - | Jun 5, 15:05 UTC | Jun 5, 23:50 UTC | 8h 45m |
| 2026-06-04 | VJT749 | - | Jun 4, 08:55 UTC | Jun 4, 13:05 UTC | 4h 10m |
| 2026-06-04 | VJT749 | - | Jun 4, 05:00 UTC | Jun 4, 07:40 UTC | 2h 40m |
| 2026-05-30 | VJT749 | - | May 30, 07:25 UTC | May 30, 11:55 UTC | 4h 30m |
| 2026-05-27 | VJT749 | - | May 27, 22:50 UTC | May 28, 00:30 UTC | 1h 40m |
| 2026-05-27 | VJT749 | - | May 27, 16:40 UTC | May 27, 22:45 UTC | 6h 5m |
| 2026-05-27 | VJT171 | - | May 27, 13:55 UTC | May 27, 14:40 UTC | 45m |
| 2026-05-26 | VJT749 | - | May 26, 14:50 UTC | May 26, 17:44 UTC | 2h 55m |
| 2026-05-24 | VJT749 | - | May 24, 20:25 UTC | May 24, 21:45 UTC | 1h 20m |
| 2026-05-19 | VJT749 | - | May 19, 08:55 UTC | May 19, 15:15 UTC | 6h 20m |
| 2026-05-18 | VJT749 | - | May 18, 14:25 UTC | May 18, 15:35 UTC | 1h 10m |
| 2026-05-18 | VJT749 | GMP → NCE | May 18, 00:10 UTC | May 18, 13:00 UTC | 12h 50m |
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-VIC page for operator, model, and routing details .