sensors Mode-S transponder
ADFFBB
ICAO 24-bit transponder address
Currently assigned to 65-10320 · Northrop T-38C Talon
- Hex
- ADFFBB
- Octal
- 53377673
- Decimal
- 11,403,195
- Tail
- 65-10320
- Type
- T38
- Flights observed
- 23
- Distinct callsigns
- 20
- Country
- -
- Last broadcast
- 1d ago
Last known position
Callsign history 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| BULLY25 | - | 2 | 2026-06-29 |
| SWEEP41 | - | 1 | 2026-06-16 |
| STEER92 | - | 1 | 2026-06-24 |
| STEER91 | - | 1 | 2026-06-17 |
| STEER81 | - | 1 | 2026-06-23 |
| STEER21 | - | 1 | 2026-06-18 |
| SHED92 | - | 1 | 2026-07-13 |
| SHED71 | - | 1 | 2026-06-15 |
| SHED41 | - | 1 | 2026-06-12 |
| RIBYE31 | - | 1 | 2026-06-23 |
| OCTNE21 | - | 1 | 2026-06-25 |
| OCTAN51 | - | 1 | 2026-06-17 |
| OCTAN12 | - | 1 | 2026-06-25 |
| JUMP10 | - | 1 | 2026-06-24 |
| GRIM41 | - | 1 | 2026-07-13 |
| GLOCK51 | - | 1 | 2026-06-29 |
| ERASR61 | - | 1 | 2026-06-16 |
| COOL52 | - | 1 | 2026-07-13 |
| BULLY68 | - | 1 | 2026-07-07 |
| BULLY55 | - | 1 | 2026-07-06 |
Recent flights last 23
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | SHED92 | - | Jul 13, 21:05 UTC | Jul 13, 21:45 UTC | 40m |
| 2026-07-13 | GRIM41 | - | Jul 13, 18:00 UTC | Jul 13, 18:35 UTC | 35m |
| 2026-07-13 | COOL52 | - | Jul 13, 13:35 UTC | Jul 13, 13:55 UTC | 20m |
| 2026-07-07 | BULLY46 | - | Jul 7, 18:50 UTC | Jul 7, 19:05 UTC | 15m |
| 2026-07-07 | BULLY68 | - | Jul 7, 15:35 UTC | Jul 7, 15:45 UTC | 10m |
| 2026-07-06 | BULLY55 | - | Jul 6, 15:20 UTC | Jul 6, 15:35 UTC | 15m |
| 2026-06-29 | BULLY25 | - | Jun 29, 17:10 UTC | Jun 29, 17:19 UTC | 10m |
| 2026-06-29 | GLOCK51 | - | Jun 29, 13:49 UTC | Jun 29, 14:14 UTC | 25m |
| 2026-06-25 | OCTAN12 | - | Jun 25, 21:15 UTC | Jun 25, 21:55 UTC | 40m |
| 2026-06-25 | OCTNE21 | - | Jun 25, 13:14 UTC | Jun 25, 13:45 UTC | 30m |
| 2026-06-24 | STEER92 | - | Jun 24, 21:04 UTC | Jun 24, 21:50 UTC | 45m |
| 2026-06-24 | JUMP10 | - | Jun 24, 13:44 UTC | Jun 24, 14:39 UTC | 55m |
| 2026-06-23 | STEER81 | - | Jun 23, 17:30 UTC | Jun 23, 17:50 UTC | 20m |
| 2026-06-23 | RIBYE31 | - | Jun 23, 13:45 UTC | Jun 23, 14:25 UTC | 40m |
| 2026-06-18 | STEER21 | - | Jun 18, 13:30 UTC | Jun 18, 14:25 UTC | 55m |
| 2026-06-17 | STEER91 | - | Jun 17, 21:15 UTC | Jun 17, 21:40 UTC | 25m |
| 2026-06-17 | BULLY25 | - | Jun 17, 17:35 UTC | Jun 17, 17:45 UTC | 10m |
| 2026-06-17 | OCTAN51 | - | Jun 17, 13:55 UTC | Jun 17, 14:35 UTC | 40m |
| 2026-06-16 | ERASR61 | - | Jun 16, 20:55 UTC | Jun 16, 21:20 UTC | 25m |
| 2026-06-16 | SWEEP41 | - | Jun 16, 13:34 UTC | Jun 16, 14:09 UTC | 35m |
| 2026-06-15 | SHED71 | - | Jun 15, 17:34 UTC | Jun 15, 17:54 UTC | 20m |
| 2026-06-12 | SHED41 | - | Jun 12, 16:50 UTC | Jun 12, 17:35 UTC | 45m |
| 2026-06-12 | BULLY08 | - | Jun 12, 12:15 UTC | Jun 12, 12:35 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 65-10320 page for operator, model, and routing details .