sensors Mode-S transponder
4D247F
ICAO 24-bit transponder address
Currently assigned to 9H-VIT · BOMBARDIER BD-700 Global 7000/7500
- Hex
- 4D247F
- Octal
- 23222177
- Decimal
- 5,055,615
- Tail
- 9H-VIT
- Type
- GL7T
- Flights observed
- 45
- Distinct callsigns
- 2
- Country
- -
- Last broadcast
- 10d ago
Last known position
Callsign history 2 distinct
Recent flights last 45
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | VJT255 | - | Jul 26, 14:25 UTC | Jul 26, 18:35 UTC | 4h 10m |
| 2026-07-25 | VJT768 | NCE → LTN | Jul 25, 18:45 UTC | Jul 25, 20:20 UTC | 1h 35m |
| 2026-07-24 | VJT768 | - | Jul 24, 17:20 UTC | Jul 24, 19:55 UTC | 2h 35m |
| 2026-07-23 | VJT768 | - | Jul 23, 20:25 UTC | Jul 24, 15:20 UTC | 18h 55m |
| 2026-07-23 | VJT768 | - | Jul 23, 17:50 UTC | Jul 24, 15:20 UTC | 21h 30m |
| 2026-07-23 | VJT768 | - | Jul 23, 16:40 UTC | Jul 24, 15:20 UTC | 22h 40m |
| 2026-07-22 | VJT768 | - | Jul 22, 19:05 UTC | Jul 22, 20:40 UTC | 1h 35m |
| 2026-07-22 | VJT768 | MLA → IBZ | Jul 22, 16:15 UTC | Jul 22, 18:10 UTC | 1h 55m |
| 2026-07-21 | VJT768 | - | Jul 21, 12:40 UTC | Jul 21, 15:00 UTC | 2h 20m |
| 2026-07-21 | VJT768 | - | Jul 21, 08:40 UTC | Jul 21, 10:40 UTC | 2h 0m |
| 2026-07-21 | VJT768 | - | Jul 21, 05:20 UTC | Jul 21, 06:55 UTC | 1h 35m |
| 2026-07-20 | VJT768 | - | Jul 20, 09:10 UTC | Jul 20, 12:50 UTC | 3h 40m |
| 2026-07-20 | VJT768 | - | Jul 20, 04:40 UTC | Jul 20, 05:35 UTC | 55m |
| 2026-07-19 | VJT768 | - | Jul 19, 14:10 UTC | Jul 19, 14:40 UTC | 30m |
| 2026-07-18 | VJT768 | - | Jul 18, 07:25 UTC | Jul 18, 14:15 UTC | 6h 50m |
| 2026-07-15 | VJT768 | - | Jul 15, 23:25 UTC | Jul 16, 09:20 UTC | 9h 55m |
| 2026-07-15 | VJT768 | COE → AUS | Jul 15, 18:50 UTC | Jul 15, 22:05 UTC | 3h 15m |
| 2026-07-12 | VJT768 | DFW → COE | Jul 12, 15:25 UTC | Jul 12, 18:20 UTC | 2h 55m |
| 2026-07-10 | VJT768 | LIS → DFW | Jul 10, 14:50 UTC | Jul 11, 00:00 UTC | 9h 10m |
| 2026-07-10 | VJT768 | FAO → LIS | Jul 10, 12:30 UTC | Jul 10, 13:15 UTC | 45m |
| 2026-07-09 | VJT768 | - | Jul 9, 17:35 UTC | Jul 9, 20:00 UTC | 2h 25m |
| 2026-07-09 | VJT768 | - | Jul 9, 10:45 UTC | Jul 9, 16:10 UTC | 5h 25m |
| 2026-07-08 | VJT768 | - | Jul 8, 11:35 UTC | Jul 8, 17:45 UTC | 6h 10m |
| 2026-07-08 | VJT768 | - | Jul 8, 07:35 UTC | Jul 8, 08:55 UTC | 1h 20m |
| 2026-07-06 | VJT768 | EWR → GLA | Jul 6, 20:00 UTC | Jul 7, 01:40 UTC | 5h 40m |
| 2026-07-06 | VJT768 | - | Jul 6, 14:15 UTC | Jul 6, 15:20 UTC | 1h 5m |
| 2026-07-04 | VJT768 | - | Jul 4, 13:30 UTC | Jul 4, 22:00 UTC | 8h 30m |
| 2026-07-04 | VJT768 | - | Jul 4, 11:15 UTC | Jul 4, 11:45 UTC | 30m |
| 2026-07-03 | VJT768 | - | Jul 3, 12:30 UTC | Jul 3, 12:45 UTC | 15m |
| 2026-07-02 | VJT768 | - | Jul 2, 15:50 UTC | Jul 3, 11:05 UTC | 19h 15m |
| 2026-07-02 | VJT768 | - | Jul 2, 11:50 UTC | Jul 3, 11:05 UTC | 23h 15m |
| 2026-07-02 | VJT768 | - | Jul 2, 11:10 UTC | Jul 3, 07:45 UTC | 20h 35m |
| 2026-06-30 | VJT768 | - | Jun 30, 19:05 UTC | Jun 30, 19:50 UTC | 45m |
| 2026-06-30 | VJT768 | - | Jun 30, 15:30 UTC | Jun 30, 18:15 UTC | 2h 45m |
| 2026-06-30 | VJT768 | - | Jun 30, 12:05 UTC | Jun 30, 13:50 UTC | 1h 45m |
| 2026-06-29 | VJT768 | SJU → TLN | Jun 29, 03:44 UTC | Jun 29, 11:50 UTC | 8h 5m |
| 2026-06-27 | VJT768 | - | Jun 27, 19:15 UTC | Jun 27, 19:29 UTC | 15m |
| 2026-06-27 | VJT768 | - | Jun 27, 17:20 UTC | Jun 27, 17:39 UTC | 20m |
| 2026-06-25 | VJT768 | - | Jun 25, 21:29 UTC | Jun 25, 22:04 UTC | 35m |
| 2026-06-24 | VJT768 | - | Jun 24, 12:20 UTC | Jun 24, 13:05 UTC | 45m |
| 2026-06-22 | VJT768 | - | Jun 22, 09:30 UTC | Jun 22, 10:05 UTC | 35m |
| 2026-06-22 | VJT768 | - | Jun 22, 02:25 UTC | Jun 22, 08:15 UTC | 5h 50m |
| 2026-06-21 | VJT768 | - | Jun 21, 00:10 UTC | Jun 21, 00:49 UTC | 40m |
| 2026-06-19 | VJT768 | - | Jun 19, 16:19 UTC | Jun 19, 20:34 UTC | 4h 15m |
| 2026-06-19 | VJT768 | - | Jun 19, 11:24 UTC | Jun 19, 14:59 UTC | 3h 35m |
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-VIT page for operator, model, and routing details .