sensors Mode-S transponder
A34C88
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N311WM · GULFSTREAM G600
- Hex
- A34C88
- Octal
- 50646210
- Decimal
- 10,701,960
- Country
- US
- Tail
- N311WM
- Type
- GA6C
- Flights observed
- 59
- Distinct callsigns
- 2
- Country
- US
- Last broadcast
- 5d ago
Last known position
Country allocation
The ICAO 24-bit address A34C88 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-25 | N311WM | TEB → PTK | Jul 25, 14:25 UTC | Jul 25, 15:35 UTC | 1h 10m |
| 2026-07-25 | N311WM | - | Jul 25, 11:45 UTC | Jul 25, 12:55 UTC | 1h 10m |
| 2026-07-23 | N311WM | - | Jul 23, 13:15 UTC | Jul 23, 15:20 UTC | 2h 5m |
| 2026-07-22 | N311WM | - | Jul 22, 20:00 UTC | Jul 22, 20:30 UTC | 30m |
| 2026-07-21 | N311WM | - | Jul 21, 14:10 UTC | Jul 21, 17:25 UTC | 3h 15m |
| 2026-07-17 | N311WM | - | Jul 17, 14:20 UTC | Jul 17, 16:40 UTC | 2h 20m |
| 2026-07-16 | N311WM | - | Jul 16, 21:45 UTC | Jul 16, 22:30 UTC | 45m |
| 2026-07-16 | N311WM | - | Jul 16, 20:19 UTC | Jul 16, 21:05 UTC | 45m |
| 2026-07-16 | N311WM | - | Jul 16, 03:25 UTC | Jul 16, 04:00 UTC | 35m |
| 2026-07-16 | N311WM | - | Jul 16, 01:50 UTC | Jul 16, 02:45 UTC | 55m |
| 2026-07-15 | N311WM | - | Jul 15, 23:05 UTC | Jul 15, 23:15 UTC | 10m |
| 2026-07-15 | N311WM | - | Jul 15, 21:50 UTC | Jul 15, 22:55 UTC | 1h 5m |
| 2026-07-08 | N311WM | - | Jul 8, 21:15 UTC | Jul 8, 21:55 UTC | 40m |
| 2026-07-08 | N311WM | ZRH → MDW | Jul 8, 12:00 UTC | Jul 8, 20:25 UTC | 8h 25m |
| 2026-07-06 | N311WM | - | Jul 6, 06:45 UTC | Jul 6, 07:15 UTC | 30m |
| 2026-07-01 | N311WM | NCE → GVA | Jul 1, 09:25 UTC | Jul 1, 10:10 UTC | 45m |
| 2026-06-30 | N311WM | LCY → NCE | Jun 30, 12:35 UTC | Jun 30, 14:10 UTC | 1h 35m |
| 2026-06-30 | N311WM | - | Jun 30, 08:15 UTC | Jun 30, 08:25 UTC | 10m |
| 2026-06-30 | N311WM | LCY → LCY | Jun 30, 07:50 UTC | Jun 30, 08:00 UTC | 10m |
| 2026-06-30 | N311WM | - | Jun 30, 05:15 UTC | Jun 30, 06:40 UTC | 1h 25m |
| 2026-06-24 | N311WM | - | Jun 24, 12:20 UTC | Jun 24, 19:44 UTC | 7h 25m |
| 2026-06-24 | N311WM | RST → PTK | Jun 24, 02:24 UTC | Jun 24, 03:24 UTC | 1h 0m |
| 2026-06-23 | N311WM | - | Jun 23, 16:20 UTC | Jun 23, 16:29 UTC | 10m |
| 2026-06-23 | N311WM | - | Jun 23, 15:59 UTC | Jun 23, 16:14 UTC | 15m |
| 2026-06-23 | N311WM | - | Jun 23, 14:15 UTC | Jun 23, 15:19 UTC | 1h 5m |
| 2026-06-18 | N311WM | - | Jun 18, 00:25 UTC | Jun 18, 01:20 UTC | 55m |
| 2026-06-17 | N311WM | - | Jun 17, 22:35 UTC | Jun 17, 23:45 UTC | 1h 10m |
| 2026-06-17 | N311WM | - | Jun 17, 12:20 UTC | Jun 17, 13:35 UTC | 1h 15m |
| 2026-06-15 | N311WM | - | Jun 15, 19:50 UTC | Jun 15, 20:59 UTC | 1h 10m |
| 2026-05-29 | N311WM | RST → PTK | May 29, 21:00 UTC | May 29, 22:00 UTC | 1h 0m |
| 2026-05-27 | N311WM | - | May 27, 20:35 UTC | May 27, 21:45 UTC | 1h 10m |
| 2026-05-27 | N311WM | - | May 27, 17:35 UTC | May 27, 17:50 UTC | 15m |
| 2026-05-14 | N311WM | RST → PTK | May 14, 21:45 UTC | May 14, 22:45 UTC | 1h 0m |
| 2026-05-13 | N311WM | - | May 13, 21:25 UTC | May 13, 23:00 UTC | 1h 35m |
| 2026-05-13 | N311WM | RST → PTK | May 13, 19:35 UTC | May 13, 20:40 UTC | 1h 5m |
| 2026-05-12 | N311WM | - | May 12, 23:05 UTC | May 13, 00:20 UTC | 1h 15m |
| 2026-05-11 | N311WM | - | May 11, 13:40 UTC | May 11, 14:35 UTC | 55m |
| 2026-05-11 | N311WM | - | May 11, 11:40 UTC | May 11, 12:50 UTC | 1h 10m |
| 2026-05-08 | N311WM | RST → PTK | May 8, 17:30 UTC | May 8, 18:35 UTC | 1h 5m |
| 2026-05-08 | N311WM | - | May 8, 13:55 UTC | May 8, 15:05 UTC | 1h 10m |
| 2026-05-06 | N311WM | - | May 6, 22:40 UTC | May 6, 23:40 UTC | 1h 0m |
| 2026-05-06 | N311WM | - | May 6, 19:50 UTC | May 6, 22:20 UTC | 2h 30m |
| 2026-05-06 | N311WM | - | May 6, 11:45 UTC | May 6, 19:20 UTC | 7h 34m |
| 2026-05-04 | N311WM | - | May 4, 12:20 UTC | May 4, 19:45 UTC | 7h 26m |
| 2026-05-03 | N311WM | - | May 3, 20:45 UTC | May 3, 22:00 UTC | 1h 15m |
| 2026-05-02 | GLF96 | TEB → PTK | May 2, 14:10 UTC | May 2, 15:25 UTC | 1h 15m |
| 2026-05-02 | GLF96 | - | May 2, 11:05 UTC | May 2, 12:10 UTC | 1h 5m |
| 2026-04-27 | N311WM | - | Apr 27, 04:50 UTC | Apr 27, 06:05 UTC | 1h 15m |
| 2026-04-27 | N311WM | - | Apr 27, 02:10 UTC | Apr 27, 04:05 UTC | 1h 55m |
| 2026-04-26 | N311WM | - | Apr 26, 20:55 UTC | Apr 26, 22:05 UTC | 1h 10m |
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 N311WM page for operator, model, and routing details .