sensors Mode-S transponder
A6BD51
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N533TX · CESSNA 525B Citation CJ3 · operated by NLW INC DBA, TXJET INC
- Hex
- A6BD51
- Octal
- 51536521
- Decimal
- 10,927,441
- Country
- US
- Tail
- N533TX
- Type
- C25B
- Flights observed
- 52
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 1h ago
Current position
Country allocation
The ICAO 24-bit address A6BD51 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 |
|---|---|---|---|
| JLG533 | - | 52 | 2026-06-15 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-15 | JLG533 | - | Jun 15, 09:45 UTC | Jun 15, 12:00 UTC | 2h 15m |
| 2026-06-15 | JLG533 | LUK → IND | Jun 15, 03:24 UTC | Jun 15, 03:55 UTC | 30m |
| 2026-06-15 | JLG533 | IND → LUK | Jun 15, 01:35 UTC | Jun 15, 01:59 UTC | 25m |
| 2026-06-14 | JLG533 | - | Jun 14, 05:00 UTC | Jun 14, 06:45 UTC | 1h 45m |
| 2026-06-13 | JLG533 | - | Jun 13, 23:50 UTC | Jun 14, 01:35 UTC | 1h 45m |
| 2026-06-12 | JLG533 | - | Jun 12, 17:05 UTC | Jun 12, 17:35 UTC | 30m |
| 2026-06-12 | JLG533 | - | Jun 12, 11:15 UTC | Jun 12, 11:50 UTC | 35m |
| 2026-06-11 | JLG533 | - | Jun 11, 00:55 UTC | Jun 11, 02:00 UTC | 1h 5m |
| 2026-06-10 | JLG533 | IND → PDK | Jun 10, 19:05 UTC | Jun 10, 20:15 UTC | 1h 10m |
| 2026-06-09 | JLG533 | - | Jun 9, 06:20 UTC | Jun 9, 07:05 UTC | 45m |
| 2026-06-09 | JLG533 | - | Jun 9, 04:15 UTC | Jun 9, 05:10 UTC | 55m |
| 2026-06-09 | JLG533 | - | Jun 9, 00:40 UTC | Jun 9, 01:05 UTC | 25m |
| 2026-06-07 | JLG533 | - | Jun 7, 21:15 UTC | Jun 7, 22:15 UTC | 1h 0m |
| 2026-06-07 | JLG533 | - | Jun 7, 16:35 UTC | Jun 7, 17:35 UTC | 1h 0m |
| 2026-06-06 | JLG533 | - | Jun 6, 07:10 UTC | Jun 6, 07:50 UTC | 40m |
| 2026-06-06 | JLG533 | - | Jun 6, 05:10 UTC | Jun 6, 06:30 UTC | 1h 20m |
| 2026-06-06 | JLG533 | - | Jun 6, 00:00 UTC | Jun 6, 01:35 UTC | 1h 35m |
| 2026-06-05 | JLG533 | - | Jun 5, 22:30 UTC | Jun 5, 23:15 UTC | 45m |
| 2026-06-04 | JLG533 | - | Jun 4, 18:40 UTC | Jun 4, 19:00 UTC | 20m |
| 2026-06-04 | JLG533 | - | Jun 4, 13:00 UTC | Jun 4, 13:15 UTC | 15m |
| 2026-06-01 | JLG533 | - | Jun 1, 22:30 UTC | Jun 1, 23:10 UTC | 40m |
| 2026-06-01 | JLG533 | - | Jun 1, 17:40 UTC | Jun 1, 18:25 UTC | 45m |
| 2026-05-31 | JLG533 | - | May 31, 00:15 UTC | May 31, 01:11 UTC | 56m |
| 2026-05-30 | JLG533 | DSM → IND | May 30, 16:45 UTC | May 30, 17:50 UTC | 1h 5m |
| 2026-05-30 | JLG533 | - | May 30, 11:30 UTC | May 30, 12:35 UTC | 1h 5m |
| 2026-05-29 | JLG533 | - | May 29, 20:25 UTC | May 29, 20:50 UTC | 25m |
| 2026-05-29 | JLG533 | - | May 29, 15:15 UTC | May 29, 15:40 UTC | 25m |
| 2026-05-23 | JLG533 | - | May 23, 15:20 UTC | May 23, 16:20 UTC | 1h 0m |
| 2026-05-23 | JLG533 | ATL → AGC | May 23, 13:30 UTC | May 23, 14:45 UTC | 1h 15m |
| 2026-05-23 | JLG533 | - | May 23, 07:10 UTC | May 23, 08:25 UTC | 1h 15m |
| 2026-05-08 | JLG533 | - | May 8, 19:40 UTC | May 8, 20:25 UTC | 45m |
| 2026-05-08 | JLG533 | - | May 8, 14:40 UTC | May 8, 15:25 UTC | 45m |
| 2026-05-05 | JLG533 | - | May 5, 20:55 UTC | May 5, 21:40 UTC | 45m |
| 2026-05-05 | JLG533 | IND → AZO | May 5, 17:00 UTC | May 5, 17:35 UTC | 35m |
| 2026-05-02 | JLG533 | - | May 2, 06:25 UTC | May 2, 07:25 UTC | 1h 0m |
| 2026-05-02 | JLG533 | CHA → BKL | May 2, 04:30 UTC | May 2, 05:45 UTC | 1h 15m |
| 2026-05-01 | JLG533 | - | May 1, 23:20 UTC | May 2, 00:45 UTC | 1h 25m |
| 2026-05-01 | JLG533 | - | May 1, 21:45 UTC | May 1, 22:40 UTC | 55m |
| 2026-04-30 | JLG533 | - | Apr 30, 15:30 UTC | Apr 30, 16:05 UTC | 35m |
| 2026-04-30 | JLG533 | - | Apr 30, 13:55 UTC | Apr 30, 15:00 UTC | 1h 5m |
| 2026-04-30 | JLG533 | - | Apr 30, 09:00 UTC | Apr 30, 10:05 UTC | 1h 5m |
| 2026-04-29 | JLG533 | - | Apr 29, 22:50 UTC | Apr 29, 23:20 UTC | 29m |
| 2026-04-26 | JLG533 | - | Apr 26, 10:30 UTC | Apr 26, 10:55 UTC | 25m |
| 2026-04-19 | JLG533 | - | Apr 19, 15:40 UTC | Apr 19, 16:10 UTC | 30m |
| 2026-04-19 | JLG533 | - | Apr 19, 13:45 UTC | Apr 19, 14:25 UTC | 40m |
| 2026-04-17 | JLG533 | - | Apr 17, 13:20 UTC | Apr 17, 14:10 UTC | 50m |
| 2026-04-17 | JLG533 | - | Apr 17, 11:20 UTC | Apr 17, 13:15 UTC | 1h 55m |
| 2026-04-17 | JLG533 | - | Apr 17, 10:05 UTC | Apr 17, 11:15 UTC | 1h 10m |
| 2026-04-17 | JLG533 | - | Apr 17, 07:20 UTC | Apr 17, 09:10 UTC | 1h 50m |
| 2026-04-17 | JLG533 | - | Apr 17, 06:35 UTC | Apr 17, 07:15 UTC | 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 N533TX page for operator, model, and routing details .