sensors Mode-S transponder
AD2C9F
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N948TX · CESSNA 750 Citation 10 · operated by AIR PLAY II LLC
- Hex
- AD2C9F
- Octal
- 53226237
- Decimal
- 11,349,151
- Country
- US
- Tail
- N948TX
- Type
- C750
- Flights observed
- 124
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 15h ago
Last known position
Country allocation
The ICAO 24-bit address AD2C9F falls within the block assigned to United States (US) by ICAO Annex 10, Volume III. Every aircraft registered in United States 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 1 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| RKJ948 | - | 124 | 2026-07-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | RKJ948 | - | Jul 17, 19:55 UTC | Jul 17, 20:25 UTC | 30m |
| 2026-07-17 | RKJ948 | - | Jul 17, 13:10 UTC | Jul 17, 18:40 UTC | 5h 30m |
| 2026-07-16 | RKJ948 | - | Jul 16, 23:25 UTC | Jul 16, 23:59 UTC | 35m |
| 2026-07-16 | RKJ948 | AUS → TEB | Jul 16, 18:10 UTC | Jul 16, 21:25 UTC | 3h 15m |
| 2026-07-14 | RKJ948 | - | Jul 14, 03:50 UTC | Jul 14, 23:10 UTC | 19h 19m |
| 2026-07-14 | RKJ948 | - | Jul 14, 01:50 UTC | Jul 14, 23:10 UTC | 21h 19m |
| 2026-07-14 | RKJ948 | - | Jul 14, 00:55 UTC | Jul 14, 23:10 UTC | 22h 14m |
| 2026-07-13 | RKJ948 | - | Jul 13, 22:40 UTC | Jul 13, 23:35 UTC | 55m |
| 2026-07-13 | RKJ948 | - | Jul 13, 15:55 UTC | Jul 13, 20:15 UTC | 4h 20m |
| 2026-07-09 | RKJ948 | - | Jul 9, 21:40 UTC | Jul 9, 22:05 UTC | 25m |
| 2026-07-09 | RKJ948 | - | Jul 9, 14:45 UTC | Jul 9, 20:25 UTC | 5h 40m |
| 2026-07-08 | RKJ948 | - | Jul 8, 20:55 UTC | Jul 8, 22:20 UTC | 1h 25m |
| 2026-07-08 | RKJ948 | OAK → NEW | Jul 8, 16:50 UTC | Jul 8, 20:15 UTC | 3h 25m |
| 2026-07-07 | RKJ948 | NUQ → OAK | Jul 7, 19:55 UTC | Jul 7, 20:05 UTC | 10m |
| 2026-07-06 | RKJ948 | IAD → NUQ | Jul 6, 18:40 UTC | Jul 6, 23:30 UTC | 4h 50m |
| 2026-07-06 | RKJ948 | - | Jul 6, 15:40 UTC | Jul 6, 16:30 UTC | 50m |
| 2026-07-05 | RKJ948 | - | Jul 5, 22:20 UTC | Jul 6, 02:15 UTC | 3h 55m |
| 2026-07-03 | RKJ948 | - | Jul 3, 22:00 UTC | Jul 3, 23:25 UTC | 1h 25m |
| 2026-07-03 | RKJ948 | - | Jul 3, 01:40 UTC | Jul 3, 05:45 UTC | 4h 5m |
| 2026-07-02 | RKJ948 | IAD → CMH | Jul 2, 23:15 UTC | Jul 3, 00:05 UTC | 50m |
| 2026-07-02 | RKJ948 | HIO → IAD | Jul 2, 06:20 UTC | Jul 2, 10:35 UTC | 4h 15m |
| 2026-07-02 | RKJ948 | - | Jul 2, 03:15 UTC | Jul 2, 03:45 UTC | 30m |
| 2026-06-28 | RKJ948 | - | Jun 28, 15:05 UTC | Jun 28, 18:25 UTC | 3h 20m |
| 2026-06-25 | RKJ948 | - | Jun 25, 18:24 UTC | Jun 25, 21:29 UTC | 3h 5m |
| 2026-06-24 | RKJ948 | PDX → BFI | Jun 24, 20:54 UTC | Jun 24, 21:29 UTC | 35m |
| 2026-06-22 | RKJ948 | - | Jun 22, 20:34 UTC | Jun 23, 00:39 UTC | 4h 5m |
| 2026-06-19 | RKJ948 | - | Jun 19, 16:44 UTC | Jun 19, 20:09 UTC | 3h 25m |
| 2026-06-18 | RKJ948 | - | Jun 18, 22:25 UTC | Jun 18, 23:30 UTC | 1h 5m |
| 2026-06-18 | RKJ948 | - | Jun 18, 16:05 UTC | Jun 18, 21:30 UTC | 5h 25m |
| 2026-06-17 | RKJ948 | - | Jun 17, 20:20 UTC | Jun 17, 21:40 UTC | 1h 20m |
| 2026-06-17 | RKJ948 | - | Jun 17, 13:40 UTC | Jun 17, 17:00 UTC | 3h 20m |
| 2026-06-15 | RKJ948 | - | Jun 15, 18:50 UTC | Jun 16, 00:29 UTC | 5h 40m |
| 2026-06-15 | RKJ948 | - | Jun 15, 16:35 UTC | Jun 15, 16:45 UTC | 10m |
| 2026-06-14 | RKJ948 | BFI → FXE | Jun 14, 17:50 UTC | Jun 14, 22:35 UTC | 4h 45m |
| 2026-06-13 | RKJ948 | - | Jun 13, 21:50 UTC | Jun 13, 22:45 UTC | 55m |
| 2026-06-12 | RKJ948 | - | Jun 12, 16:40 UTC | Jun 12, 20:30 UTC | 3h 50m |
| 2026-06-12 | RKJ948 | - | Jun 12, 14:30 UTC | Jun 12, 15:35 UTC | 1h 5m |
| 2026-06-11 | RKJ948 | - | Jun 11, 21:20 UTC | Jun 12, 07:20 UTC | 10h 1m |
| 2026-06-10 | RKJ948 | - | Jun 10, 21:55 UTC | Jun 10, 22:30 UTC | 35m |
| 2026-06-09 | RKJ948 | - | Jun 9, 16:45 UTC | Jun 9, 19:00 UTC | 2h 15m |
| 2026-06-08 | RKJ948 | LAS → SLC | Jun 8, 22:05 UTC | Jun 8, 23:05 UTC | 1h 0m |
| 2026-06-08 | RKJ948 | - | Jun 8, 16:20 UTC | Jun 8, 21:00 UTC | 4h 40m |
| 2026-06-05 | RKJ948 | - | Jun 5, 21:25 UTC | Jun 5, 21:50 UTC | 25m |
| 2026-06-05 | RKJ948 | - | Jun 5, 15:20 UTC | Jun 5, 20:05 UTC | 4h 45m |
| 2026-06-04 | RKJ948 | - | Jun 4, 20:10 UTC | Jun 4, 21:30 UTC | 1h 20m |
| 2026-06-04 | RKJ948 | - | Jun 4, 15:35 UTC | Jun 4, 19:00 UTC | 3h 25m |
| 2026-06-03 | RKJ948 | - | Jun 3, 21:10 UTC | Jun 3, 21:50 UTC | 40m |
| 2026-06-03 | RKJ948 | - | Jun 3, 12:25 UTC | Jun 3, 20:10 UTC | 7h 45m |
| 2026-06-02 | RKJ948 | TMB → FXE | Jun 2, 22:40 UTC | Jun 2, 23:00 UTC | 20m |
| 2026-06-02 | RKJ948 | - | Jun 2, 18:55 UTC | Jun 2, 21:25 UTC | 2h 30m |
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 N948TX page for operator, model, and routing details .