sensors Mode-S transponder
AD329F
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N95DF · CESSNA 750 Citation 10
- Hex
- AD329F
- Octal
- 53231237
- Decimal
- 11,350,687
- Country
- US
- Tail
- N95DF
- Type
- C750
- Flights observed
- 79
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address AD329F 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 |
|---|---|---|---|
| NJM95 | - | 79 | 2026-07-18 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-18 | NJM95 | - | Jul 18, 16:30 UTC | Jul 18, 18:40 UTC | 2h 10m |
| 2026-07-17 | NJM95 | - | Jul 17, 19:49 UTC | Jul 18, 18:40 UTC | 22h 51m |
| 2026-07-17 | NJM95 | - | Jul 17, 17:50 UTC | Jul 18, 17:45 UTC | 23h 56m |
| 2026-07-17 | NJM95 | - | Jul 17, 17:25 UTC | Jul 17, 20:44 UTC | 3h 20m |
| 2026-07-17 | NJM95 | - | Jul 17, 15:44 UTC | Jul 17, 16:19 UTC | 35m |
| 2026-07-16 | NJM95 | - | Jul 16, 21:30 UTC | Jul 16, 21:55 UTC | 25m |
| 2026-07-16 | NJM95 | - | Jul 16, 19:14 UTC | Jul 16, 19:55 UTC | 40m |
| 2026-07-16 | NJM95 | MCO → ORL | Jul 16, 01:50 UTC | Jul 16, 02:00 UTC | 10m |
| 2026-07-16 | NJM95 | FTY → MCO | Jul 16, 00:00 UTC | Jul 16, 01:05 UTC | 1h 5m |
| 2026-07-15 | NJM95 | ORL → FTY | Jul 15, 20:30 UTC | Jul 15, 21:35 UTC | 1h 5m |
| 2026-07-09 | NJM95 | - | Jul 9, 15:00 UTC | Jul 9, 15:35 UTC | 35m |
| 2026-07-09 | NJM95 | - | Jul 9, 11:40 UTC | Jul 9, 13:15 UTC | 1h 35m |
| 2026-07-06 | NJM95 | - | Jul 6, 20:10 UTC | Jul 6, 21:20 UTC | 1h 10m |
| 2026-07-06 | NJM95 | - | Jul 6, 18:15 UTC | Jul 6, 19:15 UTC | 1h 0m |
| 2026-07-06 | NJM95 | - | Jul 6, 16:30 UTC | Jul 6, 17:05 UTC | 35m |
| 2026-07-05 | NJM95 | - | Jul 5, 21:50 UTC | Jul 5, 23:55 UTC | 2h 5m |
| 2026-07-05 | NJM95 | - | Jul 5, 17:00 UTC | Jul 5, 17:40 UTC | 40m |
| 2026-07-05 | NJM95 | - | Jul 5, 14:50 UTC | Jul 5, 15:30 UTC | 40m |
| 2026-07-04 | NJM95 | - | Jul 4, 17:35 UTC | Jul 4, 18:15 UTC | 40m |
| 2026-07-01 | NJM95 | ORL → ORL | Jul 1, 18:15 UTC | Jul 1, 18:40 UTC | 25m |
| 2026-06-27 | NJM95 | ORL → ORL | Jun 27, 16:44 UTC | Jun 27, 16:55 UTC | 10m |
| 2026-06-20 | NJM95 | - | Jun 20, 15:49 UTC | Jun 20, 17:19 UTC | 1h 30m |
| 2026-06-16 | NJM95 | - | Jun 16, 15:15 UTC | Jun 16, 17:15 UTC | 2h 0m |
| 2026-06-15 | NJM95 | - | Jun 15, 22:15 UTC | Jun 15, 22:40 UTC | 25m |
| 2026-06-15 | NJM95 | - | Jun 15, 18:35 UTC | Jun 15, 20:50 UTC | 2h 15m |
| 2026-06-15 | NJM95 | - | Jun 15, 15:10 UTC | Jun 15, 16:40 UTC | 1h 30m |
| 2026-06-15 | NJM95 | - | Jun 15, 13:10 UTC | Jun 15, 14:24 UTC | 1h 15m |
| 2026-06-15 | NJM95 | - | Jun 15, 10:55 UTC | Jun 15, 11:54 UTC | 1h 0m |
| 2026-06-14 | NJM95 | - | Jun 14, 14:50 UTC | Jun 14, 16:05 UTC | 1h 15m |
| 2026-06-13 | NJM95 | - | Jun 13, 16:40 UTC | Jun 13, 17:25 UTC | 45m |
| 2026-06-13 | NJM95 | ORL → FOK | Jun 13, 13:35 UTC | Jun 13, 15:45 UTC | 2h 10m |
| 2026-06-11 | NJM95 | - | Jun 11, 16:45 UTC | Jun 11, 17:55 UTC | 1h 10m |
| 2026-05-09 | NJM95 | ORL → CHA | May 9, 14:55 UTC | May 9, 16:10 UTC | 1h 15m |
| 2026-05-03 | NJM95 | - | May 3, 22:39 UTC | May 3, 23:45 UTC | 1h 5m |
| 2026-05-03 | NJM95 | - | May 3, 19:30 UTC | May 3, 20:45 UTC | 1h 15m |
| 2026-05-03 | NJM95 | - | May 3, 03:00 UTC | May 3, 03:25 UTC | 25m |
| 2026-05-02 | NJM95 | - | May 2, 20:25 UTC | May 2, 20:50 UTC | 25m |
| 2026-05-01 | NJM95 | - | May 1, 13:25 UTC | May 1, 14:00 UTC | 35m |
| 2026-04-27 | NJM95 | - | Apr 27, 16:55 UTC | Apr 27, 17:15 UTC | 20m |
| 2026-04-27 | NJM95 | - | Apr 27, 13:30 UTC | Apr 27, 16:10 UTC | 2h 40m |
| 2026-04-26 | NJM95 | AUS → APF | Apr 26, 23:00 UTC | Apr 27, 00:55 UTC | 1h 55m |
| 2026-04-26 | NJM95 | - | Apr 26, 19:15 UTC | Apr 26, 21:35 UTC | 2h 20m |
| 2026-04-25 | NJM95 | - | Apr 25, 18:05 UTC | Apr 25, 20:15 UTC | 2h 10m |
| 2026-04-25 | NJM95 | - | Apr 25, 14:15 UTC | Apr 25, 16:55 UTC | 2h 40m |
| 2026-04-25 | NJM95 | - | Apr 25, 12:45 UTC | Apr 25, 13:30 UTC | 45m |
| 2026-04-24 | NJM95 | - | Apr 24, 17:20 UTC | Apr 24, 17:50 UTC | 30m |
| 2026-04-24 | NJM95 | - | Apr 24, 14:15 UTC | Apr 24, 16:20 UTC | 2h 5m |
| 2026-04-23 | NJM95 | - | Apr 23, 21:15 UTC | Apr 23, 21:25 UTC | 10m |
| 2026-04-23 | NJM95 | - | Apr 23, 18:30 UTC | Apr 23, 20:25 UTC | 1h 55m |
| 2026-04-23 | NJM95 | - | Apr 23, 14:45 UTC | Apr 23, 17:00 UTC | 2h 15m |
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 N95DF page for operator, model, and routing details .