sensors Mode-S transponder
AB6800
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N834JB · AIRBUS A-320 · operated by JETBLUE AIRWAYS CORP
- Hex
- AB6800
- Octal
- 52664000
- Decimal
- 11,233,280
- Country
- US
- Tail
- N834JB
- Type
- A320
- Flights observed
- 278
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 2h ago
Last known position
Country allocation
The ICAO 24-bit address AB6800 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 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| JBU1743 | JetBlue Airways | 5 | 2026-06-12 |
| JBU1245 | - | 4 | 2026-07-07 |
| JBU1133 | JetBlue Airways | 4 | 2026-06-19 |
| JBU8350 | - | 3 | 2026-07-11 |
| JBU754 | - | 3 | 2026-07-07 |
| JBU740 | - | 3 | 2026-07-09 |
| JBU703 | - | 3 | 2026-07-06 |
| JBU503 | JetBlue Airways | 3 | 2026-06-09 |
| JBU304 | JetBlue Airways | 3 | 2026-06-20 |
| JBU276 | - | 3 | 2026-06-29 |
| JBU2661 | JetBlue Airways | 3 | 2026-05-12 |
| JBU2538 | JetBlue Airways | 3 | 2026-05-28 |
| JBU1754 | JetBlue Airways | 3 | 2026-06-09 |
| JBU1553 | - | 3 | 2026-07-10 |
| JBU997 | JetBlue Airways | 2 | 2026-04-22 |
| JBU94 | - | 2 | 2026-07-05 |
| JBU883 | JetBlue Airways | 2 | 2026-05-26 |
| JBU880 | JetBlue Airways | 2 | 2026-04-23 |
| JBU87 | - | 2 | 2026-07-07 |
| JBU83 | - | 2 | 2026-06-27 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | JBU746 | - | Jul 14, 23:55 UTC | Jul 15, 02:10 UTC | 2h 15m |
| 2026-07-14 | JBU40 | - | Jul 14, 21:10 UTC | Jul 14, 21:50 UTC | 40m |
| 2026-07-14 | JBU753 | - | Jul 14, 10:50 UTC | Jul 14, 16:15 UTC | 5h 25m |
| 2026-07-13 | JBU70 | FLL → BOS | Jul 13, 18:55 UTC | Jul 14, 16:15 UTC | 21h 21m |
| 2026-07-13 | JBU54 | SJU → FLL | Jul 13, 15:06 UTC | Jul 14, 11:20 UTC | 20h 15m |
| 2026-07-13 | JBU761 | BOS → SJU | Jul 13, 10:25 UTC | Jul 13, 13:50 UTC | 3h 25m |
| 2026-07-13 | JBU761 | BOS → SJU | Jul 13, 10:23 UTC | Jul 14, 02:00 UTC | 15h 38m |
| 2026-07-12 | JBU974 | - | Jul 12, 22:00 UTC | Jul 13, 02:05 UTC | 4h 5m |
| 2026-07-12 | JBU773 | - | Jul 12, 20:05 UTC | Jul 12, 20:20 UTC | 15m |
| 2026-07-12 | JBU773 | - | Jul 12, 15:55 UTC | Jul 12, 19:20 UTC | 3h 25m |
| 2026-07-11 | JBU8350 | - | Jul 11, 21:55 UTC | Jul 11, 22:35 UTC | 40m |
| 2026-07-11 | JBU8350 | - | Jul 11, 20:15 UTC | Jul 11, 20:25 UTC | 10m |
| 2026-07-11 | JBU8350 | SJU → FLL | Jul 11, 20:12 UTC | Jul 12, 19:20 UTC | 23h 9m |
| 2026-07-10 | JBU928 | SJU → ORF | Jul 10, 17:50 UTC | Jul 11, 01:25 UTC | 7h 36m |
| 2026-07-10 | JBU1553 | FLL → SJU | Jul 10, 14:33 UTC | Jul 11, 01:25 UTC | 10h 53m |
| 2026-07-10 | JBU1197 | PVD → FLL | Jul 10, 09:53 UTC | Jul 11, 01:25 UTC | 15h 33m |
| 2026-07-10 | JBU1128 | JFK → PVD | Jul 10, 02:45 UTC | Jul 11, 01:25 UTC | 22h 41m |
| 2026-07-09 | JBU740 | ANU → JFK | Jul 9, 19:45 UTC | Jul 10, 18:00 UTC | 22h 15m |
| 2026-07-09 | JBU743 | JFK → JFK | Jul 9, 14:40 UTC | Jul 9, 23:45 UTC | 9h 5m |
| 2026-07-09 | JBU2884 | MCO → JFK | Jul 9, 10:20 UTC | Jul 9, 12:15 UTC | 1h 55m |
| 2026-07-08 | JBU375 | PVD → MCO | Jul 8, 11:36 UTC | Jul 9, 10:00 UTC | 22h 25m |
| 2026-07-08 | JBU376 | FLL → PHL | Jul 8, 03:50 UTC | Jul 9, 02:00 UTC | 22h 11m |
| 2026-07-07 | JBU87 | - | Jul 7, 20:15 UTC | Jul 7, 22:50 UTC | 2h 35m |
| 2026-07-07 | JBU87 | FLL → ALB | Jul 7, 20:11 UTC | Jul 8, 18:40 UTC | 22h 30m |
| 2026-07-07 | JBU1245 | - | Jul 7, 16:40 UTC | Jul 7, 18:30 UTC | 1h 50m |
| 2026-07-07 | JBU1246 | - | Jul 7, 13:50 UTC | Jul 7, 15:30 UTC | 1h 40m |
| 2026-07-07 | JBU754 | - | Jul 7, 11:30 UTC | Jul 7, 12:00 UTC | 30m |
| 2026-07-07 | JBU754 | - | Jul 7, 09:45 UTC | Jul 7, 10:00 UTC | 15m |
| 2026-07-07 | JBU1138 | - | Jul 7, 01:15 UTC | Jul 7, 01:30 UTC | 15m |
| 2026-07-06 | JBU1137 | BOS → DTW | Jul 6, 22:50 UTC | Jul 6, 23:00 UTC | 10m |
| 2026-07-06 | JBU703 | - | Jul 6, 20:45 UTC | Jul 6, 21:05 UTC | 20m |
| 2026-07-06 | JBU703 | - | Jul 6, 18:15 UTC | Jul 6, 18:25 UTC | 10m |
| 2026-07-06 | JBU703 | - | Jul 6, 17:40 UTC | Jul 6, 18:10 UTC | 30m |
| 2026-07-05 | JBU1694 | MCO → HPN | Jul 5, 22:18 UTC | Jul 6, 21:05 UTC | 22h 48m |
| 2026-07-05 | JBU94 | - | Jul 5, 13:30 UTC | Jul 5, 15:55 UTC | 2h 25m |
| 2026-07-05 | JBU94 | MCO → HPN | Jul 5, 13:26 UTC | Jul 6, 12:00 UTC | 22h 34m |
| 2026-07-05 | JBU1434 | - | Jul 5, 11:15 UTC | Jul 5, 12:10 UTC | 55m |
| 2026-07-05 | JBU1434 | - | Jul 5, 09:30 UTC | Jul 5, 09:45 UTC | 15m |
| 2026-07-04 | JBU861 | BOS → SJU | Jul 4, 13:41 UTC | Jul 5, 12:00 UTC | 22h 20m |
| 2026-07-03 | JBU1941 | BOS → SRQ | Jul 3, 20:32 UTC | Jul 4, 18:40 UTC | 22h 8m |
| 2026-07-03 | JBU1941 | BOS → SRQ | Jul 3, 20:35 UTC | Jul 3, 23:35 UTC | 3h 0m |
| 2026-07-02 | JBU1194 | MBJ → BOS | Jul 2, 21:14 UTC | Jul 3, 02:10 UTC | 4h 56m |
| 2026-07-02 | JBU1194 | BOS → BOS | Jul 2, 16:00 UTC | Jul 3, 01:00 UTC | 9h 0m |
| 2026-07-01 | JBU23 | - | Jul 1, 23:05 UTC | Jul 2, 00:55 UTC | 1h 50m |
| 2026-07-01 | JBU23 | DCA → PBI | Jul 1, 23:02 UTC | Jul 2, 19:00 UTC | 19h 59m |
| 2026-07-01 | JBU24 | - | Jul 1, 18:45 UTC | Jul 1, 20:40 UTC | 1h 55m |
| 2026-07-01 | JBU2143 | - | Jul 1, 14:50 UTC | Jul 1, 17:00 UTC | 2h 10m |
| 2026-07-01 | JBU306 | - | Jul 1, 10:50 UTC | Jul 1, 13:20 UTC | 2h 30m |
| 2026-06-30 | JBU725 | RDU → FLL | Jun 30, 22:50 UTC | Jul 1, 00:25 UTC | 1h 35m |
| 2026-06-30 | JBU726 | - | Jun 30, 20:05 UTC | Jun 30, 21:45 UTC | 1h 40m |
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 N834JB page for operator, model, and routing details .