sensors Mode-S transponder
A32F84
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N304PS · BOMBARDIER BD-100 Challenger 300 · operated by NUAGE NINE LLC
- Hex
- A32F84
- Octal
- 50627604
- Decimal
- 10,694,532
- Country
- US
- Tail
- N304PS
- Type
- CL30
- Flights observed
- 63
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 6d ago
Last known position
Country allocation
The ICAO 24-bit address A32F84 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 |
|---|---|---|---|
| JTL304 | - | 63 | 2026-07-08 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-08 | JTL304 | TEB → STL | Jul 8, 13:15 UTC | Jul 8, 15:15 UTC | 2h 0m |
| 2026-07-07 | JTL304 | MSP → TEB | Jul 7, 22:45 UTC | Jul 8, 00:50 UTC | 2h 5m |
| 2026-07-07 | JTL304 | - | Jul 7, 17:40 UTC | Jul 7, 18:35 UTC | 55m |
| 2026-07-07 | JTL304 | - | Jul 7, 13:40 UTC | Jul 7, 15:50 UTC | 2h 10m |
| 2026-07-06 | JTL304 | - | Jul 6, 20:35 UTC | Jul 6, 21:20 UTC | 45m |
| 2026-07-06 | JTL304 | - | Jul 6, 14:30 UTC | Jul 6, 16:20 UTC | 1h 50m |
| 2026-07-02 | JTL304 | CAK → STL | Jul 2, 20:15 UTC | Jul 2, 21:25 UTC | 1h 10m |
| 2026-07-02 | JTL304 | - | Jul 2, 16:55 UTC | Jul 2, 19:00 UTC | 2h 5m |
| 2026-07-01 | JTL304 | - | Jul 1, 18:50 UTC | Jul 1, 21:25 UTC | 2h 35m |
| 2026-07-01 | JTL304 | - | Jul 1, 14:05 UTC | Jul 1, 16:35 UTC | 2h 30m |
| 2026-07-01 | JTL304 | - | Jul 1, 12:15 UTC | Jul 1, 12:30 UTC | 15m |
| 2026-06-29 | JTL304 | - | Jun 29, 19:09 UTC | Jun 29, 19:35 UTC | 25m |
| 2026-06-29 | JTL304 | - | Jun 29, 14:14 UTC | Jun 29, 17:34 UTC | 3h 20m |
| 2026-06-25 | JTL304 | - | Jun 25, 21:20 UTC | Jun 25, 23:39 UTC | 2h 20m |
| 2026-06-25 | JTL304 | - | Jun 25, 19:24 UTC | Jun 25, 20:09 UTC | 45m |
| 2026-06-21 | JTL304 | - | Jun 21, 19:50 UTC | Jun 21, 20:34 UTC | 45m |
| 2026-06-20 | JTL304 | - | Jun 20, 19:44 UTC | Jun 20, 20:45 UTC | 1h 0m |
| 2026-06-19 | JTL304 | - | Jun 19, 19:14 UTC | Jun 19, 19:29 UTC | 15m |
| 2026-06-18 | JTL304 | - | Jun 18, 19:45 UTC | Jun 18, 21:30 UTC | 1h 45m |
| 2026-06-17 | JTL304 | - | Jun 17, 23:35 UTC | Jun 18, 00:15 UTC | 40m |
| 2026-06-17 | JTL304 | - | Jun 17, 16:35 UTC | Jun 17, 17:25 UTC | 50m |
| 2026-06-17 | JTL304 | - | Jun 17, 13:15 UTC | Jun 17, 13:50 UTC | 35m |
| 2026-06-16 | JTL304 | - | Jun 16, 21:45 UTC | Jun 16, 22:25 UTC | 40m |
| 2026-06-16 | JTL304 | - | Jun 16, 13:50 UTC | Jun 16, 14:30 UTC | 40m |
| 2026-06-15 | JTL304 | - | Jun 15, 18:20 UTC | Jun 15, 20:04 UTC | 1h 45m |
| 2026-06-14 | JTL304 | - | Jun 14, 21:50 UTC | Jun 14, 22:50 UTC | 1h 0m |
| 2026-06-14 | JTL304 | - | Jun 14, 16:05 UTC | Jun 14, 19:45 UTC | 3h 40m |
| 2026-06-14 | JTL304 | STL → MCO | Jun 14, 13:05 UTC | Jun 14, 15:00 UTC | 1h 55m |
| 2026-06-12 | JTL304 | AUS → STL | Jun 12, 23:05 UTC | Jun 13, 00:45 UTC | 1h 40m |
| 2026-06-08 | JTL304 | PHL → PDK | Jun 8, 19:15 UTC | Jun 8, 20:55 UTC | 1h 40m |
| 2026-06-06 | JTL304 | PHL → PDK | Jun 6, 10:55 UTC | Jun 6, 16:10 UTC | 5h 15m |
| 2026-06-03 | JTL304 | PHL → PDK | Jun 3, 15:30 UTC | Jun 3, 16:05 UTC | 35m |
| 2026-05-31 | JTL304 | PHL → PDK | May 31, 19:15 UTC | May 31, 19:45 UTC | 30m |
| 2026-05-29 | JTL304 | PHL → PDK | May 29, 18:10 UTC | May 29, 18:35 UTC | 25m |
| 2026-05-29 | JTL304 | PHL → PDK | May 29, 14:10 UTC | May 29, 16:35 UTC | 2h 25m |
| 2026-05-26 | JTL304 | PHL → PDK | May 26, 20:29 UTC | May 26, 21:14 UTC | 45m |
| 2026-05-26 | JTL304 | PHL → PDK | May 26, 16:55 UTC | May 26, 19:20 UTC | 2h 25m |
| 2026-05-23 | JTL304 | PHL → PDK | May 23, 17:50 UTC | May 23, 23:50 UTC | 6h 0m |
| 2026-05-21 | JTL304 | PHL → PDK | May 21, 20:30 UTC | May 21, 21:55 UTC | 1h 25m |
| 2026-05-21 | JTL304 | PHL → PDK | May 21, 14:25 UTC | May 21, 15:50 UTC | 1h 25m |
| 2026-05-20 | JTL304 | PHL → PDK | May 20, 19:05 UTC | May 20, 19:45 UTC | 40m |
| 2026-05-20 | JTL304 | PHL → PDK | May 20, 15:00 UTC | May 20, 17:40 UTC | 2h 40m |
| 2026-05-19 | JTL304 | PHL → PDK | May 19, 19:45 UTC | May 20, 17:40 UTC | 21h 56m |
| 2026-05-19 | JTL304 | PHL → PDK | May 19, 16:20 UTC | May 19, 18:25 UTC | 2h 5m |
| 2026-05-15 | JTL304 | PHL → PDK | May 15, 21:15 UTC | May 15, 23:20 UTC | 2h 5m |
| 2026-05-15 | JTL304 | PHL → PDK | May 15, 01:00 UTC | May 15, 02:20 UTC | 1h 20m |
| 2026-05-14 | JTL304 | PHL → PDK | May 14, 20:15 UTC | May 14, 21:35 UTC | 1h 20m |
| 2026-05-14 | JTL304 | PHL → PDK | May 14, 18:15 UTC | May 14, 18:25 UTC | 10m |
| 2026-05-14 | JTL304 | PHL → PDK | May 14, 00:45 UTC | May 14, 01:25 UTC | 40m |
| 2026-05-13 | JTL304 | PHL → PDK | May 13, 15:25 UTC | May 13, 16:10 UTC | 45m |
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 N304PS page for operator, model, and routing details .