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
- 106
- Distinct callsigns
- 6
- Country
- MT
- Last broadcast
- Jul 26, 18:45 UTC
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 6 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | VJT712 | - | Jul 26, 11:10 UTC | Jul 26, 18:40 UTC | 7h 30m |
| 2026-07-21 | VJT712 | - | Jul 21, 23:00 UTC | Jul 22, 02:20 UTC | 3h 20m |
| 2026-07-21 | VJT712 | - | Jul 21, 01:35 UTC | Jul 21, 01:50 UTC | 15m |
| 2026-07-20 | VJT712 | - | Jul 20, 06:25 UTC | Jul 20, 06:45 UTC | 20m |
| 2026-07-20 | VJT712 | - | Jul 20, 01:30 UTC | Jul 20, 05:40 UTC | 4h 10m |
| 2026-07-19 | VJT712 | - | Jul 19, 13:40 UTC | Jul 20, 00:00 UTC | 10h 20m |
| 2026-07-18 | VJT712 | - | Jul 18, 17:10 UTC | Jul 18, 18:00 UTC | 50m |
| 2026-07-18 | VJT712 | - | Jul 18, 13:05 UTC | Jul 18, 15:35 UTC | 2h 30m |
| 2026-07-18 | VJT712 | BQH → FRA | Jul 18, 10:50 UTC | Jul 18, 11:50 UTC | 1h 0m |
| 2026-07-15 | VJT712 | - | Jul 15, 07:20 UTC | Jul 15, 14:35 UTC | 7h 15m |
| 2026-07-14 | VJT712 | - | Jul 14, 14:30 UTC | Jul 14, 19:45 UTC | 5h 15m |
| 2026-07-14 | VJT712 | - | Jul 14, 12:05 UTC | Jul 14, 12:25 UTC | 20m |
| 2026-07-13 | VJT712 | SOF → BOJ | Jul 13, 20:40 UTC | Jul 13, 21:15 UTC | 35m |
| 2026-07-13 | VJT712 | - | Jul 13, 18:25 UTC | Jul 13, 19:10 UTC | 45m |
| 2026-07-13 | VJT712 | NCE → ATH | Jul 13, 15:20 UTC | Jul 13, 17:10 UTC | 1h 50m |
| 2026-07-12 | VJT712 | TEB → NCE | Jul 12, 14:01 UTC | Jul 12, 21:15 UTC | 7h 15m |
| 2026-07-12 | VJT712 | FOK → TEB | Jul 12, 11:50 UTC | Jul 12, 12:25 UTC | 35m |
| 2026-07-11 | VJT712 | - | Jul 11, 07:25 UTC | Jul 11, 14:05 UTC | 6h 40m |
| 2026-07-10 | VJT712 | LIN → LTN | Jul 10, 13:25 UTC | Jul 10, 15:05 UTC | 1h 40m |
| 2026-07-07 | VJT712 | - | Jul 7, 14:45 UTC | Jul 7, 15:55 UTC | 1h 10m |
| 2026-07-07 | VJT712 | - | Jul 7, 12:30 UTC | Jul 7, 13:20 UTC | 50m |
| 2026-07-06 | VJT712 | - | Jul 6, 13:40 UTC | Jul 6, 15:30 UTC | 1h 50m |
| 2026-07-05 | VJT712 | - | Jul 5, 17:25 UTC | Jul 5, 22:55 UTC | 5h 30m |
| 2026-07-04 | VJT712 | - | Jul 4, 14:25 UTC | Jul 4, 16:30 UTC | 2h 5m |
| 2026-07-04 | VJT712 | - | Jul 4, 08:55 UTC | Jul 4, 13:00 UTC | 4h 5m |
| 2026-07-03 | VJT712 | - | Jul 3, 08:50 UTC | Jul 3, 14:25 UTC | 5h 35m |
| 2026-07-01 | VJT712 | - | Jul 1, 23:55 UTC | Jul 2, 07:40 UTC | 7h 45m |
| 2026-07-01 | VJT712 | - | Jul 1, 20:40 UTC | Jul 1, 21:35 UTC | 55m |
| 2026-06-27 | VJT712 | - | Jun 27, 15:55 UTC | Jun 28, 00:00 UTC | 8h 5m |
| 2026-06-25 | VJT712 | - | Jun 25, 18:10 UTC | Jun 25, 18:50 UTC | 40m |
| 2026-06-25 | VJT712 | - | Jun 25, 12:04 UTC | Jun 25, 17:44 UTC | 5h 40m |
| 2026-06-25 | VJT712 | ZRH → DWC | Jun 25, 05:09 UTC | Jun 25, 11:10 UTC | 6h 0m |
| 2026-06-23 | VJT712 | TEB → ZRH | Jun 23, 23:24 UTC | Jun 24, 06:20 UTC | 6h 55m |
| 2026-06-23 | VJT712 | - | Jun 23, 09:20 UTC | Jun 23, 16:35 UTC | 7h 15m |
| 2026-06-22 | VJT712 | FAO → FAB | Jun 22, 15:20 UTC | Jun 22, 17:25 UTC | 2h 5m |
| 2026-06-21 | VJT712 | - | Jun 21, 21:54 UTC | Jun 21, 22:29 UTC | 35m |
| 2026-06-21 | VJT712 | - | Jun 21, 14:40 UTC | Jun 21, 20:29 UTC | 5h 50m |
| 2026-06-21 | VJT712 | TEB → MHT | Jun 21, 11:44 UTC | Jun 21, 12:24 UTC | 40m |
| 2026-06-17 | VJT712 | OLB → TEB | Jun 17, 05:25 UTC | Jun 17, 14:00 UTC | 8h 35m |
| 2026-06-16 | VJT712 | - | Jun 16, 08:15 UTC | Jun 16, 09:20 UTC | 1h 5m |
| 2026-06-16 | VJT712 | TEB → VIP | Jun 16, 00:10 UTC | Jun 16, 06:54 UTC | 6h 45m |
| 2026-06-14 | VJT712 | DEN → TEB | Jun 14, 21:45 UTC | Jun 15, 00:49 UTC | 3h 4m |
| 2026-06-13 | VJT712 | LIN → DEN | Jun 13, 11:25 UTC | Jun 13, 21:25 UTC | 10h 0m |
| 2026-06-13 | VJT712 | LBG → LIN | Jun 13, 08:35 UTC | Jun 13, 09:45 UTC | 1h 10m |
| 2026-06-11 | VJT712 | - | Jun 11, 10:30 UTC | Jun 11, 11:10 UTC | 40m |
| 2026-06-11 | VJT355R | - | Jun 11, 01:00 UTC | Jun 11, 09:45 UTC | 8h 45m |
| 2026-06-10 | VJT712 | GMP → BFI | Jun 10, 06:00 UTC | Jun 10, 15:05 UTC | 9h 5m |
| 2026-06-09 | VJT712 | - | Jun 9, 05:25 UTC | Jun 9, 05:55 UTC | 30m |
| 2026-06-09 | VJT712 | - | Jun 9, 02:55 UTC | Jun 9, 04:15 UTC | 1h 20m |
| 2026-06-08 | VJT712 | - | Jun 8, 08:50 UTC | Jun 8, 09:05 UTC | 15m |
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 .