sensors Mode-S transponder
AD48EF
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N955TM · BOMBARDIER CL-600 Challenger
- Hex
- AD48EF
- Octal
- 53244357
- Decimal
- 11,356,399
- Country
- US
- Tail
- N955TM
- Type
- CL60
- Flights observed
- 51
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 14h ago
Last known position
Country allocation
The ICAO 24-bit address AD48EF 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 |
|---|---|---|---|
| N955TM | - | 51 | 2026-06-12 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-12 | N955TM | PNE → ROC | Jun 12, 12:20 UTC | Jun 12, 13:10 UTC | 50m |
| 2026-06-10 | N955TM | SLC → PNE | Jun 10, 16:25 UTC | Jun 10, 20:30 UTC | 4h 5m |
| 2026-06-10 | N955TM | MSN → SLC | Jun 10, 01:20 UTC | Jun 10, 04:20 UTC | 3h 0m |
| 2026-06-09 | N955TM | - | Jun 9, 23:40 UTC | Jun 10, 00:25 UTC | 45m |
| 2026-06-09 | N955TM | - | Jun 9, 18:40 UTC | Jun 9, 19:20 UTC | 40m |
| 2026-06-08 | N955TM | - | Jun 8, 20:40 UTC | Jun 9, 00:00 UTC | 3h 20m |
| 2026-06-05 | N955TM | - | Jun 5, 01:45 UTC | Jun 5, 02:00 UTC | 15m |
| 2026-06-04 | N955TM | - | Jun 4, 19:45 UTC | Jun 5, 00:55 UTC | 5h 10m |
| 2026-06-03 | N955TM | VNY → EWR | Jun 3, 22:40 UTC | Jun 4, 03:40 UTC | 5h 0m |
| 2026-06-03 | N955TM | LAS → VNY | Jun 3, 20:30 UTC | Jun 3, 21:10 UTC | 40m |
| 2026-06-03 | N955TM | VNY → LAS | Jun 3, 05:00 UTC | Jun 3, 05:45 UTC | 45m |
| 2026-06-03 | N955TM | OAK → VNY | Jun 3, 03:20 UTC | Jun 3, 04:10 UTC | 50m |
| 2026-06-02 | N955TM | LAS → OAK | Jun 2, 23:30 UTC | Jun 3, 00:35 UTC | 1h 5m |
| 2026-06-01 | N955TM | - | Jun 1, 19:10 UTC | Jun 1, 21:25 UTC | 2h 15m |
| 2026-06-01 | N955TM | - | Jun 1, 16:20 UTC | Jun 1, 16:55 UTC | 35m |
| 2026-05-30 | N955TM | - | May 30, 18:50 UTC | May 30, 20:50 UTC | 2h 0m |
| 2026-05-26 | N955TM | - | May 26, 21:25 UTC | May 26, 22:20 UTC | 55m |
| 2026-05-05 | N955TM | - | May 5, 16:00 UTC | May 5, 18:45 UTC | 2h 45m |
| 2026-05-04 | N955TM | - | May 4, 18:40 UTC | May 4, 20:10 UTC | 1h 30m |
| 2026-05-03 | N955TM | YYZ → LAS | May 3, 21:24 UTC | May 4, 01:55 UTC | 4h 30m |
| 2026-05-03 | N955TM | LAS → YYZ | May 3, 16:40 UTC | May 3, 20:25 UTC | 3h 45m |
| 2026-05-01 | N955TM | - | May 1, 17:00 UTC | May 1, 19:00 UTC | 2h 0m |
| 2026-04-30 | N955TM | - | Apr 30, 19:30 UTC | Apr 30, 20:15 UTC | 45m |
| 2026-04-30 | N955TM | - | Apr 30, 12:40 UTC | Apr 30, 16:30 UTC | 3h 50m |
| 2026-04-29 | N955TM | - | Apr 29, 21:35 UTC | Apr 29, 22:20 UTC | 45m |
| 2026-04-29 | N955TM | - | Apr 29, 17:05 UTC | Apr 29, 20:50 UTC | 3h 45m |
| 2026-04-29 | N955TM | - | Apr 29, 00:05 UTC | Apr 29, 01:10 UTC | 1h 5m |
| 2026-04-28 | N955TM | - | Apr 28, 22:25 UTC | Apr 28, 23:00 UTC | 35m |
| 2026-04-28 | N955TM | - | Apr 28, 20:00 UTC | Apr 28, 20:40 UTC | 40m |
| 2026-04-27 | N955TM | - | Apr 27, 15:45 UTC | Apr 27, 21:10 UTC | 5h 25m |
| 2026-04-26 | N955TM | - | Apr 26, 23:45 UTC | Apr 27, 01:45 UTC | 2h 0m |
| 2026-04-26 | N955TM | - | Apr 26, 20:30 UTC | Apr 26, 23:05 UTC | 2h 35m |
| 2026-04-26 | N955TM | - | Apr 26, 01:40 UTC | Apr 26, 02:20 UTC | 40m |
| 2026-04-25 | N955TM | - | Apr 25, 23:55 UTC | Apr 26, 00:35 UTC | 40m |
| 2026-04-24 | N955TM | SLC → LAS | Apr 24, 21:00 UTC | Apr 24, 22:05 UTC | 1h 5m |
| 2026-04-24 | N955TM | LAS → SLC | Apr 24, 17:35 UTC | Apr 24, 18:30 UTC | 55m |
| 2026-04-23 | N955TM | - | Apr 23, 19:00 UTC | Apr 23, 19:40 UTC | 40m |
| 2026-04-23 | N955TM | - | Apr 23, 01:35 UTC | Apr 23, 03:20 UTC | 1h 45m |
| 2026-04-22 | N955TM | SJC → SFO | Apr 22, 23:00 UTC | Apr 22, 23:15 UTC | 15m |
| 2026-04-20 | N955TM | - | Apr 20, 23:05 UTC | Apr 21, 01:00 UTC | 1h 55m |
| 2026-04-19 | N955TM | - | Apr 19, 23:55 UTC | Apr 20, 02:00 UTC | 2h 5m |
| 2026-04-19 | N955TM | - | Apr 19, 20:25 UTC | Apr 19, 21:05 UTC | 40m |
| 2026-04-17 | N955TM | - | Apr 17, 21:25 UTC | Apr 17, 22:50 UTC | 1h 25m |
| 2026-04-17 | N955TM | - | Apr 17, 19:25 UTC | Apr 17, 21:20 UTC | 1h 55m |
| 2026-04-17 | N955TM | - | Apr 17, 18:55 UTC | Apr 17, 19:20 UTC | 25m |
| 2026-04-17 | N955TM | - | Apr 17, 15:20 UTC | Apr 17, 16:50 UTC | 1h 30m |
| 2026-04-17 | N955TM | - | Apr 17, 15:00 UTC | Apr 17, 15:15 UTC | 15m |
| 2026-04-16 | N955TM | - | Apr 16, 19:15 UTC | Apr 16, 20:15 UTC | 1h 0m |
| 2026-04-16 | N955TM | - | Apr 16, 17:15 UTC | Apr 16, 19:10 UTC | 1h 55m |
| 2026-04-16 | N955TM | - | Apr 16, 16:00 UTC | Apr 16, 17:10 UTC | 1h 10m |
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 N955TM page for operator, model, and routing details .