sensors Mode-S transponder
A210A3
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N232HF · operated by HF JET LLC
- Hex
- A210A3
- Octal
- 50410243
- Decimal
- 10,621,091
- Country
- US
- Tail
- N232HF
- Type
- GLEX
- Flights observed
- 71
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 10h ago
Last known position
Country allocation
The ICAO 24-bit address A210A3 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 |
|---|---|---|---|
| N232HF | - | 71 | 2026-07-20 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-20 | N232HF | VNY → LAX | Jul 20, 20:25 UTC | Jul 20, 20:40 UTC | 15m |
| 2026-07-16 | N232HF | - | Jul 16, 02:30 UTC | Jul 16, 03:20 UTC | 50m |
| 2026-07-15 | N232HF | - | Jul 15, 17:15 UTC | Jul 15, 18:00 UTC | 45m |
| 2026-07-15 | N232HF | CLD → VNY | Jul 15, 04:35 UTC | Jul 15, 05:10 UTC | 35m |
| 2026-07-15 | N232HF | - | Jul 15, 03:00 UTC | Jul 15, 04:10 UTC | 1h 10m |
| 2026-07-12 | N232HF | - | Jul 12, 18:30 UTC | Jul 12, 19:20 UTC | 50m |
| 2026-07-12 | N232HF | - | Jul 12, 02:40 UTC | Jul 12, 03:25 UTC | 45m |
| 2026-07-11 | N232HF | - | Jul 11, 20:50 UTC | Jul 11, 22:01 UTC | 1h 10m |
| 2026-07-11 | N232HF | - | Jul 11, 19:05 UTC | Jul 11, 19:45 UTC | 40m |
| 2026-07-11 | N232HF | - | Jul 11, 17:00 UTC | Jul 11, 17:30 UTC | 30m |
| 2026-07-11 | N232HF | - | Jul 11, 15:05 UTC | Jul 11, 16:20 UTC | 1h 15m |
| 2026-07-10 | N232HF | - | Jul 10, 22:15 UTC | Jul 10, 23:00 UTC | 45m |
| 2026-07-09 | N232HF | - | Jul 9, 19:45 UTC | Jul 9, 20:30 UTC | 45m |
| 2026-07-08 | N232HF | VNY → SJC | Jul 8, 21:10 UTC | Jul 8, 22:00 UTC | 50m |
| 2026-07-04 | N232HF | VNY → VNY | Jul 4, 19:45 UTC | Jul 4, 20:25 UTC | 40m |
| 2026-06-21 | N232HF | - | Jun 21, 17:45 UTC | Jun 21, 19:14 UTC | 1h 30m |
| 2026-06-21 | N232HF | - | Jun 21, 00:14 UTC | Jun 21, 01:25 UTC | 1h 10m |
| 2026-06-20 | N232HF | - | Jun 20, 18:29 UTC | Jun 20, 20:45 UTC | 2h 15m |
| 2026-06-20 | N232HF | - | Jun 20, 16:05 UTC | Jun 20, 17:19 UTC | 1h 15m |
| 2026-06-18 | N232HF | - | Jun 18, 18:40 UTC | Jun 18, 19:55 UTC | 1h 15m |
| 2026-06-18 | N232HF | - | Jun 18, 11:45 UTC | Jun 18, 17:00 UTC | 5h 15m |
| 2026-06-17 | N232HF | - | Jun 17, 07:05 UTC | Jun 17, 15:10 UTC | 8h 5m |
| 2026-06-12 | N232HF | - | Jun 12, 04:30 UTC | Jun 12, 11:45 UTC | 7h 15m |
| 2026-06-10 | N232HF | VNY → TEB | Jun 10, 15:50 UTC | Jun 10, 20:40 UTC | 4h 50m |
| 2026-06-05 | N232HF | - | Jun 5, 06:20 UTC | Jun 5, 07:10 UTC | 50m |
| 2026-06-04 | N232HF | - | Jun 4, 21:30 UTC | Jun 4, 22:20 UTC | 50m |
| 2026-06-03 | N232HF | - | Jun 3, 17:25 UTC | Jun 3, 22:20 UTC | 4h 55m |
| 2026-05-29 | N232HF | - | May 29, 16:40 UTC | May 29, 20:50 UTC | 4h 10m |
| 2026-05-26 | N232HF | - | May 26, 15:45 UTC | May 26, 17:20 UTC | 1h 35m |
| 2026-05-26 | N232HF | - | May 26, 13:29 UTC | May 26, 14:55 UTC | 1h 25m |
| 2026-05-17 | N232HF | - | May 17, 23:30 UTC | May 18, 01:05 UTC | 1h 35m |
| 2026-05-15 | N232HF | VNY → OGD | May 15, 23:15 UTC | May 16, 00:30 UTC | 1h 15m |
| 2026-05-13 | N232HF | VNY → VNY | May 13, 02:55 UTC | May 13, 03:25 UTC | 30m |
| 2026-05-12 | N232HF | VNY → VNY | May 12, 17:40 UTC | May 12, 18:40 UTC | 1h 0m |
| 2026-05-12 | N232HF | VNY → VNY | May 12, 15:40 UTC | May 12, 16:05 UTC | 25m |
| 2026-05-11 | N232HF | - | May 11, 06:50 UTC | May 11, 06:55 UTC | 5m |
| 2026-05-10 | N232HF | - | May 10, 22:40 UTC | May 11, 05:50 UTC | 7h 10m |
| 2026-05-06 | N232HF | - | May 6, 12:30 UTC | May 6, 18:15 UTC | 5h 44m |
| 2026-05-04 | N232HF | - | May 4, 22:45 UTC | May 4, 23:35 UTC | 50m |
| 2026-05-04 | N232HF | - | May 4, 18:05 UTC | May 4, 19:50 UTC | 1h 46m |
| 2026-05-04 | N232HF | VNY → BFI | May 4, 14:50 UTC | May 4, 16:55 UTC | 2h 5m |
| 2026-05-03 | N232HF | - | May 3, 22:54 UTC | May 3, 23:45 UTC | 50m |
| 2026-05-03 | N232HF | - | May 3, 21:00 UTC | May 3, 21:39 UTC | 40m |
| 2026-05-03 | N232HF | - | May 3, 19:15 UTC | May 3, 20:05 UTC | 50m |
| 2026-05-02 | N232HF | - | May 2, 20:15 UTC | May 2, 20:50 UTC | 35m |
| 2026-04-30 | N232HF | APC → VNY | Apr 30, 04:10 UTC | Apr 30, 05:00 UTC | 50m |
| 2026-04-30 | N232HF | - | Apr 30, 01:45 UTC | Apr 30, 03:00 UTC | 1h 15m |
| 2026-04-29 | N232HF | - | Apr 29, 22:05 UTC | Apr 30, 00:15 UTC | 2h 9m |
| 2026-04-28 | N232HF | - | Apr 28, 22:55 UTC | Apr 28, 23:40 UTC | 45m |
| 2026-04-28 | N232HF | - | Apr 28, 20:45 UTC | Apr 28, 21:50 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 N232HF page for operator, model, and routing details .