sensors Mode-S transponder
4D2131
ICAO 24-bit transponder address · allocated to Malta
Currently assigned to 9H-VJV · BOMBARDIER BD-700 Global 6000/6500
- Hex
- 4D2131
- Octal
- 23220461
- Decimal
- 5,054,769
- Country
- MT
- Tail
- 9H-VJV
- Type
- GLEX
- Flights observed
- 58
- Distinct callsigns
- 3
- Country
- MT
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 4D2131 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 3 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-28 | VJT957 | - | May 28, 17:00 UTC | May 28, 17:20 UTC | 20m |
| 2026-05-28 | VJT957 | - | May 28, 14:50 UTC | May 28, 15:25 UTC | 35m |
| 2026-05-27 | VJT957 | - | May 27, 04:30 UTC | May 27, 10:20 UTC | 5h 50m |
| 2026-05-26 | VJT957 | - | May 26, 17:04 UTC | May 27, 02:04 UTC | 9h 0m |
| 2026-05-25 | VJT957 | - | May 25, 20:09 UTC | May 25, 22:25 UTC | 2h 15m |
| 2026-05-25 | VJT957 | YYZ → VNY | May 25, 14:45 UTC | May 25, 19:10 UTC | 4h 25m |
| 2026-05-24 | VJT957 | - | May 24, 20:40 UTC | May 24, 21:45 UTC | 1h 5m |
| 2026-05-24 | VJT957 | AUS → ROG | May 24, 17:10 UTC | May 24, 18:10 UTC | 1h 0m |
| 2026-05-22 | VJT957 | - | May 22, 19:55 UTC | May 23, 01:50 UTC | 5h 55m |
| 2026-05-22 | VJT957 | TSA → ANC | May 22, 10:05 UTC | May 22, 18:20 UTC | 8h 15m |
| 2026-05-21 | VJT957 | - | May 21, 06:40 UTC | May 21, 11:00 UTC | 4h 20m |
| 2026-05-20 | VJT957 | - | May 20, 10:25 UTC | May 21, 05:10 UTC | 18h 45m |
| 2026-05-20 | VJT957 | - | May 20, 09:25 UTC | May 21, 05:10 UTC | 19h 45m |
| 2026-05-20 | VJT957 | - | May 20, 06:50 UTC | May 20, 07:00 UTC | 10m |
| 2026-05-20 | VJT957 | - | May 20, 04:45 UTC | May 20, 05:15 UTC | 30m |
| 2026-05-18 | VJT957 | - | May 18, 15:40 UTC | May 18, 15:50 UTC | 10m |
| 2026-05-18 | VJT957 | - | May 18, 03:30 UTC | May 18, 06:50 UTC | 3h 20m |
| 2026-05-16 | VJT274 | - | May 16, 10:16 UTC | May 16, 15:25 UTC | 5h 10m |
| 2026-05-15 | VJT957 | - | May 15, 01:35 UTC | May 15, 08:15 UTC | 6h 40m |
| 2026-05-14 | VJT957 | - | May 14, 18:35 UTC | May 15, 00:25 UTC | 5h 50m |
| 2026-05-14 | VJT957 | TEB → HPN | May 14, 15:50 UTC | May 14, 16:10 UTC | 20m |
| 2026-05-12 | VJT957 | BQH → TEB | May 12, 14:00 UTC | May 12, 21:20 UTC | 7h 20m |
| 2026-05-11 | VJT957 | - | May 11, 08:15 UTC | May 11, 08:50 UTC | 35m |
| 2026-05-10 | VJT957 | - | May 10, 23:09 UTC | May 11, 06:55 UTC | 7h 45m |
| 2026-05-10 | VJT957 | - | May 10, 19:30 UTC | May 10, 21:54 UTC | 2h 25m |
| 2026-05-09 | VJT957 | - | May 9, 10:30 UTC | May 9, 17:40 UTC | 7h 10m |
| 2026-05-09 | VJT957 | - | May 9, 07:15 UTC | May 9, 08:45 UTC | 1h 30m |
| 2026-05-08 | VJT957 | - | May 8, 10:39 UTC | May 8, 15:25 UTC | 4h 45m |
| 2026-05-04 | VJT957 | - | May 4, 13:05 UTC | May 4, 17:00 UTC | 3h 55m |
| 2026-05-04 | VJT957 | LIN → NCE | May 4, 09:25 UTC | May 4, 10:05 UTC | 40m |
| 2026-05-03 | VJT957 | - | May 3, 15:10 UTC | May 3, 16:45 UTC | 1h 35m |
| 2026-05-03 | VJT957 | LBG → LTN | May 3, 07:25 UTC | May 3, 08:15 UTC | 50m |
| 2026-05-03 | VJT957 | - | May 3, 04:50 UTC | May 3, 06:25 UTC | 1h 35m |
| 2026-05-02 | VJT957 | - | May 2, 22:20 UTC | May 2, 22:30 UTC | 10m |
| 2026-05-01 | VJT957 | - | May 1, 21:00 UTC | May 1, 23:30 UTC | 2h 30m |
| 2026-05-01 | VJT957 | - | May 1, 17:30 UTC | May 1, 20:05 UTC | 2h 35m |
| 2026-04-30 | VJT957 | - | Apr 30, 07:50 UTC | Apr 30, 15:10 UTC | 7h 20m |
| 2026-04-29 | VJT957 | - | Apr 29, 10:30 UTC | Apr 29, 11:45 UTC | 1h 15m |
| 2026-04-29 | VJT957 | - | Apr 29, 01:05 UTC | Apr 29, 09:05 UTC | 8h 1m |
| 2026-04-28 | VJT957 | - | Apr 28, 22:00 UTC | Apr 28, 23:25 UTC | 1h 25m |
| 2026-04-27 | VJT957 | - | Apr 27, 20:20 UTC | Apr 27, 21:00 UTC | 40m |
| 2026-04-26 | VJT957 | - | Apr 26, 06:20 UTC | Apr 26, 17:25 UTC | 11h 5m |
| 2026-04-25 | VJT957 | - | Apr 25, 08:55 UTC | Apr 25, 09:40 UTC | 45m |
| 2026-04-23 | VJT957 | - | Apr 23, 06:40 UTC | Apr 23, 07:01 UTC | 20m |
| 2026-04-23 | VJT957 | - | Apr 23, 00:10 UTC | Apr 23, 05:50 UTC | 5h 40m |
| 2026-04-21 | VJT957 | - | Apr 21, 12:15 UTC | Apr 21, 13:30 UTC | 1h 15m |
| 2026-04-20 | VJT957 | - | Apr 20, 21:00 UTC | Apr 21, 07:35 UTC | 10h 35m |
| 2026-04-18 | VJT957 | - | Apr 18, 18:55 UTC | Apr 19, 05:05 UTC | 10h 10m |
| 2026-04-18 | VJT957 | LBA → LBA | Apr 18, 17:50 UTC | Apr 18, 18:05 UTC | 15m |
| 2026-04-18 | VJT957 | MUC → LBA | Apr 18, 14:35 UTC | Apr 18, 16:15 UTC | 1h 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-VJV page for operator, model, and routing details .