sensors Mode-S transponder
A27E31
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N26RX · GULFSTREAM 5 · operated by IQVIA TRANSPORTATION SERVICES CORP
- Hex
- A27E31
- Octal
- 50477061
- Decimal
- 10,649,137
- Country
- US
- Tail
- N26RX
- Type
- GLF5
- Flights observed
- 62
- Distinct callsigns
- 2
- Country
- US
- Last broadcast
- 14h ago
Current position
Country allocation
The ICAO 24-bit address A27E31 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 2 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | N26RX | RDU → BED | Jul 14, 01:20 UTC | Jul 14, 02:50 UTC | 1h 30m |
| 2026-07-13 | N26RX | - | Jul 13, 16:10 UTC | Jul 13, 17:40 UTC | 1h 30m |
| 2026-07-12 | N26RX | RDU → MDW | Jul 12, 22:55 UTC | Jul 13, 00:30 UTC | 1h 35m |
| 2026-07-12 | N26RX | - | Jul 12, 18:45 UTC | Jul 12, 21:45 UTC | 3h 0m |
| 2026-07-12 | N26RX | - | Jul 12, 14:01 UTC | Jul 12, 17:35 UTC | 3h 35m |
| 2026-07-11 | EJM261 | - | Jul 11, 23:20 UTC | Jul 11, 23:45 UTC | 25m |
| 2026-07-11 | EJM261 | VNY → TEB | Jul 11, 18:05 UTC | Jul 11, 22:45 UTC | 4h 40m |
| 2026-07-10 | EJM261 | LUK → VNY | Jul 10, 17:45 UTC | Jul 10, 23:35 UTC | 5h 50m |
| 2026-07-10 | EJM261 | - | Jul 10, 14:45 UTC | Jul 10, 16:35 UTC | 1h 50m |
| 2026-07-10 | EJM261 | - | Jul 10, 02:45 UTC | Jul 10, 03:35 UTC | 50m |
| 2026-07-09 | EJM261 | DWH → BWI | Jul 9, 18:45 UTC | Jul 9, 21:35 UTC | 2h 50m |
| 2026-07-09 | EJM261 | - | Jul 9, 17:30 UTC | Jul 9, 17:50 UTC | 20m |
| 2026-07-08 | EJM261 | - | Jul 8, 20:55 UTC | Jul 8, 23:40 UTC | 2h 45m |
| 2026-07-08 | EJM261 | - | Jul 8, 18:05 UTC | Jul 8, 19:00 UTC | 55m |
| 2026-07-07 | EJM261 | - | Jul 7, 14:00 UTC | Jul 7, 18:30 UTC | 4h 30m |
| 2026-07-07 | EJM261 | - | Jul 7, 11:50 UTC | Jul 7, 13:05 UTC | 1h 15m |
| 2026-06-28 | EJM261 | - | Jun 28, 16:35 UTC | Jun 28, 16:55 UTC | 20m |
| 2026-06-28 | EJM261 | - | Jun 28, 14:59 UTC | Jun 28, 15:44 UTC | 45m |
| 2026-06-27 | EJM261 | - | Jun 27, 19:05 UTC | Jun 28, 15:44 UTC | 20h 40m |
| 2026-06-21 | EJM261 | JAX → OXC | Jun 21, 22:34 UTC | Jun 22, 00:29 UTC | 1h 55m |
| 2026-06-21 | EJM261 | - | Jun 21, 15:19 UTC | Jun 21, 21:34 UTC | 6h 15m |
| 2026-06-21 | EJM261 | - | Jun 21, 13:15 UTC | Jun 21, 13:39 UTC | 25m |
| 2026-06-12 | N26RX | - | Jun 12, 17:10 UTC | Jun 12, 18:20 UTC | 1h 10m |
| 2026-06-12 | N26RX | - | Jun 12, 08:30 UTC | Jun 12, 16:20 UTC | 7h 50m |
| 2026-06-11 | N26RX | - | Jun 11, 11:20 UTC | Jun 11, 12:40 UTC | 1h 20m |
| 2026-06-10 | N26RX | - | Jun 10, 15:40 UTC | Jun 10, 17:25 UTC | 1h 45m |
| 2026-06-09 | N26RX | - | Jun 9, 16:45 UTC | Jun 9, 17:55 UTC | 1h 10m |
| 2026-06-08 | N26RX | - | Jun 8, 11:30 UTC | Jun 8, 19:05 UTC | 7h 35m |
| 2026-06-07 | N26RX | - | Jun 7, 19:00 UTC | Jun 7, 20:15 UTC | 1h 15m |
| 2026-06-04 | N26RX | - | Jun 4, 22:40 UTC | Jun 5, 00:00 UTC | 1h 20m |
| 2026-06-04 | N26RX | - | Jun 4, 21:15 UTC | Jun 4, 22:15 UTC | 1h 0m |
| 2026-06-04 | N26RX | - | Jun 4, 11:10 UTC | Jun 4, 12:20 UTC | 1h 10m |
| 2026-06-03 | N26RX | - | Jun 3, 20:00 UTC | Jun 3, 21:10 UTC | 1h 10m |
| 2026-06-01 | N26RX | - | Jun 1, 17:25 UTC | Jun 1, 17:45 UTC | 20m |
| 2026-06-01 | N26RX | - | Jun 1, 15:05 UTC | Jun 1, 16:45 UTC | 1h 40m |
| 2026-06-01 | N26RX | - | Jun 1, 14:15 UTC | Jun 1, 14:30 UTC | 15m |
| 2026-05-31 | EJM261 | - | May 31, 12:15 UTC | May 31, 12:35 UTC | 20m |
| 2026-05-30 | EJM261 | - | May 30, 00:00 UTC | May 30, 11:10 UTC | 11h 10m |
| 2026-05-27 | EJM261 | - | May 27, 13:10 UTC | May 27, 16:15 UTC | 3h 5m |
| 2026-05-24 | EJM261 | - | May 24, 02:00 UTC | May 24, 11:10 UTC | 9h 10m |
| 2026-05-22 | N26RX | - | May 22, 20:25 UTC | May 22, 20:50 UTC | 25m |
| 2026-05-12 | N26RX | - | May 12, 20:55 UTC | May 12, 22:10 UTC | 1h 15m |
| 2026-05-12 | N26RX | BOS → RDU | May 12, 18:35 UTC | May 12, 20:05 UTC | 1h 30m |
| 2026-05-11 | N26RX | - | May 11, 16:25 UTC | May 11, 17:20 UTC | 55m |
| 2026-05-11 | N26RX | RDU → TTN | May 11, 12:25 UTC | May 11, 13:20 UTC | 55m |
| 2026-05-10 | N26RX | HVN → RDU | May 10, 19:40 UTC | May 10, 21:00 UTC | 1h 20m |
| 2026-05-07 | N26RX | - | May 7, 21:45 UTC | May 7, 22:50 UTC | 1h 5m |
| 2026-05-07 | N26RX | - | May 7, 19:50 UTC | May 7, 21:15 UTC | 1h 25m |
| 2026-05-07 | N26RX | BOS → TEB | May 7, 10:50 UTC | May 7, 11:50 UTC | 1h 0m |
| 2026-05-06 | N26RX | TEB → BOS | May 6, 22:35 UTC | May 6, 23:40 UTC | 1h 5m |
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 N26RX page for operator, model, and routing details .