sensors Mode-S transponder
4D238C
ICAO 24-bit transponder address · allocated to Malta
Currently assigned to 9H-VIJ · BOMBARDIER BD-700 Global 7000/7500
- Hex
- 4D238C
- Octal
- 23221614
- Decimal
- 5,055,372
- Country
- MT
- Tail
- 9H-VIJ
- Type
- GL7T
- Flights observed
- 84
- Distinct callsigns
- 8
- Country
- MT
- Last broadcast
- 6d ago
Current position
Country allocation
The ICAO 24-bit address 4D238C 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-25 | VJT296 | - | Jul 25, 11:25 UTC | Jul 25, 21:20 UTC | 9h 55m |
| 2026-07-24 | VJT187 | - | Jul 24, 02:05 UTC | Jul 24, 03:00 UTC | 55m |
| 2026-07-23 | VJT187 | - | Jul 23, 20:15 UTC | Jul 23, 23:35 UTC | 3h 20m |
| 2026-07-23 | VJT164 | - | Jul 23, 16:55 UTC | Jul 23, 17:15 UTC | 20m |
| 2026-07-23 | VJT164 | - | Jul 23, 14:50 UTC | Jul 23, 15:50 UTC | 1h 0m |
| 2026-07-21 | VJT164 | - | Jul 21, 16:50 UTC | Jul 21, 17:55 UTC | 1h 5m |
| 2026-07-20 | VJT042Y | - | Jul 20, 17:15 UTC | Jul 21, 17:00 UTC | 23h 44m |
| 2026-07-20 | VJT042Y | DSS → JNB | Jul 20, 07:55 UTC | Jul 20, 15:45 UTC | 7h 50m |
| 2026-07-19 | VJT792 | NHT → DSS | Jul 19, 09:40 UTC | Jul 19, 15:20 UTC | 5h 40m |
| 2026-07-18 | VJT792 | SJC → NHT | Jul 18, 00:00 UTC | Jul 18, 09:55 UTC | 9h 56m |
| 2026-07-16 | VJT792 | - | Jul 16, 03:45 UTC | Jul 16, 14:35 UTC | 10h 50m |
| 2026-07-16 | VJT792 | - | Jul 16, 02:30 UTC | Jul 16, 02:40 UTC | 10m |
| 2026-07-15 | VJT792 | - | Jul 15, 04:30 UTC | Jul 15, 04:45 UTC | 15m |
| 2026-07-15 | VJT792 | - | Jul 15, 02:45 UTC | Jul 15, 03:00 UTC | 15m |
| 2026-07-14 | VJT792 | - | Jul 14, 15:10 UTC | Jul 15, 01:40 UTC | 10h 29m |
| 2026-07-13 | VJT792 | - | Jul 13, 22:20 UTC | Jul 13, 23:10 UTC | 50m |
| 2026-07-11 | VJT792 | - | Jul 11, 09:50 UTC | Jul 11, 21:00 UTC | 11h 10m |
| 2026-07-10 | VJT792 | AMS → ZRH | Jul 10, 13:05 UTC | Jul 10, 14:00 UTC | 55m |
| 2026-07-10 | VJT792 | - | Jul 10, 09:25 UTC | Jul 10, 11:25 UTC | 2h 0m |
| 2026-07-10 | VJT792 | CMN → IBZ | Jul 10, 05:55 UTC | Jul 10, 07:15 UTC | 1h 20m |
| 2026-07-08 | VJT792 | - | Jul 8, 20:30 UTC | Jul 8, 22:40 UTC | 2h 10m |
| 2026-07-08 | VJT792 | - | Jul 8, 19:15 UTC | Jul 8, 19:30 UTC | 15m |
| 2026-07-08 | VJT792 | - | Jul 8, 14:20 UTC | Jul 8, 16:15 UTC | 1h 55m |
| 2026-07-08 | VJT792 | BGR → YYZ | Jul 8, 11:15 UTC | Jul 8, 12:35 UTC | 1h 20m |
| 2026-07-07 | VJT792 | AMS → BGR | Jul 7, 12:25 UTC | Jul 7, 18:45 UTC | 6h 20m |
| 2026-07-07 | VJT792 | - | Jul 7, 09:25 UTC | Jul 7, 10:15 UTC | 50m |
| 2026-06-28 | VJT792 | - | Jun 28, 15:34 UTC | Jun 28, 16:00 UTC | 25m |
| 2026-06-28 | VJT792 | IBZ → NHT | Jun 28, 11:00 UTC | Jun 28, 12:50 UTC | 1h 50m |
| 2026-06-28 | VJT792 | CPH → IBZ | Jun 28, 06:55 UTC | Jun 28, 09:39 UTC | 2h 45m |
| 2026-06-24 | VJT297 | - | Jun 24, 16:19 UTC | Jun 25, 04:10 UTC | 11h 50m |
| 2026-06-23 | VJT792 | - | Jun 23, 12:25 UTC | Jun 23, 17:30 UTC | 5h 5m |
| 2026-06-23 | VJT792 | - | Jun 23, 10:29 UTC | Jun 23, 10:49 UTC | 20m |
| 2026-06-23 | VJT792 | - | Jun 23, 08:15 UTC | Jun 23, 08:50 UTC | 35m |
| 2026-06-20 | VJT272 | - | Jun 20, 20:29 UTC | Jun 21, 07:55 UTC | 11h 25m |
| 2026-06-19 | VJT792 | - | Jun 19, 13:50 UTC | Jun 19, 20:44 UTC | 6h 55m |
| 2026-06-18 | VJT792 | LUK → PWK | Jun 18, 18:45 UTC | Jun 18, 19:40 UTC | 55m |
| 2026-06-16 | VJT792 | - | Jun 16, 12:39 UTC | Jun 16, 22:00 UTC | 9h 21m |
| 2026-06-16 | VJT792 | - | Jun 16, 08:30 UTC | Jun 16, 09:10 UTC | 40m |
| 2026-06-14 | VJT792 | - | Jun 14, 20:50 UTC | Jun 14, 21:20 UTC | 30m |
| 2026-06-14 | VJT174 | - | Jun 14, 15:20 UTC | Jun 14, 19:10 UTC | 3h 50m |
| 2026-06-14 | VJT174 | - | Jun 14, 06:45 UTC | Jun 14, 07:05 UTC | 20m |
| 2026-06-12 | VJT174 | ZGN → HKG | Jun 12, 16:35 UTC | Jun 12, 17:05 UTC | 30m |
| 2026-06-12 | VJT174 | - | Jun 12, 07:20 UTC | Jun 12, 09:40 UTC | 2h 20m |
| 2026-06-11 | VJT792 | - | Jun 11, 09:35 UTC | Jun 11, 11:25 UTC | 1h 50m |
| 2026-06-08 | VJT792 | - | Jun 8, 18:15 UTC | Jun 8, 22:10 UTC | 3h 55m |
| 2026-06-08 | VJT792 | GLA → LBG | Jun 8, 15:25 UTC | Jun 8, 16:50 UTC | 1h 25m |
| 2026-06-07 | VJT792 | EDI → GLA | Jun 7, 09:20 UTC | Jun 7, 09:35 UTC | 15m |
| 2026-06-07 | VJT792 | - | Jun 7, 01:24 UTC | Jun 7, 08:05 UTC | 6h 40m |
| 2026-06-06 | VJT792 | - | Jun 6, 22:15 UTC | Jun 7, 00:00 UTC | 1h 45m |
| 2026-06-05 | VJT792 | ATH → TEB | Jun 5, 14:35 UTC | Jun 6, 00:15 UTC | 9h 40m |
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-VIJ page for operator, model, and routing details .