sensors Mode-S transponder
4D23B7
ICAO 24-bit transponder address · allocated to Malta
Currently assigned to 9H-VIK · BOMBARDIER BD-700 Global 7000/7500
- Hex
- 4D23B7
- Octal
- 23221667
- Decimal
- 5,055,415
- Country
- MT
- Tail
- 9H-VIK
- Type
- GL7T
- Flights observed
- 47
- Distinct callsigns
- 4
- Country
- MT
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 4D23B7 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 4 distinct
Recent flights last 47
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-01 | VJT712 | - | Jun 1, 00:30 UTC | Jun 1, 08:45 UTC | 8h 15m |
| 2026-05-31 | VJT712 | YYZ → MIA | May 31, 19:50 UTC | May 31, 22:15 UTC | 2h 25m |
| 2026-05-30 | VJT779 | ICN → YYZ | May 30, 09:40 UTC | May 30, 22:05 UTC | 12h 25m |
| 2026-05-29 | VJT779 | - | May 29, 10:55 UTC | May 29, 14:00 UTC | 3h 5m |
| 2026-05-29 | VJT215 | - | May 29, 00:30 UTC | May 29, 05:45 UTC | 5h 15m |
| 2026-05-25 | VJT712 | - | May 25, 23:40 UTC | May 26, 13:24 UTC | 13h 45m |
| 2026-05-24 | VJT712 | - | May 24, 13:20 UTC | May 24, 17:05 UTC | 3h 45m |
| 2026-05-22 | VJT712 | - | May 22, 09:45 UTC | May 22, 16:20 UTC | 6h 35m |
| 2026-05-14 | VJT712 | NOC → FAB | May 14, 07:15 UTC | May 14, 08:10 UTC | 55m |
| 2026-05-13 | VJT712 | - | May 13, 10:30 UTC | May 13, 16:50 UTC | 6h 20m |
| 2026-05-12 | VJT712 | - | May 12, 16:25 UTC | May 12, 17:10 UTC | 45m |
| 2026-05-10 | VJT712 | - | May 10, 10:40 UTC | May 10, 21:59 UTC | 11h 20m |
| 2026-05-07 | VJT185 | - | May 7, 01:30 UTC | May 7, 02:05 UTC | 35m |
| 2026-05-05 | VJT185 | - | May 5, 18:50 UTC | May 6, 03:55 UTC | 9h 5m |
| 2026-05-05 | VJT712 | - | May 5, 16:06 UTC | May 5, 17:20 UTC | 1h 15m |
| 2026-05-04 | VJT712 | - | May 4, 12:05 UTC | May 4, 13:50 UTC | 1h 45m |
| 2026-05-04 | VJT712 | - | May 4, 00:00 UTC | May 4, 11:00 UTC | 11h 0m |
| 2026-04-30 | VJT712 | GMP → SFO | Apr 30, 08:15 UTC | Apr 30, 17:50 UTC | 9h 35m |
| 2026-04-30 | VJT712 | - | Apr 30, 05:35 UTC | Apr 30, 06:50 UTC | 1h 15m |
| 2026-04-26 | VJT712 | - | Apr 26, 23:55 UTC | Apr 27, 12:15 UTC | 12h 20m |
| 2026-04-26 | VJT712 | - | Apr 26, 20:45 UTC | Apr 26, 22:35 UTC | 1h 50m |
| 2026-04-26 | VJT712 | ATH → TEB | Apr 26, 09:25 UTC | Apr 26, 19:00 UTC | 9h 35m |
| 2026-04-26 | VJT712 | NCE → ATH | Apr 26, 06:00 UTC | Apr 26, 07:55 UTC | 1h 55m |
| 2026-04-24 | VJT712 | - | Apr 24, 14:30 UTC | Apr 24, 16:00 UTC | 1h 30m |
| 2026-04-24 | VJT712 | - | Apr 24, 11:15 UTC | Apr 24, 12:20 UTC | 1h 5m |
| 2026-04-23 | VJT712 | - | Apr 23, 11:40 UTC | Apr 23, 16:25 UTC | 4h 45m |
| 2026-04-22 | VJT712 | - | Apr 22, 13:50 UTC | Apr 23, 13:45 UTC | 23h 55m |
| 2026-04-22 | VJT712 | - | Apr 22, 12:20 UTC | Apr 23, 11:45 UTC | 23h 25m |
| 2026-04-21 | VJT712 | - | Apr 21, 17:05 UTC | Apr 21, 17:55 UTC | 50m |
| 2026-04-21 | VJT712 | - | Apr 21, 09:55 UTC | Apr 21, 16:25 UTC | 6h 30m |
| 2026-04-20 | VJT712 | - | Apr 20, 16:55 UTC | Apr 21, 15:45 UTC | 22h 50m |
| 2026-04-20 | VJT712 | - | Apr 20, 11:50 UTC | Apr 21, 10:35 UTC | 22h 45m |
| 2026-04-20 | VJT712 | - | Apr 20, 10:35 UTC | Apr 20, 17:10 UTC | 6h 35m |
| 2026-04-19 | VJT712 | - | Apr 19, 22:10 UTC | Apr 20, 08:20 UTC | 10h 10m |
| 2026-04-19 | VJT712 | - | Apr 19, 11:50 UTC | Apr 19, 19:35 UTC | 7h 45m |
| 2026-04-18 | VJT712 | - | Apr 18, 05:50 UTC | Apr 18, 07:15 UTC | 1h 25m |
| 2026-04-17 | VJT712 | - | Apr 17, 23:25 UTC | Apr 18, 00:40 UTC | 1h 15m |
| 2026-04-17 | VJT712 | - | Apr 17, 21:30 UTC | Apr 17, 23:20 UTC | 1h 50m |
| 2026-04-16 | VJT712 | - | Apr 16, 19:30 UTC | Apr 16, 20:00 UTC | 30m |
| 2026-04-14 | VJT712 | - | Apr 14, 19:45 UTC | Apr 14, 20:50 UTC | 1h 5m |
| 2026-04-14 | VJT712 | - | Apr 14, 17:05 UTC | Apr 14, 18:00 UTC | 55m |
| 2026-04-14 | VJT712 | - | Apr 14, 15:30 UTC | Apr 14, 15:45 UTC | 15m |
| 2026-04-14 | VJT712 | - | Apr 14, 10:50 UTC | Apr 14, 11:10 UTC | 20m |
| 2026-04-14 | VJT712 | - | Apr 14, 09:20 UTC | Apr 14, 11:05 UTC | 1h 45m |
| 2026-04-13 | VJT712 | - | Apr 13, 12:20 UTC | Apr 13, 12:30 UTC | 10m |
| 2026-04-13 | VJT712 | - | Apr 13, 11:55 UTC | Apr 13, 12:30 UTC | 35m |
| 2026-04-13 | VJT712 | - | Apr 13, 10:20 UTC | Apr 13, 12:15 UTC | 1h 55m |
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-VIK page for operator, model, and routing details .