sensors Mode-S transponder
A1B2A8
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N2084J · AIRBUS A-321neo · operated by UMB BANK NA TRUSTEE
- Hex
- A1B2A8
- Octal
- 50331250
- Decimal
- 10,597,032
- Country
- US
- Tail
- N2084J
- Type
- A21N
- Flights observed
- 132
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 4h ago
Last known position
Country allocation
The ICAO 24-bit address A1B2A8 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 |
|---|---|---|---|
| JBU466 | - | 5 | 2026-07-12 |
| JBU505 | - | 4 | 2026-07-13 |
| JBU387 | JetBlue Airways | 4 | 2026-04-17 |
| JBU1966 | - | 4 | 2026-07-11 |
| JBU1769 | - | 4 | 2026-07-04 |
| JBU1360 | JetBlue Airways | 4 | 2026-04-15 |
| JBU1359 | - | 4 | 2026-04-15 |
| JBU1328 | JetBlue Airways | 4 | 2026-04-20 |
| JBU1188 | - | 4 | 2026-06-30 |
| JBU8627 | JetBlue Airways | 3 | 2026-05-01 |
| JBU787 | - | 3 | 2026-07-10 |
| JBU561 | JetBlue Airways | 3 | 2026-04-22 |
| JBU465 | - | 3 | 2026-07-12 |
| JBU1965 | - | 3 | 2026-06-29 |
| JBU1669 | - | 3 | 2026-07-05 |
| JBU1584 | JetBlue Airways | 3 | 2026-05-01 |
| JBU1483 | JetBlue Airways | 3 | 2026-05-01 |
| JBU1383 | JetBlue Airways | 3 | 2026-04-20 |
| JBU1370 | JetBlue Airways | 3 | 2026-04-20 |
| JBU1124 | JetBlue Airways | 3 | 2026-04-18 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | JBU1611 | - | Jul 14, 16:15 UTC | Jul 14, 18:40 UTC | 2h 25m |
| 2026-07-14 | JBU1611 | FLL → AUA | Jul 14, 16:13 UTC | Jul 14, 22:50 UTC | 6h 37m |
| 2026-07-14 | JBU1505 | EWR → FLL | Jul 14, 10:15 UTC | Jul 14, 12:45 UTC | 2h 30m |
| 2026-07-14 | JBU706 | - | Jul 14, 02:25 UTC | Jul 14, 04:55 UTC | 2h 30m |
| 2026-07-13 | JBU505 | JFK → FLL | Jul 13, 10:50 UTC | Jul 13, 22:30 UTC | 11h 40m |
| 2026-07-12 | JBU466 | GEO → JFK | Jul 12, 22:23 UTC | Jul 13, 22:00 UTC | 23h 38m |
| 2026-07-12 | JBU465 | - | Jul 12, 15:45 UTC | Jul 13, 03:45 UTC | 12h 0m |
| 2026-07-11 | JBU1532 | CTG → JFK | Jul 11, 19:59 UTC | Jul 12, 16:20 UTC | 20h 22m |
| 2026-07-11 | JBU1966 | GEO → JFK | Jul 11, 05:50 UTC | Jul 12, 00:30 UTC | 18h 41m |
| 2026-07-10 | JBU1966 | JFK → JFK | Jul 10, 23:25 UTC | Jul 11, 11:10 UTC | 11h 45m |
| 2026-07-10 | JBU787 | - | Jul 10, 13:15 UTC | Jul 10, 13:30 UTC | 15m |
| 2026-07-10 | JBU787 | JFK → SXM | Jul 10, 10:27 UTC | Jul 11, 08:10 UTC | 21h 44m |
| 2026-07-10 | JBU787 | - | Jul 10, 10:30 UTC | Jul 10, 11:05 UTC | 35m |
| 2026-07-09 | JBU517 | BOS → JFK | Jul 9, 13:28 UTC | Jul 10, 11:05 UTC | 21h 37m |
| 2026-07-09 | JBU517 | BOS → JFK | Jul 9, 13:30 UTC | Jul 9, 14:55 UTC | 1h 25m |
| 2026-07-09 | JBU518 | - | Jul 9, 10:25 UTC | Jul 9, 11:50 UTC | 1h 25m |
| 2026-07-08 | JBU505 | JFK → FLL | Jul 8, 10:00 UTC | Jul 8, 21:45 UTC | 11h 45m |
| 2026-07-07 | JBU1858 | AUA → JFK | Jul 7, 17:39 UTC | Jul 8, 13:40 UTC | 20h 2m |
| 2026-07-07 | JBU1759 | JFK → KIN | Jul 7, 01:12 UTC | Jul 7, 22:10 UTC | 20h 59m |
| 2026-07-07 | JBU1759 | - | Jul 7, 01:15 UTC | Jul 7, 03:45 UTC | 2h 30m |
| 2026-07-05 | JBU1669 | - | Jul 5, 17:05 UTC | Jul 5, 17:50 UTC | 45m |
| 2026-07-05 | JBU1669 | JFK → PUJ | Jul 5, 17:00 UTC | Jul 6, 16:00 UTC | 23h 0m |
| 2026-07-04 | JBU610 | JFK → JFK | Jul 4, 21:50 UTC | Jul 5, 13:30 UTC | 15h 40m |
| 2026-07-04 | JBU1769 | JFK → JFK | Jul 4, 03:45 UTC | Jul 4, 18:35 UTC | 14h 50m |
| 2026-07-03 | JBU57 | - | Jul 3, 14:35 UTC | Jul 3, 17:50 UTC | 3h 15m |
| 2026-07-03 | JBU57 | JFK → AUA | Jul 3, 14:35 UTC | Jul 4, 07:20 UTC | 16h 45m |
| 2026-07-03 | JBU1024 | - | Jul 3, 05:35 UTC | Jul 3, 10:30 UTC | 4h 55m |
| 2026-07-02 | JBU823 | JFK → LAX | Jul 2, 22:20 UTC | Jul 3, 03:35 UTC | 5h 15m |
| 2026-07-02 | JBU788 | JFK → JFK | Jul 2, 10:30 UTC | Jul 2, 19:00 UTC | 8h 30m |
| 2026-07-01 | JBU466 | GEO → JFK | Jul 1, 22:05 UTC | Jul 2, 19:00 UTC | 20h 56m |
| 2026-07-01 | JBU465 | JFK → GEO | Jul 1, 15:10 UTC | Jul 2, 13:35 UTC | 22h 26m |
| 2026-06-30 | JBU1188 | - | Jun 30, 19:25 UTC | Jun 30, 22:45 UTC | 3h 20m |
| 2026-06-30 | JBU1188 | SXM → JFK | Jun 30, 19:06 UTC | Jul 1, 15:45 UTC | 20h 39m |
| 2026-06-30 | JBU887 | - | Jun 30, 13:35 UTC | Jun 30, 16:30 UTC | 2h 55m |
| 2026-06-29 | JBU1965 | - | Jun 29, 21:50 UTC | Jun 30, 02:20 UTC | 4h 31m |
| 2026-06-29 | JBU1965 | JFK → GEO | Jun 29, 21:45 UTC | Jun 30, 19:40 UTC | 21h 56m |
| 2026-06-29 | JBU1769 | JFK → GYE | Jun 29, 04:01 UTC | Jun 30, 02:00 UTC | 22h 0m |
| 2026-06-29 | JBU1769 | - | Jun 29, 04:04 UTC | Jun 29, 07:50 UTC | 3h 45m |
| 2026-06-28 | JBU1188 | JFK → JFK | Jun 28, 13:55 UTC | Jun 28, 23:14 UTC | 9h 20m |
| 2026-06-27 | JBU1669 | JFK → PUJ | Jun 27, 15:49 UTC | Jun 28, 13:59 UTC | 22h 11m |
| 2026-06-26 | JBU309 | - | Jun 26, 22:55 UTC | Jun 26, 23:19 UTC | 25m |
| 2026-06-26 | JBU309 | JFK → SDQ | Jun 26, 22:50 UTC | Jun 27, 16:35 UTC | 17h 45m |
| 2026-06-26 | JBU788 | - | Jun 26, 16:20 UTC | Jun 26, 20:04 UTC | 3h 45m |
| 2026-06-25 | JBU466 | GEO → JFK | Jun 25, 23:15 UTC | Jun 26, 20:29 UTC | 21h 15m |
| 2026-06-25 | JBU466 | - | Jun 25, 18:29 UTC | Jun 26, 04:39 UTC | 10h 10m |
| 2026-06-25 | JBU465 | - | Jun 25, 15:29 UTC | Jun 25, 15:54 UTC | 25m |
| 2026-06-23 | JBU1936 | STI → JFK | Jun 23, 05:13 UTC | Jun 23, 22:10 UTC | 16h 57m |
| 2026-06-22 | JBU380 | MBJ → JFK | Jun 22, 16:26 UTC | Jun 23, 15:15 UTC | 22h 49m |
| 2026-06-22 | JBU1179 | JFK → MBJ | Jun 22, 11:24 UTC | Jun 23, 08:39 UTC | 21h 16m |
| 2026-06-22 | JBU1179 | - | Jun 22, 11:24 UTC | Jun 22, 13:49 UTC | 2h 25m |
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 N2084J page for operator, model, and routing details .