sensors Mode-S transponder
4D20E7
ICAO 24-bit transponder address · allocated to Malta
Currently assigned to 9H-VCE · BOMBARDIER BD-100 Challenger 350
- Hex
- 4D20E7
- Octal
- 23220347
- Decimal
- 5,054,695
- Country
- MT
- Tail
- 9H-VCE
- Type
- CL35
- Flights observed
- 53
- Distinct callsigns
- 2
- Country
- MT
- Last broadcast
- 3d ago
Last known position
Country allocation
The ICAO 24-bit address 4D20E7 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 2 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | VJT474 | - | May 30, 06:45 UTC | May 30, 07:55 UTC | 1h 10m |
| 2026-05-30 | VJT474 | - | May 30, 04:55 UTC | May 30, 05:10 UTC | 15m |
| 2026-05-30 | VJT474 | - | May 30, 03:25 UTC | May 30, 04:00 UTC | 35m |
| 2026-05-29 | VJT474 | - | May 29, 03:50 UTC | May 29, 04:00 UTC | 10m |
| 2026-05-28 | VJT474 | HKG → SZB | May 28, 09:10 UTC | May 28, 12:40 UTC | 3h 30m |
| 2026-05-27 | VJT474 | - | May 27, 14:50 UTC | May 27, 15:00 UTC | 10m |
| 2026-05-27 | VJT474 | - | May 27, 11:20 UTC | May 27, 14:15 UTC | 2h 55m |
| 2026-05-26 | VJT474 | HKG → HND | May 26, 13:54 UTC | May 26, 17:55 UTC | 4h 0m |
| 2026-05-25 | VJT474 | - | May 25, 16:45 UTC | May 25, 17:00 UTC | 15m |
| 2026-05-25 | VJT474 | - | May 25, 13:40 UTC | May 25, 14:00 UTC | 20m |
| 2026-05-21 | VJT474 | - | May 21, 07:30 UTC | May 21, 10:35 UTC | 3h 5m |
| 2026-05-21 | VJT474 | - | May 21, 06:00 UTC | May 21, 06:15 UTC | 15m |
| 2026-05-21 | VJT474 | - | May 21, 02:30 UTC | May 21, 02:45 UTC | 15m |
| 2026-05-19 | VJT474 | - | May 19, 23:05 UTC | May 19, 23:25 UTC | 20m |
| 2026-05-18 | VJT474 | - | May 18, 08:01 UTC | May 18, 08:10 UTC | 10m |
| 2026-05-18 | VJT474 | - | May 18, 05:45 UTC | May 18, 06:10 UTC | 25m |
| 2026-05-10 | VJT474 | - | May 10, 08:40 UTC | May 10, 10:24 UTC | 1h 45m |
| 2026-05-10 | VJT474 | - | May 10, 06:35 UTC | May 10, 07:30 UTC | 55m |
| 2026-05-08 | VJT474 | - | May 8, 08:34 UTC | May 8, 08:49 UTC | 15m |
| 2026-05-08 | VJT474 | - | May 8, 06:45 UTC | May 8, 07:04 UTC | 20m |
| 2026-05-07 | VJT474 | - | May 7, 05:25 UTC | May 7, 05:35 UTC | 10m |
| 2026-05-06 | VJT474 | - | May 6, 05:10 UTC | May 6, 09:25 UTC | 4h 15m |
| 2026-05-06 | VJT474 | HKG → TSA | May 6, 02:15 UTC | May 6, 03:30 UTC | 1h 15m |
| 2026-05-05 | VJT474 | - | May 5, 08:30 UTC | May 5, 08:55 UTC | 25m |
| 2026-05-05 | VJT474 | - | May 5, 05:30 UTC | May 5, 08:00 UTC | 2h 30m |
| 2026-05-05 | VJT474 | - | May 5, 01:35 UTC | May 5, 01:40 UTC | 5m |
| 2026-05-03 | VJT474 | - | May 3, 07:55 UTC | May 3, 08:15 UTC | 20m |
| 2026-05-03 | VJT474 | - | May 3, 04:50 UTC | May 3, 06:10 UTC | 1h 20m |
| 2026-05-02 | VJT474 | - | May 2, 07:50 UTC | May 2, 13:30 UTC | 5h 40m |
| 2026-05-01 | VJT474 | - | May 1, 08:05 UTC | May 1, 08:50 UTC | 45m |
| 2026-04-30 | VJT474 | - | Apr 30, 07:50 UTC | Apr 30, 08:00 UTC | 10m |
| 2026-04-30 | VJT474 | - | Apr 30, 01:10 UTC | Apr 30, 06:35 UTC | 5h 25m |
| 2026-04-29 | VJT474 | - | Apr 29, 22:30 UTC | Apr 29, 23:25 UTC | 54m |
| 2026-04-29 | VJT474 | - | Apr 29, 07:40 UTC | Apr 29, 08:20 UTC | 40m |
| 2026-04-28 | VJT474 | - | Apr 28, 11:50 UTC | Apr 29, 08:20 UTC | 20h 30m |
| 2026-04-28 | VJT474 | - | Apr 28, 10:05 UTC | Apr 28, 10:15 UTC | 10m |
| 2026-04-28 | VJT474 | - | Apr 28, 08:10 UTC | Apr 28, 09:15 UTC | 1h 5m |
| 2026-04-27 | VJT474 | - | Apr 27, 07:25 UTC | Apr 27, 07:50 UTC | 25m |
| 2026-04-27 | VJT474 | - | Apr 27, 06:20 UTC | Apr 27, 06:50 UTC | 30m |
| 2026-04-27 | VJT474 | - | Apr 27, 04:20 UTC | Apr 27, 04:40 UTC | 20m |
| 2026-04-27 | VJT474 | - | Apr 27, 00:35 UTC | Apr 27, 03:45 UTC | 3h 10m |
| 2026-04-26 | VJT474 | TSA → CTS | Apr 26, 00:15 UTC | Apr 26, 03:25 UTC | 3h 10m |
| 2026-04-25 | VJT474 | - | Apr 25, 03:00 UTC | Apr 25, 07:15 UTC | 4h 15m |
| 2026-04-17 | VJT474 | - | Apr 17, 09:25 UTC | Apr 17, 10:00 UTC | 35m |
| 2026-04-17 | VJT474 | - | Apr 17, 03:20 UTC | Apr 17, 04:20 UTC | 1h 0m |
| 2026-04-17 | VJT474 | HKG → TSA | Apr 17, 00:00 UTC | Apr 17, 01:15 UTC | 1h 15m |
| 2026-04-16 | VJT474 | - | Apr 16, 09:10 UTC | Apr 16, 09:35 UTC | 25m |
| 2026-04-16 | VJT474 | - | Apr 16, 07:09 UTC | Apr 16, 07:24 UTC | 15m |
| 2026-04-16 | VJT474 | - | Apr 16, 02:24 UTC | Apr 16, 03:04 UTC | 40m |
| 2026-04-15 | VJT474 | - | Apr 15, 07:20 UTC | Apr 15, 07:50 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-VCE page for operator, model, and routing details .