sensors Mode-S transponder
AD4804
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N955JB · AIRBUS A-321 · operated by JETBLUE AIRWAYS CORP
- Hex
- AD4804
- Octal
- 53244004
- Decimal
- 11,356,164
- Country
- US
- Tail
- N955JB
- Type
- A321
- Flights observed
- 251
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address AD4804 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 |
|---|---|---|---|
| JBU904 | - | 9 | 2026-07-05 |
| JBU70 | JetBlue Airways | 7 | 2026-05-03 |
| JBU1192 | JetBlue Airways | 7 | 2026-06-06 |
| JBU491 | JetBlue Airways | 6 | 2026-04-16 |
| JBU69 | JetBlue Airways | 5 | 2026-05-03 |
| JBU651 | JetBlue Airways | 5 | 2026-05-26 |
| JBU57 | - | 5 | 2026-07-07 |
| JBU552 | JetBlue Airways | 5 | 2026-05-26 |
| JBU303 | - | 5 | 2026-06-19 |
| JBU269 | JetBlue Airways | 5 | 2026-04-20 |
| JBU162 | - | 5 | 2026-06-30 |
| JBU882 | JetBlue Airways | 4 | 2026-05-29 |
| JBU2904 | - | 4 | 2026-07-02 |
| JBU151 | - | 4 | 2026-06-18 |
| JBU1058 | JetBlue Airways | 4 | 2026-05-30 |
| JBU939 | JetBlue Airways | 3 | 2026-06-01 |
| JBU903 | - | 3 | 2026-06-20 |
| JBU881 | JetBlue Airways | 3 | 2026-05-13 |
| JBU58 | JetBlue Airways | 3 | 2026-06-23 |
| JBU2851 | JetBlue Airways | 3 | 2026-06-06 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | JBU395 | BOS → PDX | Jul 13, 15:19 UTC | Jul 14, 03:00 UTC | 11h 42m |
| 2026-07-12 | JBU330 | SDQ → BOS | Jul 12, 22:27 UTC | Jul 13, 20:40 UTC | 22h 14m |
| 2026-07-12 | JBU1829 | BOS → SDQ | Jul 12, 16:44 UTC | Jul 13, 15:00 UTC | 22h 17m |
| 2026-07-12 | JBU1830 | SDQ → BOS | Jul 12, 09:07 UTC | Jul 13, 02:05 UTC | 16h 59m |
| 2026-07-11 | JBU9 | JFK → SDQ | Jul 11, 21:52 UTC | Jul 12, 18:05 UTC | 20h 14m |
| 2026-07-11 | JBU9 | - | Jul 11, 21:55 UTC | Jul 11, 22:35 UTC | 40m |
| 2026-07-11 | JBU602 | - | Jul 11, 16:20 UTC | Jul 11, 18:40 UTC | 2h 20m |
| 2026-07-11 | JBU1601 | JFK → FLL | Jul 11, 12:00 UTC | Jul 11, 14:25 UTC | 2h 25m |
| 2026-07-10 | JBU2709 | JFK → SDQ | Jul 10, 11:31 UTC | Jul 11, 11:00 UTC | 23h 30m |
| 2026-07-09 | JBU1528 | POP → JFK | Jul 9, 19:56 UTC | Jul 10, 12:15 UTC | 16h 19m |
| 2026-07-09 | JBU355 | JFK → ONT | Jul 9, 00:43 UTC | Jul 9, 23:00 UTC | 22h 18m |
| 2026-07-08 | JBU2709 | JFK → SDQ | Jul 8, 12:26 UTC | Jul 9, 11:00 UTC | 22h 35m |
| 2026-07-08 | JBU2709 | - | Jul 8, 12:30 UTC | Jul 8, 15:35 UTC | 3h 5m |
| 2026-07-07 | JBU57 | JFK → AUA | Jul 7, 15:48 UTC | Jul 8, 13:45 UTC | 21h 58m |
| 2026-07-07 | JBU1323 | - | Jul 7, 04:25 UTC | Jul 7, 05:05 UTC | 40m |
| 2026-07-07 | JBU1323 | BOS → STI | Jul 7, 04:25 UTC | Jul 8, 02:05 UTC | 21h 40m |
| 2026-07-06 | JBU398 | SEA → BOS | Jul 6, 21:40 UTC | Jul 7, 02:35 UTC | 4h 55m |
| 2026-07-06 | JBU397 | BOS → SEA | Jul 6, 11:30 UTC | Jul 6, 17:05 UTC | 5h 35m |
| 2026-07-05 | JBU2924 | JFK → BOS | Jul 5, 18:45 UTC | Jul 6, 03:15 UTC | 8h 30m |
| 2026-07-05 | JBU904 | - | Jul 5, 14:40 UTC | Jul 5, 15:25 UTC | 45m |
| 2026-07-05 | JBU904 | - | Jul 5, 12:00 UTC | Jul 5, 12:15 UTC | 15m |
| 2026-07-04 | JBU255 | JFK → PLS | Jul 4, 14:33 UTC | Jul 5, 12:15 UTC | 21h 42m |
| 2026-07-04 | JBU160 | KIN → JFK | Jul 4, 07:37 UTC | Jul 5, 06:25 UTC | 22h 49m |
| 2026-07-04 | JBU1059 | JFK → KIN | Jul 4, 02:51 UTC | Jul 5, 01:00 UTC | 22h 9m |
| 2026-07-04 | JBU1059 | - | Jul 4, 02:55 UTC | Jul 4, 05:20 UTC | 2h 25m |
| 2026-07-03 | JBU662 | - | Jul 3, 18:20 UTC | Jul 3, 22:50 UTC | 4h 30m |
| 2026-07-03 | JBU361 | - | Jul 3, 16:20 UTC | Jul 3, 16:30 UTC | 10m |
| 2026-07-03 | JBU361 | - | Jul 3, 12:20 UTC | Jul 3, 15:40 UTC | 3h 20m |
| 2026-07-03 | JBU2536 | JFK → JFK | Jul 3, 01:35 UTC | Jul 3, 10:20 UTC | 8h 45m |
| 2026-07-02 | JBU503 | JFK → SJU | Jul 2, 14:34 UTC | Jul 3, 12:55 UTC | 22h 21m |
| 2026-07-02 | JBU2904 | SJU → JFK | Jul 2, 09:03 UTC | Jul 3, 02:15 UTC | 17h 12m |
| 2026-07-01 | JBU2903 | JFK → SJU | Jul 1, 23:29 UTC | Jul 2, 23:00 UTC | 23h 31m |
| 2026-07-01 | JBU779 | JFK → MBJ | Jul 1, 12:13 UTC | Jul 2, 09:20 UTC | 21h 8m |
| 2026-06-30 | JBU280 | MBJ → JFK | Jun 30, 19:14 UTC | Jul 1, 19:00 UTC | 23h 47m |
| 2026-06-30 | JBU280 | JFK → JFK | Jun 30, 14:10 UTC | Jun 30, 22:30 UTC | 8h 20m |
| 2026-06-30 | JBU162 | - | Jun 30, 06:55 UTC | Jun 30, 11:45 UTC | 4h 50m |
| 2026-06-29 | JBU169 | JFK → PUJ | Jun 29, 11:59 UTC | Jun 30, 11:00 UTC | 23h 2m |
| 2026-06-29 | JBU1668 | PUJ → JFK | Jun 29, 00:26 UTC | Jun 29, 20:44 UTC | 20h 19m |
| 2026-06-28 | JBU1669 | - | Jun 28, 17:34 UTC | Jun 29, 03:49 UTC | 10h 15m |
| 2026-06-27 | JBU610 | JFK → JFK | Jun 27, 22:29 UTC | Jun 28, 13:45 UTC | 15h 15m |
| 2026-06-27 | JBU788 | - | Jun 27, 15:55 UTC | Jun 27, 19:39 UTC | 3h 45m |
| 2026-06-27 | JBU787 | - | Jun 27, 10:25 UTC | Jun 27, 13:55 UTC | 3h 30m |
| 2026-06-26 | JBU209 | JFK → SDQ | Jun 26, 09:34 UTC | Jun 27, 03:20 UTC | 17h 46m |
| 2026-06-25 | JBU57 | JFK → AUA | Jun 25, 14:42 UTC | Jun 26, 10:55 UTC | 20h 13m |
| 2026-06-24 | JBU1532 | CTG → JFK | Jun 24, 20:04 UTC | Jun 25, 18:59 UTC | 22h 56m |
| 2026-06-24 | JBU1533 | JFK → CTG | Jun 24, 13:30 UTC | Jun 24, 16:09 UTC | 2h 40m |
| 2026-06-24 | JBU1533 | JFK → CTG | Jun 24, 13:28 UTC | Jun 25, 00:55 UTC | 11h 27m |
| 2026-06-23 | JBU58 | MCO → JFK | Jun 23, 21:20 UTC | Jun 24, 00:30 UTC | 3h 10m |
| 2026-06-23 | JBU58 | MCO → JFK | Jun 23, 20:19 UTC | Jun 23, 20:34 UTC | 15m |
| 2026-06-23 | JBU57 | JFK → AUA | Jun 23, 18:14 UTC | Jun 23, 18:34 UTC | 20m |
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 N955JB page for operator, model, and routing details .