sensors Mode-S transponder
ADFFB9
ICAO 24-bit transponder address
Currently assigned to 64-13282 · Northrop T-38C Talon
- Hex
- ADFFB9
- Octal
- 53377671
- Decimal
- 11,403,193
- Tail
- 64-13282
- Type
- T38
- Flights observed
- 23
- Distinct callsigns
- 20
- Country
- -
- Last broadcast
- 22d ago
Last known position
Callsign history 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| RATLR21 | - | 2 | 2026-04-14 |
| SWEEP71 | - | 1 | 2026-06-01 |
| SHED71 | - | 1 | 2026-06-23 |
| RNCID62 | - | 1 | 2026-06-03 |
| RIBYE42 | - | 1 | 2026-06-09 |
| RANCD51 | - | 1 | 2026-05-15 |
| RANCD32 | - | 1 | 2026-06-09 |
| RANCD11 | - | 1 | 2026-06-02 |
| OCTNE71 | - | 1 | 2026-06-10 |
| OCTAN12 | - | 1 | 2026-06-11 |
| JUMP25 | - | 1 | 2026-06-02 |
| GLOCK72 | - | 1 | 2026-06-08 |
| FIEND22 | - | 1 | 2026-06-10 |
| EXCEL67 | - | 1 | 2026-06-24 |
| ETHER81 | - | 1 | 2026-06-09 |
| BULLY70 | - | 1 | 2026-06-01 |
| BULLY68 | - | 1 | 2026-06-08 |
| BULLY24 | - | 1 | 2026-05-15 |
| BULLY20 | - | 1 | 2026-06-25 |
| BULLY19 | - | 1 | 2026-06-25 |
Recent flights last 23
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-25 | BULLY19 | - | Jun 25, 20:49 UTC | Jun 25, 21:05 UTC | 15m |
| 2026-06-25 | BULLY20 | - | Jun 25, 13:14 UTC | Jun 25, 13:24 UTC | 10m |
| 2026-06-24 | EXCEL67 | - | Jun 24, 13:50 UTC | Jun 24, 14:09 UTC | 20m |
| 2026-06-23 | SHED71 | - | Jun 23, 17:34 UTC | Jun 23, 18:10 UTC | 35m |
| 2026-06-11 | OCTAN12 | - | Jun 11, 13:20 UTC | Jun 11, 13:35 UTC | 15m |
| 2026-06-10 | OCTNE71 | - | Jun 10, 17:15 UTC | Jun 10, 17:55 UTC | 40m |
| 2026-06-10 | FIEND22 | - | Jun 10, 13:20 UTC | Jun 10, 13:40 UTC | 20m |
| 2026-06-09 | RANCD32 | - | Jun 9, 21:15 UTC | Jun 9, 21:55 UTC | 40m |
| 2026-06-09 | ETHER81 | - | Jun 9, 17:25 UTC | Jun 9, 18:10 UTC | 45m |
| 2026-06-09 | RIBYE42 | - | Jun 9, 13:50 UTC | Jun 9, 14:25 UTC | 35m |
| 2026-06-08 | BULLY68 | - | Jun 8, 21:10 UTC | Jun 8, 21:20 UTC | 10m |
| 2026-06-08 | GLOCK72 | - | Jun 8, 17:35 UTC | Jun 8, 18:05 UTC | 30m |
| 2026-06-03 | RNCID62 | - | Jun 3, 15:35 UTC | Jun 3, 16:00 UTC | 25m |
| 2026-06-02 | RANCD11 | - | Jun 2, 18:45 UTC | Jun 2, 19:15 UTC | 30m |
| 2026-06-02 | JUMP25 | - | Jun 2, 02:30 UTC | Jun 2, 02:50 UTC | 20m |
| 2026-06-01 | BULLY70 | - | Jun 1, 23:10 UTC | Jun 1, 23:20 UTC | 10m |
| 2026-06-01 | SWEEP71 | - | Jun 1, 16:05 UTC | Jun 1, 16:35 UTC | 30m |
| 2026-05-15 | BULLY24 | - | May 15, 17:25 UTC | May 15, 17:35 UTC | 10m |
| 2026-05-15 | RANCD51 | - | May 15, 13:50 UTC | May 15, 14:40 UTC | 50m |
| 2026-05-06 | BOXER32 | - | May 6, 16:45 UTC | May 6, 17:05 UTC | 20m |
| 2026-05-06 | BOXER33 | - | May 6, 00:05 UTC | May 6, 00:15 UTC | 10m |
| 2026-04-14 | RATLR21 | - | Apr 14, 17:20 UTC | Apr 14, 17:55 UTC | 35m |
| 2026-04-14 | RATLR21 | - | Apr 14, 13:25 UTC | Apr 14, 13:35 UTC | 10m |
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 64-13282 page for operator, model, and routing details .