sensors Mode-S transponder
AF3B60
ICAO 24-bit transponder address
- Hex
- AF3B60
- Octal
- 53635540
- Decimal
- 11,484,000
No current signal · last broadcast 1h ago
- Flights observed
- 42
- Distinct callsigns
- 17
- Country
- -
- Last broadcast
- 1h ago
Last known position
Callsign history 17 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| ZORRO91 | - | 8 | 2026-07-13 |
| ZORRO77 | - | 6 | 2026-07-13 |
| ZORRO23 | - | 5 | 2026-07-02 |
| ZORRO66 | - | 4 | 2026-07-08 |
| ZORRO43 | - | 3 | 2026-06-29 |
| ZORRO20 | - | 3 | 2026-05-08 |
| ZORRO34 | - | 2 | 2026-05-14 |
| ZORRO28 | - | 2 | 2026-05-29 |
| ZORRO87 | - | 1 | 2026-07-10 |
| ZORRO76 | - | 1 | 2026-07-09 |
| ZORRO75 | - | 1 | 2026-06-16 |
| ZORRO52 | - | 1 | 2026-05-04 |
| ZORRO24 | - | 1 | 2026-06-29 |
| ZORRO21 | - | 1 | 2026-05-14 |
| ZORRO19 | - | 1 | 2026-06-24 |
| ZORRO13 | - | 1 | 2026-06-25 |
| NOMAD11 | - | 1 | 2026-07-14 |
Recent flights last 42
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | NOMAD11 | OKC → OKC | Jul 14, 13:50 UTC | Jul 14, 15:25 UTC | 1h 35m |
| 2026-07-13 | ZORRO77 | OKC → OKC | Jul 13, 23:40 UTC | Jul 14, 01:45 UTC | 2h 5m |
| 2026-07-13 | ZORRO77 | OKC → OKC | Jul 13, 18:15 UTC | Jul 13, 20:20 UTC | 2h 5m |
| 2026-07-13 | ZORRO91 | OKC → OKC | Jul 13, 14:05 UTC | Jul 13, 15:55 UTC | 1h 50m |
| 2026-07-10 | ZORRO91 | OKC → OKC | Jul 10, 19:00 UTC | Jul 10, 21:00 UTC | 2h 0m |
| 2026-07-10 | ZORRO87 | OKC → OKC | Jul 10, 14:45 UTC | Jul 10, 16:35 UTC | 1h 50m |
| 2026-07-09 | ZORRO76 | - | Jul 9, 19:05 UTC | Jul 9, 20:55 UTC | 1h 50m |
| 2026-07-09 | ZORRO91 | OKC → OKC | Jul 9, 14:10 UTC | Jul 9, 15:55 UTC | 1h 45m |
| 2026-07-08 | ZORRO66 | - | Jul 8, 15:40 UTC | Jul 8, 16:00 UTC | 20m |
| 2026-07-08 | ZORRO66 | - | Jul 8, 14:05 UTC | Jul 8, 14:25 UTC | 20m |
| 2026-07-07 | ZORRO77 | OKC → OKC | Jul 7, 19:35 UTC | Jul 7, 21:30 UTC | 1h 55m |
| 2026-07-07 | ZORRO91 | OKC → OKC | Jul 7, 14:50 UTC | Jul 7, 15:35 UTC | 45m |
| 2026-07-02 | ZORRO23 | - | Jul 2, 15:25 UTC | Jul 2, 17:35 UTC | 2h 10m |
| 2026-07-01 | ZORRO23 | - | Jul 1, 19:30 UTC | Jul 1, 21:30 UTC | 2h 0m |
| 2026-07-01 | ZORRO23 | OKC → OKC | Jul 1, 14:05 UTC | Jul 1, 16:00 UTC | 1h 55m |
| 2026-06-30 | ZORRO23 | - | Jun 30, 20:25 UTC | Jun 30, 22:20 UTC | 1h 55m |
| 2026-06-30 | ZORRO91 | OKC → OKC | Jun 30, 14:05 UTC | Jun 30, 15:55 UTC | 1h 50m |
| 2026-06-29 | ZORRO77 | - | Jun 29, 23:49 UTC | Jun 30, 02:00 UTC | 2h 11m |
| 2026-06-29 | ZORRO43 | - | Jun 29, 18:30 UTC | Jun 29, 20:40 UTC | 2h 10m |
| 2026-06-29 | ZORRO24 | - | Jun 29, 14:19 UTC | Jun 29, 16:04 UTC | 1h 45m |
| 2026-06-25 | ZORRO13 | - | Jun 25, 14:29 UTC | Jun 25, 16:20 UTC | 1h 50m |
| 2026-06-24 | ZORRO19 | OKC → OKC | Jun 24, 02:00 UTC | Jun 24, 04:10 UTC | 2h 10m |
| 2026-06-17 | ZORRO77 | - | Jun 17, 21:00 UTC | Jun 17, 22:55 UTC | 1h 55m |
| 2026-06-17 | ZORRO43 | - | Jun 17, 02:55 UTC | Jun 17, 04:05 UTC | 1h 10m |
| 2026-06-16 | ZORRO43 | - | Jun 16, 20:55 UTC | Jun 16, 23:10 UTC | 2h 15m |
| 2026-06-16 | ZORRO75 | OKC → OKC | Jun 16, 14:45 UTC | Jun 16, 16:35 UTC | 1h 50m |
| 2026-06-15 | ZORRO66 | OKC → OKC | Jun 15, 15:10 UTC | Jun 15, 17:15 UTC | 2h 5m |
| 2026-06-10 | ZORRO91 | OKC → OKC | Jun 10, 21:50 UTC | Jun 10, 23:50 UTC | 2h 0m |
| 2026-06-10 | ZORRO91 | OKC → OKC | Jun 10, 16:50 UTC | Jun 10, 18:50 UTC | 2h 0m |
| 2026-06-08 | ZORRO23 | OKC → OKC | Jun 8, 22:30 UTC | Jun 8, 23:30 UTC | 1h 0m |
| 2026-06-04 | ZORRO77 | OKC → OKC | Jun 4, 20:45 UTC | Jun 4, 22:40 UTC | 1h 55m |
| 2026-06-01 | ZORRO91 | - | Jun 1, 21:10 UTC | Jun 1, 22:55 UTC | 1h 45m |
| 2026-05-29 | ZORRO28 | OKC → OKC | May 29, 01:35 UTC | May 29, 03:40 UTC | 2h 5m |
| 2026-05-14 | ZORRO21 | - | May 14, 16:20 UTC | May 14, 18:15 UTC | 1h 55m |
| 2026-05-14 | ZORRO34 | - | May 14, 02:25 UTC | May 14, 03:05 UTC | 40m |
| 2026-05-14 | ZORRO34 | - | May 14, 01:15 UTC | May 14, 01:50 UTC | 35m |
| 2026-05-12 | ZORRO66 | - | May 12, 15:45 UTC | May 12, 17:40 UTC | 1h 55m |
| 2026-05-08 | ZORRO20 | - | May 8, 18:45 UTC | May 8, 19:05 UTC | 20m |
| 2026-05-08 | ZORRO20 | - | May 8, 18:00 UTC | May 8, 18:10 UTC | 10m |
| 2026-05-08 | ZORRO20 | - | May 8, 14:20 UTC | May 8, 16:45 UTC | 2h 25m |
| 2026-05-05 | ZORRO28 | OKC → OKC | May 5, 00:55 UTC | May 5, 02:55 UTC | 2h 0m |
| 2026-05-04 | ZORRO52 | OKC → OKC | May 4, 16:45 UTC | May 4, 18:45 UTC | 2h 1m |
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 AF3B60 frequently asked
What is Mode-S code AF3B60?
AF3B60 is an ICAO 24-bit transponder address.
Is AF3B60 broadcasting right now?
No active broadcast right now. Last signal was 1h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex AF3B60, octal 53635540, decimal 11,484,000.