sensors Mode-S transponder
AD7F99
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N969WR · GULFSTREAM G280 · operated by BANK OF UTAH TRUSTEE
- Hex
- AD7F99
- Octal
- 53277631
- Decimal
- 11,370,393
- Country
- US
- Tail
- N969WR
- Type
- G280
- Flights observed
- 82
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 20d ago
Last known position
Country allocation
The ICAO 24-bit address AD7F99 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 |
|---|---|---|---|
| N969WR | - | 82 | 2026-07-24 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-24 | N969WR | - | Jul 24, 21:50 UTC | Jul 24, 22:30 UTC | 40m |
| 2026-07-24 | N969WR | - | Jul 24, 19:15 UTC | Jul 24, 19:55 UTC | 40m |
| 2026-07-20 | N969WR | LAS → LAS | Jul 20, 18:00 UTC | Jul 20, 19:05 UTC | 1h 5m |
| 2026-07-19 | N969WR | - | Jul 19, 15:15 UTC | Jul 19, 16:40 UTC | 1h 25m |
| 2026-07-17 | N969WR | - | Jul 17, 19:40 UTC | Jul 17, 22:10 UTC | 2h 30m |
| 2026-07-05 | N969WR | - | Jul 5, 22:30 UTC | Jul 6, 02:25 UTC | 3h 55m |
| 2026-07-05 | N969WR | CLD → LAS | Jul 5, 20:20 UTC | Jul 5, 21:10 UTC | 50m |
| 2026-07-05 | N969WR | LAS → CLD | Jul 5, 18:30 UTC | Jul 5, 19:10 UTC | 40m |
| 2026-07-03 | N969WR | CLD → LAS | Jul 3, 19:20 UTC | Jul 3, 20:10 UTC | 50m |
| 2026-07-03 | N969WR | LAS → CLD | Jul 3, 17:45 UTC | Jul 3, 18:25 UTC | 40m |
| 2026-07-02 | N969WR | LNK → LAS | Jul 2, 20:35 UTC | Jul 2, 22:50 UTC | 2h 15m |
| 2026-06-28 | N969WR | LAS → LNK | Jun 28, 18:40 UTC | Jun 28, 20:34 UTC | 1h 55m |
| 2026-06-27 | N969WR | - | Jun 27, 22:15 UTC | Jun 27, 23:04 UTC | 50m |
| 2026-06-27 | N969WR | - | Jun 27, 19:59 UTC | Jun 27, 21:40 UTC | 1h 40m |
| 2026-06-27 | N969WR | - | Jun 27, 15:19 UTC | Jun 27, 17:20 UTC | 2h 0m |
| 2026-06-27 | N969WR | - | Jun 27, 13:35 UTC | Jun 27, 14:20 UTC | 45m |
| 2026-06-23 | N969WR | - | Jun 23, 02:29 UTC | Jun 23, 03:15 UTC | 45m |
| 2026-06-23 | N969WR | - | Jun 23, 00:09 UTC | Jun 23, 01:50 UTC | 1h 40m |
| 2026-06-22 | N969WR | - | Jun 22, 17:34 UTC | Jun 22, 20:24 UTC | 2h 50m |
| 2026-06-22 | N969WR | - | Jun 22, 14:34 UTC | Jun 22, 15:45 UTC | 1h 10m |
| 2026-06-22 | N969WR | - | Jun 22, 12:40 UTC | Jun 22, 13:39 UTC | 1h 0m |
| 2026-06-22 | N969WR | - | Jun 22, 00:34 UTC | Jun 22, 02:30 UTC | 1h 55m |
| 2026-06-19 | N969WR | - | Jun 19, 21:19 UTC | Jun 19, 22:55 UTC | 1h 35m |
| 2026-06-17 | N969WR | - | Jun 17, 10:10 UTC | Jun 17, 11:15 UTC | 1h 5m |
| 2026-06-14 | N969WR | - | Jun 14, 16:10 UTC | Jun 14, 17:05 UTC | 55m |
| 2026-06-12 | N969WR | - | Jun 12, 20:35 UTC | Jun 12, 21:35 UTC | 1h 0m |
| 2026-06-12 | N969WR | LAS → CLD | Jun 12, 18:05 UTC | Jun 12, 19:55 UTC | 1h 50m |
| 2026-06-09 | N969WR | - | Jun 9, 19:55 UTC | Jun 9, 21:30 UTC | 1h 35m |
| 2026-06-09 | N969WR | - | Jun 9, 16:45 UTC | Jun 9, 19:30 UTC | 2h 45m |
| 2026-06-09 | N969WR | - | Jun 9, 14:30 UTC | Jun 9, 14:50 UTC | 20m |
| 2026-06-08 | N969WR | - | Jun 8, 22:25 UTC | Jun 8, 23:10 UTC | 45m |
| 2026-06-08 | N969WR | - | Jun 8, 20:55 UTC | Jun 8, 21:40 UTC | 45m |
| 2026-06-04 | N969WR | - | Jun 4, 22:05 UTC | Jun 4, 22:50 UTC | 45m |
| 2026-06-04 | N969WR | - | Jun 4, 20:35 UTC | Jun 4, 21:20 UTC | 45m |
| 2026-06-04 | N969WR | - | Jun 4, 15:25 UTC | Jun 4, 20:00 UTC | 4h 35m |
| 2026-06-03 | N969WR | - | Jun 3, 16:05 UTC | Jun 3, 20:20 UTC | 4h 15m |
| 2026-06-02 | N969WR | - | Jun 2, 20:30 UTC | Jun 2, 21:20 UTC | 50m |
| 2026-06-02 | N969WR | - | Jun 2, 18:40 UTC | Jun 2, 19:20 UTC | 40m |
| 2026-06-01 | N969WR | VNY → LAS | Jun 1, 19:35 UTC | Jun 1, 20:10 UTC | 35m |
| 2026-05-31 | N969WR | - | May 31, 20:55 UTC | May 31, 21:10 UTC | 15m |
| 2026-05-31 | N969WR | - | May 31, 15:30 UTC | May 31, 20:20 UTC | 4h 50m |
| 2026-05-29 | N969WR | - | May 29, 18:40 UTC | May 29, 23:05 UTC | 4h 25m |
| 2026-05-29 | N969WR | - | May 29, 16:05 UTC | May 29, 16:50 UTC | 45m |
| 2026-05-25 | N969WR | IAD → LAS | May 25, 23:24 UTC | May 26, 04:00 UTC | 4h 35m |
| 2026-05-22 | N969WR | LAS → IAD | May 22, 17:35 UTC | May 22, 21:25 UTC | 3h 50m |
| 2026-05-19 | N969WR | - | May 19, 23:00 UTC | May 19, 23:50 UTC | 50m |
| 2026-05-19 | N969WR | VNY → CLD | May 19, 22:00 UTC | May 19, 22:25 UTC | 25m |
| 2026-05-18 | N969WR | - | May 18, 23:10 UTC | May 18, 23:40 UTC | 30m |
| 2026-05-18 | N969WR | LAS → CLD | May 18, 22:10 UTC | May 18, 22:50 UTC | 40m |
| 2026-05-17 | N969WR | - | May 17, 21:30 UTC | May 17, 22:10 UTC | 40m |
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 N969WR page for operator, model, and routing details .