sensors Mode-S transponder
A0920E
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N136FX · GULFSTREAM 5 · operated by TVPX AIRCRAFT SOLUTIONS INC TRUSTEE
- Hex
- A0920E
- Octal
- 50111016
- Decimal
- 10,523,150
- Country
- US
- Tail
- N136FX
- Type
- GLF5
- Flights observed
- 57
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 9d ago
Last known position
Country allocation
The ICAO 24-bit address A0920E 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 |
|---|---|---|---|
| TWY136 | - | 57 | 2026-07-26 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | TWY136 | - | Jul 26, 21:00 UTC | Jul 26, 21:30 UTC | 30m |
| 2026-07-25 | TWY136 | - | Jul 25, 20:00 UTC | Jul 25, 22:00 UTC | 2h 0m |
| 2026-07-14 | TWY136 | - | Jul 14, 19:35 UTC | Jul 14, 21:00 UTC | 1h 25m |
| 2026-07-14 | TWY136 | - | Jul 14, 00:20 UTC | Jul 14, 02:05 UTC | 1h 45m |
| 2026-07-09 | TWY136 | - | Jul 9, 02:55 UTC | Jul 9, 04:30 UTC | 1h 35m |
| 2026-07-08 | TWY136 | - | Jul 8, 23:45 UTC | Jul 9, 02:20 UTC | 2h 35m |
| 2026-07-08 | TWY136 | - | Jul 8, 21:40 UTC | Jul 8, 22:15 UTC | 35m |
| 2026-07-04 | TWY136 | - | Jul 4, 01:00 UTC | Jul 4, 01:55 UTC | 55m |
| 2026-07-03 | TWY136 | - | Jul 3, 13:10 UTC | Jul 3, 23:55 UTC | 10h 45m |
| 2026-07-01 | TWY136 | CPH → LTN | Jul 1, 16:15 UTC | Jul 1, 17:50 UTC | 1h 35m |
| 2026-06-29 | TWY136 | - | Jun 29, 10:40 UTC | Jun 29, 11:50 UTC | 1h 10m |
| 2026-06-26 | TWY136 | - | Jun 26, 23:15 UTC | Jun 27, 09:15 UTC | 10h 0m |
| 2026-06-24 | TWY136 | - | Jun 24, 17:34 UTC | Jun 24, 18:20 UTC | 45m |
| 2026-06-22 | TWY136 | - | Jun 22, 00:34 UTC | Jun 22, 01:35 UTC | 1h 0m |
| 2026-06-21 | TWY136 | APC → CLD | Jun 21, 21:05 UTC | Jun 21, 22:15 UTC | 1h 10m |
| 2026-06-20 | TWY136 | CLD → APC | Jun 20, 21:44 UTC | Jun 20, 22:50 UTC | 1h 5m |
| 2026-06-18 | TWY136 | - | Jun 18, 22:40 UTC | Jun 19, 00:20 UTC | 1h 39m |
| 2026-06-17 | TWY136 | - | Jun 17, 01:40 UTC | Jun 17, 02:45 UTC | 1h 5m |
| 2026-06-15 | TWY136 | - | Jun 15, 06:35 UTC | Jun 15, 07:15 UTC | 40m |
| 2026-06-14 | TWY136 | - | Jun 14, 20:00 UTC | Jun 14, 20:35 UTC | 35m |
| 2026-06-14 | TWY136 | - | Jun 14, 18:30 UTC | Jun 14, 19:10 UTC | 40m |
| 2026-06-13 | TWY136 | - | Jun 13, 00:00 UTC | Jun 13, 00:35 UTC | 35m |
| 2026-06-12 | TWY136 | - | Jun 12, 22:30 UTC | Jun 12, 23:10 UTC | 40m |
| 2026-06-11 | TWY136 | - | Jun 11, 01:30 UTC | Jun 11, 03:05 UTC | 1h 35m |
| 2026-06-10 | TWY136 | - | Jun 10, 17:10 UTC | Jun 10, 19:40 UTC | 2h 30m |
| 2026-06-08 | TWY136 | - | Jun 8, 15:30 UTC | Jun 8, 17:10 UTC | 1h 40m |
| 2026-06-08 | TWY136 | - | Jun 8, 00:45 UTC | Jun 8, 02:20 UTC | 1h 35m |
| 2026-06-04 | TWY136 | - | Jun 4, 20:30 UTC | Jun 4, 22:05 UTC | 1h 35m |
| 2026-05-20 | TWY136 | - | May 20, 01:40 UTC | May 20, 03:05 UTC | 1h 25m |
| 2026-05-19 | TWY136 | - | May 19, 22:35 UTC | May 19, 22:50 UTC | 15m |
| 2026-05-18 | TWY136 | - | May 18, 22:15 UTC | May 18, 22:30 UTC | 15m |
| 2026-05-18 | TWY136 | - | May 18, 19:30 UTC | May 18, 20:55 UTC | 1h 25m |
| 2026-05-15 | TWY136 | - | May 15, 21:35 UTC | May 15, 22:15 UTC | 40m |
| 2026-05-13 | TWY136 | - | May 13, 23:45 UTC | May 14, 00:30 UTC | 45m |
| 2026-05-11 | TWY136 | - | May 11, 03:15 UTC | May 11, 05:50 UTC | 2h 35m |
| 2026-05-09 | TWY136 | BUF → CLD | May 9, 12:25 UTC | May 9, 16:50 UTC | 4h 25m |
| 2026-05-08 | TWY136 | - | May 8, 15:05 UTC | May 8, 17:40 UTC | 2h 35m |
| 2026-05-06 | TWY136 | - | May 6, 23:15 UTC | May 7, 00:55 UTC | 1h 40m |
| 2026-05-06 | TWY136 | - | May 6, 20:50 UTC | May 6, 22:20 UTC | 1h 30m |
| 2026-05-04 | TWY136 | - | May 4, 00:45 UTC | May 4, 03:54 UTC | 3h 10m |
| 2026-04-30 | TWY136 | - | Apr 30, 18:35 UTC | Apr 30, 21:10 UTC | 2h 35m |
| 2026-04-29 | TWY136 | - | Apr 29, 03:04 UTC | Apr 29, 04:34 UTC | 1h 30m |
| 2026-04-24 | TWY136 | - | Apr 24, 23:40 UTC | Apr 25, 00:20 UTC | 40m |
| 2026-04-24 | TWY136 | - | Apr 24, 03:35 UTC | Apr 24, 23:05 UTC | 19h 30m |
| 2026-04-24 | TWY136 | - | Apr 24, 03:05 UTC | Apr 24, 23:05 UTC | 20h 0m |
| 2026-04-21 | TWY136 | - | Apr 21, 22:40 UTC | Apr 22, 16:45 UTC | 18h 5m |
| 2026-04-21 | TWY136 | - | Apr 21, 17:40 UTC | Apr 22, 16:45 UTC | 23h 5m |
| 2026-04-21 | TWY136 | - | Apr 21, 15:35 UTC | Apr 22, 15:25 UTC | 23h 50m |
| 2026-04-21 | TWY136 | - | Apr 21, 14:10 UTC | Apr 21, 23:40 UTC | 9h 30m |
| 2026-04-18 | TWY136 | - | Apr 18, 05:25 UTC | Apr 18, 07:00 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 N136FX page for operator, model, and routing details .