sensors Mode-S transponder
A26F81
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N256TR · operated by CORPORATE HOSPITALITY AVIATION LLC
- Hex
- A26F81
- Octal
- 50467601
- Decimal
- 10,645,377
- Country
- US
- Tail
- N256TR
- Type
- SR20
- Flights observed
- 73
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- Jul 26, 22:00 UTC
Last known position
Country allocation
The ICAO 24-bit address A26F81 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 |
|---|---|---|---|
| N256TR | - | 73 | 2026-07-26 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | N256TR | - | Jul 26, 21:30 UTC | Jul 26, 22:00 UTC | 30m |
| 2026-07-25 | N256TR | ADS → ADS | Jul 25, 18:55 UTC | Jul 25, 20:15 UTC | 1h 20m |
| 2026-07-25 | N256TR | - | Jul 25, 13:50 UTC | Jul 25, 15:50 UTC | 2h 0m |
| 2026-07-24 | N256TR | - | Jul 24, 03:05 UTC | Jul 24, 04:25 UTC | 1h 20m |
| 2026-07-23 | N256TR | ADS → OKC | Jul 23, 22:50 UTC | Jul 24, 00:00 UTC | 1h 10m |
| 2026-07-23 | N256TR | - | Jul 23, 14:10 UTC | Jul 23, 15:25 UTC | 1h 15m |
| 2026-07-21 | N256TR | ADS → ADS | Jul 21, 16:05 UTC | Jul 21, 17:30 UTC | 1h 25m |
| 2026-07-19 | N256TR | ADS → ADS | Jul 19, 20:00 UTC | Jul 19, 21:55 UTC | 1h 55m |
| 2026-07-19 | N256TR | ADS → ADS | Jul 19, 15:15 UTC | Jul 19, 16:50 UTC | 1h 35m |
| 2026-07-18 | N256TR | ADS → ADS | Jul 18, 14:20 UTC | Jul 18, 16:10 UTC | 1h 50m |
| 2026-07-11 | N256TR | ADS → ADS | Jul 11, 15:15 UTC | Jul 11, 16:55 UTC | 1h 40m |
| 2026-07-08 | N256TR | - | Jul 8, 15:15 UTC | Jul 8, 15:45 UTC | 30m |
| 2026-07-08 | N256TR | - | Jul 8, 13:30 UTC | Jul 8, 14:00 UTC | 30m |
| 2026-07-01 | N256TR | - | Jul 1, 19:55 UTC | Jul 1, 21:10 UTC | 1h 15m |
| 2026-07-01 | N256TR | - | Jul 1, 14:35 UTC | Jul 1, 15:40 UTC | 1h 5m |
| 2026-06-30 | N256TR | ADS → ADS | Jun 30, 20:15 UTC | Jun 30, 21:55 UTC | 1h 40m |
| 2026-06-27 | N256TR | - | Jun 27, 21:04 UTC | Jun 27, 21:44 UTC | 40m |
| 2026-06-27 | N256TR | - | Jun 27, 15:10 UTC | Jun 27, 15:45 UTC | 35m |
| 2026-06-26 | N256TR | - | Jun 26, 13:10 UTC | Jun 26, 15:29 UTC | 2h 20m |
| 2026-06-21 | N256TR | - | Jun 21, 01:05 UTC | Jun 21, 01:45 UTC | 40m |
| 2026-06-20 | N256TR | - | Jun 20, 22:10 UTC | Jun 20, 22:50 UTC | 40m |
| 2026-06-18 | N256TR | ADS → ADS | Jun 18, 13:25 UTC | Jun 18, 15:20 UTC | 1h 55m |
| 2026-06-12 | N256TR | - | Jun 12, 04:20 UTC | Jun 12, 05:15 UTC | 55m |
| 2026-06-12 | N256TR | - | Jun 12, 02:30 UTC | Jun 12, 03:30 UTC | 1h 0m |
| 2026-06-10 | N256TR | - | Jun 10, 18:15 UTC | Jun 10, 19:45 UTC | 1h 30m |
| 2026-06-10 | N256TR | - | Jun 10, 13:50 UTC | Jun 10, 14:25 UTC | 35m |
| 2026-06-10 | N256TR | - | Jun 10, 12:25 UTC | Jun 10, 13:10 UTC | 45m |
| 2026-06-02 | N256TR | - | Jun 2, 16:40 UTC | Jun 2, 17:10 UTC | 30m |
| 2026-06-02 | N256TR | - | Jun 2, 14:50 UTC | Jun 2, 15:35 UTC | 45m |
| 2026-06-01 | N256TR | - | Jun 1, 16:50 UTC | Jun 1, 17:15 UTC | 25m |
| 2026-06-01 | N256TR | - | Jun 1, 14:50 UTC | Jun 1, 16:15 UTC | 1h 25m |
| 2026-05-30 | N256TR | - | May 30, 20:35 UTC | May 30, 22:10 UTC | 1h 35m |
| 2026-05-30 | N256TR | - | May 30, 14:15 UTC | May 30, 15:55 UTC | 1h 40m |
| 2026-05-29 | N256TR | - | May 29, 16:20 UTC | May 29, 16:55 UTC | 35m |
| 2026-05-29 | N256TR | - | May 29, 15:10 UTC | May 29, 15:40 UTC | 30m |
| 2026-05-16 | N256TR | - | May 16, 16:45 UTC | May 16, 19:00 UTC | 2h 15m |
| 2026-05-16 | N256TR | - | May 16, 13:25 UTC | May 16, 14:01 UTC | 35m |
| 2026-05-04 | N256TR | - | May 4, 15:35 UTC | May 4, 16:35 UTC | 1h 0m |
| 2026-05-02 | N256TR | - | May 2, 17:50 UTC | May 2, 19:25 UTC | 1h 35m |
| 2026-05-02 | N256TR | - | May 2, 15:05 UTC | May 2, 15:45 UTC | 40m |
| 2026-04-29 | N256TR | - | Apr 29, 19:55 UTC | Apr 29, 20:45 UTC | 50m |
| 2026-04-29 | N256TR | - | Apr 29, 18:05 UTC | Apr 29, 19:05 UTC | 1h 0m |
| 2026-04-29 | N256TR | ADS → ADS | Apr 29, 12:45 UTC | Apr 29, 13:50 UTC | 1h 5m |
| 2026-04-28 | N256TR | ADS → ADS | Apr 28, 17:45 UTC | Apr 28, 18:20 UTC | 35m |
| 2026-04-27 | N256TR | - | Apr 27, 21:50 UTC | Apr 27, 22:25 UTC | 35m |
| 2026-04-27 | N256TR | - | Apr 27, 19:20 UTC | Apr 27, 20:00 UTC | 40m |
| 2026-04-27 | N256TR | - | Apr 27, 16:55 UTC | Apr 27, 17:35 UTC | 40m |
| 2026-04-27 | N256TR | - | Apr 27, 15:15 UTC | Apr 27, 16:00 UTC | 45m |
| 2026-04-26 | N256TR | - | Apr 26, 19:30 UTC | Apr 26, 21:55 UTC | 2h 25m |
| 2026-04-25 | N256TR | - | Apr 25, 21:55 UTC | Apr 25, 23:30 UTC | 1h 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 N256TR page for operator, model, and routing details .