sensors Mode-S transponder
4D2530
ICAO 24-bit transponder address
Currently assigned to 9H-VFO · BOMBARDIER CL-600 Challenger
- Hex
- 4D2530
- Octal
- 23222460
- Decimal
- 5,055,792
- Tail
- 9H-VFO
- Type
- CL60
- Flights observed
- 80
- Distinct callsigns
- 4
- Country
- -
- Last broadcast
- 4h ago
Last known position
Callsign history 4 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-24 | VJT537 | - | Jul 24, 22:10 UTC | Jul 24, 22:25 UTC | 15m |
| 2026-07-24 | VJT537 | - | Jul 24, 20:55 UTC | Jul 24, 21:20 UTC | 25m |
| 2026-07-24 | VJT537 | - | Jul 24, 18:05 UTC | Jul 24, 19:40 UTC | 1h 35m |
| 2026-07-24 | VJT537 | - | Jul 24, 12:50 UTC | Jul 24, 13:40 UTC | 50m |
| 2026-07-24 | VJT537 | - | Jul 24, 09:15 UTC | Jul 24, 10:30 UTC | 1h 15m |
| 2026-07-23 | VJT537 | - | Jul 23, 14:15 UTC | Jul 23, 18:15 UTC | 4h 0m |
| 2026-07-23 | VJT537 | - | Jul 23, 12:55 UTC | Jul 23, 13:25 UTC | 30m |
| 2026-07-22 | VJT537 | - | Jul 22, 13:15 UTC | Jul 22, 13:55 UTC | 40m |
| 2026-07-22 | VJT537 | - | Jul 22, 10:20 UTC | Jul 22, 12:05 UTC | 1h 45m |
| 2026-07-21 | VJT537 | - | Jul 21, 14:00 UTC | Jul 21, 15:05 UTC | 1h 5m |
| 2026-07-21 | VJT537 | - | Jul 21, 10:25 UTC | Jul 21, 12:25 UTC | 2h 0m |
| 2026-07-21 | VJT537 | ABZ → FRA | Jul 21, 06:40 UTC | Jul 21, 08:15 UTC | 1h 35m |
| 2026-07-20 | VJT537 | NCE → ABZ | Jul 20, 15:25 UTC | Jul 20, 17:50 UTC | 2h 25m |
| 2026-07-20 | VJT537 | - | Jul 20, 12:50 UTC | Jul 20, 14:00 UTC | 1h 10m |
| 2026-07-20 | VJT537 | - | Jul 20, 09:30 UTC | Jul 20, 11:20 UTC | 1h 50m |
| 2026-07-20 | VJT537 | - | Jul 20, 06:45 UTC | Jul 20, 07:25 UTC | 40m |
| 2026-07-18 | VJT537 | - | Jul 18, 16:50 UTC | Jul 18, 19:15 UTC | 2h 25m |
| 2026-07-18 | VJT537 | - | Jul 18, 12:50 UTC | Jul 18, 15:10 UTC | 2h 20m |
| 2026-07-18 | VJT537 | BQH → FAB | Jul 18, 10:55 UTC | Jul 18, 11:30 UTC | 35m |
| 2026-07-17 | VJT966R | - | Jul 17, 12:00 UTC | Jul 17, 13:40 UTC | 1h 40m |
| 2026-07-16 | VJT966R | - | Jul 16, 12:05 UTC | Jul 17, 12:00 UTC | 23h 55m |
| 2026-07-16 | VJT966R | - | Jul 16, 11:15 UTC | Jul 16, 13:30 UTC | 2h 15m |
| 2026-07-15 | VJT537 | DUB → BFS | Jul 15, 18:20 UTC | Jul 15, 18:40 UTC | 20m |
| 2026-07-15 | VJT537 | - | Jul 15, 14:55 UTC | Jul 15, 17:00 UTC | 2h 5m |
| 2026-07-15 | VJT537 | - | Jul 15, 12:20 UTC | Jul 15, 13:50 UTC | 1h 30m |
| 2026-07-14 | VJT537 | FNC → LBG | Jul 14, 12:50 UTC | Jul 14, 15:45 UTC | 2h 55m |
| 2026-07-14 | VJT537 | - | Jul 14, 10:55 UTC | Jul 14, 11:00 UTC | 5m |
| 2026-07-14 | VJT537 | - | Jul 14, 06:40 UTC | Jul 14, 08:35 UTC | 1h 55m |
| 2026-07-13 | VJT537 | - | Jul 13, 05:05 UTC | Jul 13, 07:50 UTC | 2h 45m |
| 2026-07-12 | VJT537 | - | Jul 12, 23:00 UTC | Jul 13, 02:10 UTC | 3h 10m |
| 2026-07-12 | VJT537 | - | Jul 12, 17:01 UTC | Jul 12, 19:15 UTC | 2h 15m |
| 2026-07-12 | VJT537 | - | Jul 12, 11:15 UTC | Jul 12, 13:25 UTC | 2h 10m |
| 2026-07-12 | VJT537 | - | Jul 12, 08:45 UTC | Jul 12, 10:35 UTC | 1h 50m |
| 2026-07-12 | VJT537 | - | Jul 12, 06:50 UTC | Jul 12, 07:05 UTC | 15m |
| 2026-07-11 | VJT537 | - | Jul 11, 14:55 UTC | Jul 11, 15:50 UTC | 55m |
| 2026-07-11 | VJT537 | - | Jul 11, 12:05 UTC | Jul 11, 13:15 UTC | 1h 10m |
| 2026-07-10 | VJT537 | - | Jul 10, 11:35 UTC | Jul 10, 12:30 UTC | 55m |
| 2026-07-10 | VJT537 | - | Jul 10, 08:45 UTC | Jul 10, 10:15 UTC | 1h 30m |
| 2026-07-10 | VJT537 | - | Jul 10, 06:35 UTC | Jul 10, 06:55 UTC | 20m |
| 2026-07-09 | VJT537 | - | Jul 9, 09:10 UTC | Jul 9, 13:15 UTC | 4h 5m |
| 2026-07-08 | VJT537 | - | Jul 8, 16:10 UTC | Jul 9, 13:15 UTC | 21h 5m |
| 2026-07-08 | VJT537 | - | Jul 8, 11:10 UTC | Jul 8, 14:10 UTC | 3h 0m |
| 2026-07-07 | VJT537 | - | Jul 7, 16:15 UTC | Jul 7, 19:00 UTC | 2h 45m |
| 2026-07-07 | VJT537 | - | Jul 7, 12:05 UTC | Jul 7, 15:00 UTC | 2h 55m |
| 2026-07-06 | VJT438H | - | Jul 6, 17:30 UTC | Jul 6, 19:55 UTC | 2h 25m |
| 2026-07-06 | VJT438H | - | Jul 6, 09:10 UTC | Jul 6, 15:40 UTC | 6h 30m |
| 2026-07-02 | VJT537 | - | Jul 2, 16:40 UTC | Jul 2, 17:20 UTC | 40m |
| 2026-07-02 | VJT361Z | - | Jul 2, 09:30 UTC | Jul 2, 15:20 UTC | 5h 50m |
| 2026-07-01 | VJT361Z | - | Jul 1, 14:05 UTC | Jul 2, 14:00 UTC | 23h 55m |
| 2026-07-01 | VJT361Z | - | Jul 1, 12:05 UTC | Jul 2, 12:00 UTC | 23h 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-VFO page for operator, model, and routing details .