sensors Mode-S transponder
AFA800
ICAO 24-bit transponder address
- Hex
- AFA800
- Octal
- 53724000
- Decimal
- 11,511,808
No current signal · last broadcast 2h ago
- Flights observed
- 41
- Distinct callsigns
- 18
- Country
- -
- Last broadcast
- 2h ago
Last known position
Callsign history 18 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| ZORRO77 | - | 5 | 2026-06-24 |
| ZORRO43 | - | 5 | 2026-06-04 |
| ZORRO87 | - | 3 | 2026-06-25 |
| ZORRO55 | - | 3 | 2026-07-09 |
| ZORRO34 | - | 3 | 2026-07-08 |
| JAKAL19 | - | 3 | 2026-06-17 |
| ZORRO91 | - | 2 | 2026-06-03 |
| ZORRO52 | - | 2 | 2026-07-02 |
| ZORRO33 | - | 2 | 2026-05-29 |
| ZORRO23 | - | 2 | 2026-05-08 |
| ZORRO20 | - | 2 | 2026-07-14 |
| JAKAL28 | - | 2 | 2026-06-19 |
| JAKAL14 | - | 2 | 2026-06-26 |
| ZORRO75 | - | 1 | 2026-04-20 |
| ZORRO66 | - | 1 | 2026-05-18 |
| ZORRO65 | - | 1 | 2026-05-04 |
| JAKAL04 | - | 1 | 2026-06-29 |
| JAKAL03 | - | 1 | 2026-06-30 |
Recent flights last 41
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | ZORRO20 | - | Jul 14, 17:00 UTC | Jul 14, 17:25 UTC | 25m |
| 2026-07-14 | ZORRO20 | - | Jul 14, 15:25 UTC | Jul 14, 15:45 UTC | 20m |
| 2026-07-09 | ZORRO55 | OKC → OKC | Jul 9, 17:55 UTC | Jul 9, 20:00 UTC | 2h 5m |
| 2026-07-08 | ZORRO34 | - | Jul 8, 15:30 UTC | Jul 8, 17:25 UTC | 1h 55m |
| 2026-07-07 | ZORRO34 | - | Jul 7, 19:35 UTC | Jul 7, 19:55 UTC | 20m |
| 2026-07-07 | ZORRO34 | - | Jul 7, 15:35 UTC | Jul 7, 16:10 UTC | 35m |
| 2026-07-02 | ZORRO52 | - | Jul 2, 14:35 UTC | Jul 2, 16:35 UTC | 2h 0m |
| 2026-07-01 | ZORRO52 | - | Jul 1, 19:00 UTC | Jul 1, 21:00 UTC | 2h 0m |
| 2026-06-30 | JAKAL03 | - | Jun 30, 18:55 UTC | Jun 30, 19:15 UTC | 20m |
| 2026-06-29 | JAKAL04 | - | Jun 29, 15:14 UTC | Jun 29, 16:10 UTC | 55m |
| 2026-06-26 | JAKAL14 | - | Jun 26, 16:05 UTC | Jun 26, 16:20 UTC | 15m |
| 2026-06-26 | JAKAL14 | - | Jun 26, 14:09 UTC | Jun 26, 14:44 UTC | 35m |
| 2026-06-25 | ZORRO55 | - | Jun 25, 18:59 UTC | Jun 25, 20:59 UTC | 2h 0m |
| 2026-06-25 | ZORRO87 | OKC → OKC | Jun 25, 14:29 UTC | Jun 25, 16:29 UTC | 2h 0m |
| 2026-06-24 | ZORRO77 | OKC → OKC | Jun 24, 19:10 UTC | Jun 24, 21:09 UTC | 2h 0m |
| 2026-06-19 | JAKAL28 | - | Jun 19, 02:59 UTC | Jun 19, 03:55 UTC | 55m |
| 2026-06-19 | JAKAL28 | - | Jun 19, 00:24 UTC | Jun 19, 00:55 UTC | 30m |
| 2026-06-17 | JAKAL19 | - | Jun 17, 22:25 UTC | Jun 17, 23:50 UTC | 1h 25m |
| 2026-06-17 | JAKAL19 | - | Jun 17, 19:25 UTC | Jun 17, 20:30 UTC | 1h 5m |
| 2026-06-08 | JAKAL19 | - | Jun 8, 15:00 UTC | Jun 8, 19:05 UTC | 4h 5m |
| 2026-06-04 | ZORRO43 | OKC → OKC | Jun 4, 19:55 UTC | Jun 4, 22:40 UTC | 2h 45m |
| 2026-06-03 | ZORRO87 | - | Jun 3, 20:50 UTC | Jun 3, 23:00 UTC | 2h 10m |
| 2026-06-03 | ZORRO91 | OKC → OKC | Jun 3, 16:40 UTC | Jun 3, 19:15 UTC | 2h 35m |
| 2026-06-02 | ZORRO43 | - | Jun 2, 21:15 UTC | Jun 2, 23:15 UTC | 2h 0m |
| 2026-06-02 | ZORRO87 | OKC → OKC | Jun 2, 16:50 UTC | Jun 2, 19:00 UTC | 2h 10m |
| 2026-06-01 | ZORRO77 | - | Jun 1, 20:40 UTC | Jun 1, 22:40 UTC | 2h 0m |
| 2026-06-01 | ZORRO77 | - | Jun 1, 16:20 UTC | Jun 1, 17:50 UTC | 1h 30m |
| 2026-05-29 | ZORRO33 | - | May 29, 18:30 UTC | May 29, 18:50 UTC | 20m |
| 2026-05-29 | ZORRO33 | OKC → RQO | May 29, 17:00 UTC | May 29, 17:15 UTC | 15m |
| 2026-05-28 | ZORRO91 | OKC → OKC | May 28, 17:00 UTC | May 28, 18:20 UTC | 1h 20m |
| 2026-05-18 | ZORRO66 | OKC → OKC | May 18, 14:55 UTC | May 18, 15:35 UTC | 40m |
| 2026-05-15 | ZORRO43 | - | May 15, 00:55 UTC | May 15, 03:00 UTC | 2h 5m |
| 2026-05-14 | ZORRO43 | OKC → OKC | May 14, 20:40 UTC | May 14, 22:35 UTC | 1h 55m |
| 2026-05-08 | ZORRO23 | - | May 8, 03:19 UTC | May 8, 03:49 UTC | 30m |
| 2026-05-08 | ZORRO23 | - | May 8, 01:49 UTC | May 8, 03:14 UTC | 1h 25m |
| 2026-05-07 | ZORRO77 | - | May 7, 20:55 UTC | May 7, 22:54 UTC | 2h 0m |
| 2026-05-05 | ZORRO43 | OKC → OKC | May 5, 01:10 UTC | May 5, 02:50 UTC | 1h 40m |
| 2026-05-04 | ZORRO65 | OKC → OKC | May 4, 20:40 UTC | May 4, 21:15 UTC | 35m |
| 2026-04-24 | ZORRO77 | OKC → OKC | Apr 24, 20:50 UTC | Apr 24, 22:25 UTC | 1h 35m |
| 2026-04-24 | ZORRO55 | OKC → OKC | Apr 24, 16:00 UTC | Apr 24, 17:00 UTC | 1h 0m |
| 2026-04-20 | ZORRO75 | OKC → OKC | Apr 20, 16:10 UTC | Apr 20, 18:00 UTC | 1h 50m |
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.
Mode-S AFA800 frequently asked
What is Mode-S code AFA800?
AFA800 is an ICAO 24-bit transponder address.
Is AFA800 broadcasting right now?
No active broadcast right now. Last signal was 2h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex AFA800, octal 53724000, decimal 11,511,808.