sensors Mode-S transponder
AA5F64
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N768BL · BOMBARDIER BD-100 Challenger 350 · operated by CD 321 LLC
- Hex
- AA5F64
- Octal
- 52457544
- Decimal
- 11,165,540
- Country
- US
- Tail
- N768BL
- Type
- CL35
- Flights observed
- 165
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 17h ago
Last known position
Country allocation
The ICAO 24-bit address AA5F64 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 |
|---|---|---|---|
| JRE768 | - | 165 | 2026-07-13 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | JRE768 | - | Jul 13, 21:20 UTC | Jul 13, 21:55 UTC | 35m |
| 2026-07-13 | JRE768 | - | Jul 13, 16:15 UTC | Jul 13, 19:40 UTC | 3h 25m |
| 2026-07-12 | JRE768 | - | Jul 12, 22:55 UTC | Jul 13, 00:01 UTC | 1h 5m |
| 2026-07-12 | JRE768 | - | Jul 12, 17:20 UTC | Jul 12, 21:30 UTC | 4h 10m |
| 2026-07-11 | JRE768 | - | Jul 11, 19:20 UTC | Jul 11, 22:10 UTC | 2h 50m |
| 2026-07-11 | JRE768 | - | Jul 11, 14:15 UTC | Jul 11, 16:35 UTC | 2h 20m |
| 2026-07-11 | JRE768 | BNA → RST | Jul 11, 12:05 UTC | Jul 11, 13:30 UTC | 1h 25m |
| 2026-07-10 | JRE768 | - | Jul 10, 19:40 UTC | Jul 10, 21:30 UTC | 1h 50m |
| 2026-07-10 | JRE768 | - | Jul 10, 17:30 UTC | Jul 10, 18:25 UTC | 55m |
| 2026-07-10 | JRE768 | - | Jul 10, 13:55 UTC | Jul 10, 16:40 UTC | 2h 45m |
| 2026-07-10 | JRE768 | - | Jul 10, 10:30 UTC | Jul 10, 12:45 UTC | 2h 15m |
| 2026-07-09 | JRE768 | - | Jul 9, 16:15 UTC | Jul 9, 21:30 UTC | 5h 15m |
| 2026-07-09 | JRE768 | LAS → SBP | Jul 9, 00:25 UTC | Jul 9, 01:20 UTC | 55m |
| 2026-07-08 | JRE768 | - | Jul 8, 21:00 UTC | Jul 8, 23:25 UTC | 2h 25m |
| 2026-07-08 | JRE768 | PIE → DAL | Jul 8, 14:00 UTC | Jul 8, 16:05 UTC | 2h 5m |
| 2026-07-07 | JRE768 | - | Jul 7, 22:55 UTC | Jul 7, 23:40 UTC | 45m |
| 2026-07-07 | JRE768 | FTY → FXE | Jul 7, 20:25 UTC | Jul 7, 22:00 UTC | 1h 35m |
| 2026-07-07 | JRE768 | COE → FTY | Jul 7, 14:10 UTC | Jul 7, 19:20 UTC | 5h 10m |
| 2026-07-06 | JRE768 | - | Jul 6, 13:20 UTC | Jul 6, 18:15 UTC | 4h 55m |
| 2026-07-05 | JRE768 | - | Jul 5, 21:50 UTC | Jul 5, 22:05 UTC | 15m |
| 2026-07-05 | JRE768 | - | Jul 5, 17:25 UTC | Jul 5, 21:10 UTC | 3h 45m |
| 2026-07-04 | JRE768 | - | Jul 4, 18:30 UTC | Jul 4, 19:05 UTC | 35m |
| 2026-07-04 | JRE768 | - | Jul 4, 12:45 UTC | Jul 4, 17:10 UTC | 4h 25m |
| 2026-07-03 | JRE768 | - | Jul 3, 18:40 UTC | Jul 3, 21:15 UTC | 2h 35m |
| 2026-07-02 | JRE768 | - | Jul 2, 16:15 UTC | Jul 2, 21:30 UTC | 5h 15m |
| 2026-07-02 | JRE768 | - | Jul 2, 13:25 UTC | Jul 2, 15:10 UTC | 1h 45m |
| 2026-07-01 | JRE768 | - | Jul 1, 22:00 UTC | Jul 2, 01:30 UTC | 3h 30m |
| 2026-07-01 | JRE768 | - | Jul 1, 14:35 UTC | Jul 1, 16:30 UTC | 1h 55m |
| 2026-06-30 | JRE768 | - | Jun 30, 20:55 UTC | Jun 30, 21:45 UTC | 50m |
| 2026-06-30 | JRE768 | - | Jun 30, 18:00 UTC | Jun 30, 19:45 UTC | 1h 45m |
| 2026-06-29 | JRE768 | - | Jun 29, 21:50 UTC | Jun 29, 22:44 UTC | 55m |
| 2026-06-29 | JRE768 | - | Jun 29, 19:24 UTC | Jun 29, 20:59 UTC | 1h 35m |
| 2026-06-28 | JRE768 | MSP → LAS | Jun 28, 15:24 UTC | Jun 28, 18:34 UTC | 3h 10m |
| 2026-06-27 | JRE768 | - | Jun 27, 22:25 UTC | Jun 28, 00:04 UTC | 1h 40m |
| 2026-06-27 | JRE768 | - | Jun 27, 16:04 UTC | Jun 27, 21:15 UTC | 5h 10m |
| 2026-06-26 | JRE768 | - | Jun 26, 23:25 UTC | Jun 27, 03:49 UTC | 4h 25m |
| 2026-06-26 | JRE768 | - | Jun 26, 20:40 UTC | Jun 26, 22:14 UTC | 1h 35m |
| 2026-06-26 | JRE768 | - | Jun 26, 16:39 UTC | Jun 26, 19:39 UTC | 3h 0m |
| 2026-06-25 | JRE768 | - | Jun 25, 21:29 UTC | Jun 25, 23:05 UTC | 1h 35m |
| 2026-06-25 | JRE768 | - | Jun 25, 16:29 UTC | Jun 25, 19:59 UTC | 3h 30m |
| 2026-06-25 | JRE768 | - | Jun 25, 12:44 UTC | Jun 25, 13:45 UTC | 1h 0m |
| 2026-06-24 | JRE768 | - | Jun 24, 21:14 UTC | Jun 25, 00:14 UTC | 3h 0m |
| 2026-06-24 | JRE768 | - | Jun 24, 15:24 UTC | Jun 24, 19:55 UTC | 4h 30m |
| 2026-06-24 | JRE768 | - | Jun 24, 02:34 UTC | Jun 24, 03:15 UTC | 40m |
| 2026-06-23 | JRE768 | - | Jun 23, 23:59 UTC | Jun 24, 01:39 UTC | 1h 40m |
| 2026-06-23 | JRE768 | VNY → ABQ | Jun 23, 19:29 UTC | Jun 23, 23:19 UTC | 3h 50m |
| 2026-06-22 | JRE768 | BED → VNY | Jun 22, 18:09 UTC | Jun 23, 00:15 UTC | 6h 5m |
| 2026-06-22 | JRE768 | LNS → BED | Jun 22, 15:05 UTC | Jun 22, 15:54 UTC | 50m |
| 2026-06-21 | JRE768 | - | Jun 21, 19:34 UTC | Jun 21, 22:44 UTC | 3h 10m |
| 2026-06-20 | JRE768 | - | Jun 20, 17:04 UTC | Jun 21, 16:59 UTC | 23h 55m |
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 N768BL page for operator, model, and routing details .