sensors Mode-S transponder
A20621
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N22995 · BOEING 787-9 Dreamliner · operated by UNITED AIRLINES INC
- Hex
- A20621
- Octal
- 50403041
- Decimal
- 10,618,401
- Country
- US
- Tail
- N22995
- Type
- B789
- Flights observed
- 239
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 2h ago
Last known position
Country allocation
The ICAO 24-bit address A20621 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 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| UAL821 | - | 28 | 2026-07-01 |
| UAL820 | - | 22 | 2026-06-30 |
| UAL893 | United Airlines | 9 | 2026-04-27 |
| UAL892 | United Airlines | 8 | 2026-04-28 |
| UAL83 | United Airlines | 8 | 2026-05-04 |
| UAL82 | United Airlines | 8 | 2026-05-04 |
| UAL839 | - | 7 | 2026-06-25 |
| UAL805 | United Airlines | 7 | 2026-04-24 |
| UAL63 | - | 7 | 2026-07-06 |
| UAL842 | - | 6 | 2026-06-26 |
| UAL198 | - | 6 | 2026-06-22 |
| UAL7 | - | 5 | 2026-07-06 |
| UAL62 | - | 5 | 2026-07-05 |
| UAL32 | - | 5 | 2026-07-03 |
| UAL153 | - | 5 | 2026-07-09 |
| UAL152 | United Airlines | 5 | 2026-07-08 |
| UAL870 | United Airlines | 4 | 2026-05-03 |
| UAL761 | United Airlines | 4 | 2026-06-02 |
| UAL713 | United Airlines | 4 | 2026-05-03 |
| UAL6 | - | 4 | 2026-07-04 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | UAL114 | - | Jul 14, 07:15 UTC | Jul 14, 07:40 UTC | 25m |
| 2026-07-13 | UAL115 | SFO → PPT | Jul 13, 20:52 UTC | Jul 14, 04:39 UTC | 7h 47m |
| 2026-07-13 | UAL115 | SFO → PPT | Jul 13, 20:50 UTC | Jul 14, 04:45 UTC | 7h 55m |
| 2026-07-13 | UAL61 | - | Jul 13, 01:20 UTC | Jul 13, 15:10 UTC | 13h 50m |
| 2026-07-12 | UAL60 | SFO → MEL | Jul 12, 06:57 UTC | Jul 12, 22:33 UTC | 15h 36m |
| 2026-07-12 | UAL60 | SFO → MEL | Jul 12, 07:45 UTC | Jul 12, 22:25 UTC | 14h 40m |
| 2026-07-11 | UAL8172 | EWR → SFO | Jul 11, 17:50 UTC | Jul 11, 23:00 UTC | 5h 10m |
| 2026-07-11 | UAL123 | LHR → EWR | Jul 11, 07:05 UTC | Jul 11, 14:15 UTC | 7h 10m |
| 2026-07-11 | UAL123 | LHR → EWR | Jul 11, 06:52 UTC | Jul 11, 14:27 UTC | 7h 35m |
| 2026-07-10 | UAL122 | - | Jul 10, 13:55 UTC | Jul 10, 20:05 UTC | 6h 10m |
| 2026-07-09 | UAL1855 | - | Jul 9, 22:10 UTC | Jul 10, 02:50 UTC | 4h 40m |
| 2026-07-09 | UAL153 | - | Jul 9, 04:50 UTC | Jul 9, 17:55 UTC | 13h 5m |
| 2026-07-09 | UAL153 | - | Jul 9, 02:00 UTC | Jul 9, 02:15 UTC | 15m |
| 2026-07-09 | UAL153 | SGN → HKG | Jul 9, 00:19 UTC | Jul 9, 02:27 UTC | 2h 8m |
| 2026-07-08 | UAL152 | LAX → HKG | Jul 8, 13:10 UTC | Jul 8, 13:25 UTC | 15m |
| 2026-07-07 | UAL152 | LAX → HKG | Jul 7, 20:05 UTC | Jul 8, 10:10 UTC | 14h 5m |
| 2026-07-07 | UAL33 | - | Jul 7, 08:00 UTC | Jul 7, 17:20 UTC | 9h 20m |
| 2026-07-06 | UAL7 | - | Jul 6, 15:55 UTC | Jul 7, 04:45 UTC | 12h 50m |
| 2026-07-06 | UAL63 | - | Jul 6, 01:20 UTC | Jul 6, 10:15 UTC | 8h 55m |
| 2026-07-06 | UAL63 | GRU → IAH | Jul 6, 01:21 UTC | Jul 6, 10:13 UTC | 8h 52m |
| 2026-07-05 | UAL62 | - | Jul 5, 00:00 UTC | Jul 5, 09:25 UTC | 9h 25m |
| 2026-07-04 | UAL6 | - | Jul 4, 08:15 UTC | Jul 4, 19:40 UTC | 11h 25m |
| 2026-07-03 | UAL32 | - | Jul 3, 18:40 UTC | Jul 3, 19:40 UTC | 1h 0m |
| 2026-07-03 | UAL32 | LAX → NRT | Jul 3, 18:15 UTC | Jul 4, 05:20 UTC | 11h 5m |
| 2026-07-02 | UAL99 | - | Jul 2, 23:55 UTC | Jul 3, 13:35 UTC | 13h 40m |
| 2026-07-02 | UAL98 | LAX → MEL | Jul 2, 06:15 UTC | Jul 2, 21:30 UTC | 15h 15m |
| 2026-07-01 | UAL821 | - | Jul 1, 14:05 UTC | Jul 1, 17:55 UTC | 3h 50m |
| 2026-07-01 | UAL821 | HKG → LAX | Jul 1, 14:06 UTC | Jul 2, 02:34 UTC | 12h 28m |
| 2026-07-01 | UAL821 | HKG → LAX | Jul 1, 14:06 UTC | Jul 2, 02:30 UTC | 12h 24m |
| 2026-07-01 | UAL821 | - | Jul 1, 09:00 UTC | Jul 1, 09:10 UTC | 10m |
| 2026-07-01 | UAL821 | BKK → HKG | Jul 1, 09:05 UTC | Jul 1, 11:43 UTC | 2h 38m |
| 2026-06-30 | UAL820 | - | Jun 30, 23:55 UTC | Jul 1, 02:15 UTC | 2h 20m |
| 2026-06-30 | UAL820 | - | Jun 30, 07:20 UTC | Jun 30, 20:15 UTC | 12h 55m |
| 2026-06-30 | UAL820 | LAX → HKG | Jun 30, 07:14 UTC | Jun 30, 21:19 UTC | 14h 5m |
| 2026-06-29 | UAL353 | - | Jun 29, 22:55 UTC | Jun 30, 03:50 UTC | 4h 56m |
| 2026-06-29 | UAL2096 | LAX → EWR | Jun 29, 15:45 UTC | Jun 29, 20:15 UTC | 4h 30m |
| 2026-06-28 | UAL821 | - | Jun 28, 14:09 UTC | Jun 29, 03:05 UTC | 12h 55m |
| 2026-06-28 | UAL821 | HKG → LAX | Jun 28, 14:06 UTC | Jun 29, 03:00 UTC | 12h 54m |
| 2026-06-28 | UAL821 | - | Jun 28, 11:14 UTC | Jun 28, 11:25 UTC | 10m |
| 2026-06-28 | UAL821 | - | Jun 28, 09:05 UTC | Jun 28, 09:34 UTC | 30m |
| 2026-06-28 | UAL821 | BKK → HKG | Jun 28, 09:05 UTC | Jun 28, 11:23 UTC | 2h 18m |
| 2026-06-28 | UAL820 | - | Jun 28, 01:34 UTC | Jun 28, 02:05 UTC | 30m |
| 2026-06-27 | UAL820 | - | Jun 27, 23:55 UTC | Jun 28, 00:04 UTC | 10m |
| 2026-06-27 | UAL820 | - | Jun 27, 07:34 UTC | Jun 27, 21:29 UTC | 13h 55m |
| 2026-06-26 | UAL353 | - | Jun 26, 23:19 UTC | Jun 27, 04:24 UTC | 5h 5m |
| 2026-06-26 | UAL2096 | LAX → EWR | Jun 26, 16:20 UTC | Jun 26, 21:04 UTC | 4h 45m |
| 2026-06-26 | UAL842 | SYD → LAX | Jun 26, 00:15 UTC | Jun 26, 13:10 UTC | 12h 55m |
| 2026-06-25 | UAL842 | SYD → LAX | Jun 25, 23:51 UTC | Jun 26, 13:02 UTC | 13h 11m |
| 2026-06-25 | UAL839 | - | Jun 25, 06:25 UTC | Jun 25, 20:54 UTC | 14h 30m |
| 2026-06-24 | UAL821 | HKG → LAX | Jun 24, 14:06 UTC | Jun 25, 02:03 UTC | 11h 57m |
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 N22995 page for operator, model, and routing details .