sensors Mode-S transponder
4D243B
ICAO 24-bit transponder address
Currently assigned to 9H-VCR · BOMBARDIER BD-100 Challenger 350
- Hex
- 4D243B
- Octal
- 23222073
- Decimal
- 5,055,547
- Tail
- 9H-VCR
- Type
- CL35
- Flights observed
- 93
- Distinct callsigns
- 1
- Country
- -
- Last broadcast
- 4h ago
Last known position
Callsign history 1 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| VJT423 | - | 93 | 2026-07-24 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-24 | VJT423 | - | Jul 24, 19:30 UTC | Jul 24, 19:55 UTC | 25m |
| 2026-07-24 | VJT423 | IBZ → PSA | Jul 24, 17:25 UTC | Jul 24, 18:40 UTC | 1h 15m |
| 2026-07-24 | VJT423 | IBZ → IBZ | Jul 24, 16:00 UTC | Jul 24, 16:25 UTC | 25m |
| 2026-07-24 | VJT423 | MAN → IBZ | Jul 24, 09:30 UTC | Jul 24, 11:45 UTC | 2h 15m |
| 2026-07-24 | VJT423 | - | Jul 24, 07:50 UTC | Jul 24, 08:20 UTC | 30m |
| 2026-07-23 | VJT423 | - | Jul 23, 14:20 UTC | Jul 23, 16:35 UTC | 2h 15m |
| 2026-07-23 | VJT423 | - | Jul 23, 11:45 UTC | Jul 23, 12:15 UTC | 30m |
| 2026-07-23 | VJT423 | MAN → IBZ | Jul 23, 08:00 UTC | Jul 23, 10:15 UTC | 2h 15m |
| 2026-07-23 | VJT423 | - | Jul 23, 06:25 UTC | Jul 23, 06:55 UTC | 30m |
| 2026-07-22 | VJT423 | - | Jul 22, 11:10 UTC | Jul 22, 12:35 UTC | 1h 25m |
| 2026-07-21 | VJT423 | - | Jul 21, 16:45 UTC | Jul 21, 18:35 UTC | 1h 50m |
| 2026-07-21 | VJT423 | ATH → JMK | Jul 21, 15:35 UTC | Jul 21, 15:55 UTC | 20m |
| 2026-07-21 | VJT423 | LCA → ATH | Jul 21, 12:35 UTC | Jul 21, 14:00 UTC | 1h 25m |
| 2026-07-20 | VJT423 | TLV → LCA | Jul 20, 17:30 UTC | Jul 20, 18:10 UTC | 40m |
| 2026-07-20 | VJT423 | - | Jul 20, 12:50 UTC | Jul 20, 16:20 UTC | 3h 30m |
| 2026-07-20 | VJT423 | - | Jul 20, 10:35 UTC | Jul 20, 11:30 UTC | 55m |
| 2026-07-19 | VJT423 | IBZ → MPL | Jul 19, 19:45 UTC | Jul 19, 20:50 UTC | 1h 5m |
| 2026-07-19 | VJT423 | NCE → IBZ | Jul 19, 17:35 UTC | Jul 19, 18:45 UTC | 1h 10m |
| 2026-07-18 | VJT423 | LCA → NCE | Jul 18, 13:10 UTC | Jul 18, 17:00 UTC | 3h 50m |
| 2026-07-18 | VJT423 | - | Jul 18, 08:30 UTC | Jul 18, 12:00 UTC | 3h 30m |
| 2026-07-17 | VJT423 | IBZ → RKE | Jul 17, 15:00 UTC | Jul 17, 17:44 UTC | 2h 45m |
| 2026-07-17 | VJT423 | - | Jul 17, 11:45 UTC | Jul 17, 13:40 UTC | 1h 55m |
| 2026-07-05 | VJT423 | - | Jul 5, 14:05 UTC | Jul 5, 15:15 UTC | 1h 10m |
| 2026-07-05 | VJT423 | - | Jul 5, 10:30 UTC | Jul 5, 11:15 UTC | 45m |
| 2026-07-04 | VJT423 | CEQ → GVA | Jul 4, 14:35 UTC | Jul 4, 15:20 UTC | 45m |
| 2026-07-04 | VJT423 | - | Jul 4, 12:05 UTC | Jul 4, 13:40 UTC | 1h 35m |
| 2026-07-04 | VJT423 | - | Jul 4, 06:40 UTC | Jul 4, 09:40 UTC | 3h 0m |
| 2026-07-02 | VJT423 | IBZ → OUL | Jul 2, 07:45 UTC | Jul 2, 11:55 UTC | 4h 10m |
| 2026-07-01 | VJT423 | LCA → IBZ | Jul 1, 14:10 UTC | Jul 1, 18:00 UTC | 3h 50m |
| 2026-06-30 | VJT423 | TLV → LCA | Jun 30, 20:15 UTC | Jun 30, 20:55 UTC | 40m |
| 2026-06-30 | VJT423 | PEG → TLV | Jun 30, 16:30 UTC | Jun 30, 19:30 UTC | 3h 0m |
| 2026-06-30 | VJT423 | - | Jun 30, 14:20 UTC | Jun 30, 15:10 UTC | 50m |
| 2026-06-30 | VJT423 | - | Jun 30, 10:55 UTC | Jun 30, 12:30 UTC | 1h 35m |
| 2026-06-29 | VJT423 | - | Jun 29, 16:59 UTC | Jun 29, 17:24 UTC | 25m |
| 2026-06-29 | VJT423 | - | Jun 29, 14:29 UTC | Jun 29, 15:30 UTC | 1h 0m |
| 2026-06-29 | VJT423 | - | Jun 29, 06:19 UTC | Jun 29, 07:15 UTC | 55m |
| 2026-06-28 | VJT423 | - | Jun 28, 16:00 UTC | Jun 28, 17:44 UTC | 1h 45m |
| 2026-06-28 | VJT423 | - | Jun 28, 13:04 UTC | Jun 28, 14:09 UTC | 1h 5m |
| 2026-06-28 | VJT423 | - | Jun 28, 09:55 UTC | Jun 28, 12:19 UTC | 2h 25m |
| 2026-06-27 | VJT423 | - | Jun 27, 17:25 UTC | Jun 27, 17:59 UTC | 35m |
| 2026-06-27 | VJT423 | ORK → FAO | Jun 27, 13:35 UTC | Jun 27, 15:55 UTC | 2h 20m |
| 2026-06-27 | VJT423 | - | Jun 27, 09:09 UTC | Jun 27, 11:20 UTC | 2h 10m |
| 2026-06-26 | VJT423 | - | Jun 26, 10:39 UTC | Jun 26, 11:55 UTC | 1h 15m |
| 2026-06-26 | VJT423 | - | Jun 26, 07:55 UTC | Jun 26, 08:45 UTC | 50m |
| 2026-06-25 | VJT423 | - | Jun 25, 12:25 UTC | Jun 25, 13:59 UTC | 1h 35m |
| 2026-06-25 | VJT423 | - | Jun 25, 07:15 UTC | Jun 25, 11:10 UTC | 3h 55m |
| 2026-06-25 | VJT423 | - | Jun 25, 04:40 UTC | Jun 25, 05:15 UTC | 35m |
| 2026-06-24 | VJT423 | - | Jun 24, 15:35 UTC | Jun 24, 16:19 UTC | 45m |
| 2026-06-24 | VJT423 | - | Jun 24, 12:20 UTC | Jun 24, 14:04 UTC | 1h 45m |
| 2026-06-24 | VJT423 | - | Jun 24, 08:35 UTC | Jun 24, 11:24 UTC | 2h 50m |
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-VCR page for operator, model, and routing details .