sensors Mode-S transponder
AF85A3
ICAO 24-bit transponder address
- Hex
- AF85A3
- Octal
- 53702643
- Decimal
- 11,503,011
- Flights observed
- 28
- Distinct callsigns
- 11
- Country
- -
- Last broadcast
- 12h ago
Last known position
Callsign history 11 distinct
Recent flights last 28
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | ZORRO77 | - | May 29, 17:30 UTC | May 29, 17:40 UTC | 10m |
| 2026-05-28 | ZORRO75 | OKC → OKC | May 28, 21:15 UTC | May 28, 23:15 UTC | 2h 0m |
| 2026-05-28 | ZORRO75 | OKC → OKC | May 28, 17:20 UTC | May 28, 19:00 UTC | 1h 40m |
| 2026-05-26 | ZORRO31 | OKC → OKC | May 26, 16:30 UTC | May 26, 18:59 UTC | 2h 30m |
| 2026-05-13 | ZORRO77 | - | May 13, 21:00 UTC | May 13, 23:05 UTC | 2h 5m |
| 2026-05-13 | ZORRO21 | OKC → OKC | May 13, 17:15 UTC | May 13, 18:50 UTC | 1h 35m |
| 2026-05-12 | ZORRO43 | OKC → OKC | May 12, 21:25 UTC | May 12, 23:15 UTC | 1h 50m |
| 2026-05-12 | ZORRO31 | OKC → OKC | May 12, 15:55 UTC | May 12, 18:10 UTC | 2h 15m |
| 2026-05-11 | ZORRO39 | - | May 11, 21:05 UTC | May 11, 22:35 UTC | 1h 29m |
| 2026-05-11 | ZORRO39 | OKC → OKC | May 11, 16:05 UTC | May 11, 18:30 UTC | 2h 26m |
| 2026-05-08 | JAKAL07 | - | May 8, 20:35 UTC | May 8, 21:10 UTC | 35m |
| 2026-05-08 | JAKAL07 | - | May 8, 14:15 UTC | May 8, 14:55 UTC | 40m |
| 2026-05-07 | ZORRO43 | OKC → OKC | May 7, 19:00 UTC | May 7, 20:50 UTC | 1h 50m |
| 2026-05-07 | ZORRO31 | OKC → OKC | May 7, 14:35 UTC | May 7, 16:30 UTC | 1h 55m |
| 2026-05-06 | ZORRO77 | OKC → OKC | May 6, 15:10 UTC | May 6, 17:10 UTC | 2h 0m |
| 2026-05-04 | ZORRO43 | OKC → OKC | May 4, 21:10 UTC | May 4, 22:30 UTC | 1h 20m |
| 2026-05-04 | ZORRO43 | OKC → OKC | May 4, 16:20 UTC | May 4, 18:20 UTC | 2h 0m |
| 2026-05-01 | ZORRO77 | OKC → OKC | May 1, 20:45 UTC | May 1, 22:45 UTC | 2h 0m |
| 2026-05-01 | ZORRO91 | OKC → OKC | May 1, 16:00 UTC | May 1, 18:00 UTC | 2h 0m |
| 2026-04-30 | ZORRO91 | OKC → OKC | Apr 30, 16:10 UTC | Apr 30, 18:00 UTC | 1h 50m |
| 2026-04-29 | ZORRO39 | - | Apr 29, 19:30 UTC | Apr 29, 21:25 UTC | 1h 55m |
| 2026-04-29 | ZORRO39 | - | Apr 29, 15:55 UTC | Apr 29, 17:40 UTC | 1h 45m |
| 2026-04-27 | ZORRO13 | OKC → OKC | Apr 27, 16:45 UTC | Apr 27, 19:05 UTC | 2h 20m |
| 2026-04-24 | ZORRO43 | OKC → OKC | Apr 24, 15:40 UTC | Apr 24, 17:35 UTC | 1h 55m |
| 2026-04-20 | ZORRO43 | OKC → OKC | Apr 20, 20:35 UTC | Apr 20, 22:35 UTC | 2h 0m |
| 2026-04-20 | ZORRO67 | - | Apr 20, 15:45 UTC | Apr 20, 17:40 UTC | 1h 55m |
| 2026-04-16 | ZORRO55 | - | Apr 16, 22:05 UTC | Apr 16, 22:20 UTC | 15m |
| 2026-04-13 | ZORRO77 | OKC → OKC | Apr 13, 16:45 UTC | Apr 13, 18:25 UTC | 1h 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.