sensors Mode-S transponder
4D243D
ICAO 24-bit transponder address
Currently assigned to 9H-VIO · BOMBARDIER BD-700 Global 7000/7500
- Hex
- 4D243D
- Octal
- 23222075
- Decimal
- 5,055,549
- Tail
- 9H-VIO
- Type
- GL7T
- Flights observed
- 61
- Distinct callsigns
- 5
- Country
- -
- Last broadcast
- 2d ago
Last known position
Callsign history 5 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | VJT793 | - | Jul 26, 11:45 UTC | Jul 26, 12:35 UTC | 50m |
| 2026-07-25 | VJT793 | - | Jul 25, 22:55 UTC | Jul 26, 10:20 UTC | 11h 26m |
| 2026-07-25 | VJT793 | PPM → SFO | Jul 25, 00:10 UTC | Jul 25, 05:20 UTC | 5h 10m |
| 2026-07-22 | VJT793 | TLV → FLL | Jul 22, 13:00 UTC | Jul 23, 01:00 UTC | 12h 0m |
| 2026-07-22 | VJT793 | - | Jul 22, 11:10 UTC | Jul 22, 11:15 UTC | 5m |
| 2026-07-21 | VJT793 | - | Jul 21, 13:10 UTC | Jul 21, 15:20 UTC | 2h 10m |
| 2026-07-21 | VJT793 | - | Jul 21, 10:05 UTC | Jul 21, 11:40 UTC | 1h 35m |
| 2026-07-19 | VJT793 | - | Jul 19, 19:55 UTC | Jul 20, 03:55 UTC | 8h 0m |
| 2026-07-19 | VJT793 | - | Jul 19, 01:25 UTC | Jul 19, 21:00 UTC | 19h 35m |
| 2026-07-17 | VJT793 | - | Jul 17, 10:10 UTC | Jul 17, 21:10 UTC | 11h 0m |
| 2026-07-16 | VJT789G | BEG → MAD | Jul 16, 14:40 UTC | Jul 16, 17:40 UTC | 3h 0m |
| 2026-07-16 | VJT789G | - | Jul 16, 10:45 UTC | Jul 16, 12:49 UTC | 2h 5m |
| 2026-07-16 | VJT789G | - | Jul 16, 02:20 UTC | Jul 16, 08:55 UTC | 6h 35m |
| 2026-07-15 | VJT793 | ATL → TEB | Jul 15, 21:20 UTC | Jul 15, 23:35 UTC | 2h 15m |
| 2026-07-14 | VJT793 | - | Jul 14, 19:50 UTC | Jul 15, 03:45 UTC | 7h 54m |
| 2026-07-13 | VJT793 | - | Jul 13, 17:20 UTC | Jul 13, 18:30 UTC | 1h 10m |
| 2026-07-13 | VJT793 | - | Jul 13, 13:15 UTC | Jul 13, 16:20 UTC | 3h 5m |
| 2026-07-13 | VJT793 | KEF → RKV | Jul 13, 10:40 UTC | Jul 13, 10:55 UTC | 15m |
| 2026-07-12 | VJT793 | - | Jul 12, 09:35 UTC | Jul 12, 09:55 UTC | 20m |
| 2026-07-12 | VJT793 | - | Jul 12, 03:25 UTC | Jul 12, 06:50 UTC | 3h 25m |
| 2026-07-11 | VJT793 | - | Jul 11, 23:40 UTC | Jul 12, 01:55 UTC | 2h 15m |
| 2026-07-10 | VJT793 | ATH → FOK | Jul 10, 08:45 UTC | Jul 10, 18:20 UTC | 9h 35m |
| 2026-07-09 | VJT793 | - | Jul 9, 07:25 UTC | Jul 9, 11:25 UTC | 4h 0m |
| 2026-07-08 | VJT751 | - | Jul 8, 12:00 UTC | Jul 8, 18:55 UTC | 6h 55m |
| 2026-07-08 | VJT793 | - | Jul 8, 02:05 UTC | Jul 8, 08:05 UTC | 6h 0m |
| 2026-07-08 | VJT793 | - | Jul 8, 00:25 UTC | Jul 8, 00:50 UTC | 25m |
| 2026-07-06 | VJT793 | - | Jul 6, 07:10 UTC | Jul 6, 17:05 UTC | 9h 55m |
| 2026-07-05 | VJT793 | - | Jul 5, 17:15 UTC | Jul 5, 18:10 UTC | 55m |
| 2026-07-05 | VJT793 | - | Jul 5, 13:05 UTC | Jul 5, 16:10 UTC | 3h 5m |
| 2026-07-05 | VJT793 | - | Jul 5, 02:30 UTC | Jul 5, 08:35 UTC | 6h 5m |
| 2026-07-03 | VJT793 | - | Jul 3, 09:05 UTC | Jul 3, 16:10 UTC | 7h 5m |
| 2026-07-03 | VJT793 | JMK → FAB | Jul 3, 04:05 UTC | Jul 3, 07:30 UTC | 3h 25m |
| 2026-07-03 | VJT793 | - | Jul 3, 01:00 UTC | Jul 3, 02:55 UTC | 1h 55m |
| 2026-07-01 | VJT793 | - | Jul 1, 23:15 UTC | Jul 2, 00:00 UTC | 45m |
| 2026-07-01 | VJT793 | - | Jul 1, 21:15 UTC | Jul 1, 22:00 UTC | 45m |
| 2026-07-01 | VJT793 | - | Jul 1, 19:05 UTC | Jul 1, 20:25 UTC | 1h 20m |
| 2026-07-01 | VJT793 | - | Jul 1, 14:50 UTC | Jul 1, 17:20 UTC | 2h 30m |
| 2026-06-30 | VJT793 | - | Jun 30, 16:10 UTC | Jun 30, 16:50 UTC | 40m |
| 2026-06-29 | VJT086M | - | Jun 29, 11:25 UTC | Jun 29, 13:09 UTC | 1h 45m |
| 2026-06-28 | VJT793 | - | Jun 28, 16:14 UTC | Jun 28, 17:10 UTC | 55m |
| 2026-06-28 | VJT793 | - | Jun 28, 13:49 UTC | Jun 28, 14:34 UTC | 45m |
| 2026-06-28 | VJT793 | TEB → LBG | Jun 28, 01:19 UTC | Jun 28, 07:54 UTC | 6h 35m |
| 2026-06-24 | VJT793 | - | Jun 24, 21:29 UTC | Jun 25, 07:39 UTC | 10h 10m |
| 2026-06-23 | VJT793 | - | Jun 23, 20:10 UTC | Jun 23, 23:19 UTC | 3h 10m |
| 2026-06-22 | VJT793 | - | Jun 22, 08:25 UTC | Jun 22, 10:15 UTC | 1h 50m |
| 2026-06-22 | VJT793 | BCN → IBZ | Jun 22, 06:19 UTC | Jun 22, 07:00 UTC | 40m |
| 2026-06-21 | VJT793 | - | Jun 21, 01:05 UTC | Jun 21, 07:49 UTC | 6h 45m |
| 2026-06-20 | VJT793 | PIE → HPN | Jun 20, 21:44 UTC | Jun 20, 23:59 UTC | 2h 15m |
| 2026-06-19 | VJT793 | - | Jun 19, 16:29 UTC | Jun 19, 17:09 UTC | 40m |
| 2026-06-19 | VJT793 | - | Jun 19, 08:54 UTC | Jun 19, 09:34 UTC | 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-VIO page for operator, model, and routing details .