sensors Mode-S transponder
AF4EE8
ICAO 24-bit transponder address
- Hex
- AF4EE8
- Octal
- 53647350
- Decimal
- 11,489,000
No current signal · last broadcast 19d ago
- Flights observed
- 48
- Distinct callsigns
- 20
- Country
- -
- Last broadcast
- 19d ago
Last known position
Callsign history 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| JAKAL36 | - | 8 | 2026-04-17 |
| ZORRO21 | - | 4 | 2026-05-07 |
| JAKAL20 | - | 4 | 2026-06-26 |
| ZORRO77 | - | 2 | 2026-07-23 |
| ZORRO75 | - | 2 | 2026-07-07 |
| ZORRO47 | - | 2 | 2026-07-08 |
| ZORRO36 | - | 2 | 2026-05-26 |
| ZORRO34 | - | 2 | 2026-05-29 |
| ZORRO24 | - | 2 | 2026-07-24 |
| ZORRO20 | - | 2 | 2026-05-27 |
| JAKAL03 | - | 2 | 2026-06-30 |
| ZORRP77 | - | 1 | 2026-06-08 |
| ZORRO91 | - | 1 | 2026-07-08 |
| ZORRO76 | - | 1 | 2026-05-11 |
| ZORRO67 | - | 1 | 2026-07-07 |
| ZORRO66 | - | 1 | 2026-06-16 |
| ZORRO65 | - | 1 | 2026-05-29 |
| ZORRO55 | - | 1 | 2026-06-03 |
| ZORRO52 | - | 1 | 2026-05-12 |
| ZORRO44 | - | 1 | 2026-07-23 |
Recent flights last 48
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-24 | ZORRO24 | - | Jul 24, 18:50 UTC | Jul 24, 19:10 UTC | 20m |
| 2026-07-24 | ZORRO24 | - | Jul 24, 14:20 UTC | Jul 24, 17:15 UTC | 2h 55m |
| 2026-07-23 | ZORRO77 | - | Jul 23, 20:45 UTC | Jul 23, 23:00 UTC | 2h 15m |
| 2026-07-23 | ZORRO44 | OKC → OKC | Jul 23, 13:50 UTC | Jul 23, 15:30 UTC | 1h 40m |
| 2026-07-22 | ZORRO40 | - | Jul 22, 21:20 UTC | Jul 22, 23:00 UTC | 1h 40m |
| 2026-07-10 | ZORRO41 | - | Jul 10, 15:25 UTC | Jul 10, 17:25 UTC | 2h 0m |
| 2026-07-09 | ZORRO42 | OKC → OKC | Jul 9, 21:25 UTC | Jul 9, 23:25 UTC | 2h 0m |
| 2026-07-08 | ZORRO91 | OKC → OKC | Jul 8, 19:55 UTC | Jul 8, 22:00 UTC | 2h 5m |
| 2026-07-08 | ZORRO47 | OKC → OKC | Jul 8, 14:15 UTC | Jul 8, 15:05 UTC | 50m |
| 2026-07-07 | ZORRO75 | OKC → OKC | Jul 7, 21:35 UTC | Jul 7, 23:35 UTC | 2h 0m |
| 2026-07-07 | ZORRO67 | OKC → OKC | Jul 7, 14:05 UTC | Jul 7, 16:05 UTC | 2h 0m |
| 2026-07-02 | ZORRO43 | - | Jul 2, 19:15 UTC | Jul 2, 21:05 UTC | 1h 50m |
| 2026-07-01 | ZORRO39 | - | Jul 1, 17:40 UTC | Jul 1, 19:30 UTC | 1h 50m |
| 2026-06-30 | JAKAL03 | - | Jun 30, 18:50 UTC | Jun 30, 19:30 UTC | 40m |
| 2026-06-29 | JAKAL03 | - | Jun 29, 15:04 UTC | Jun 29, 16:10 UTC | 1h 5m |
| 2026-06-26 | JAKAL20 | - | Jun 26, 16:30 UTC | Jun 26, 17:09 UTC | 40m |
| 2026-06-19 | JAKAL20 | - | Jun 19, 00:24 UTC | Jun 19, 00:55 UTC | 30m |
| 2026-06-16 | ZORRO66 | OKC → OKC | Jun 16, 17:40 UTC | Jun 16, 18:29 UTC | 50m |
| 2026-06-08 | ZORRP77 | - | Jun 8, 21:15 UTC | Jun 8, 23:10 UTC | 1h 55m |
| 2026-06-08 | ZORRO75 | - | Jun 8, 16:00 UTC | Jun 8, 18:05 UTC | 2h 5m |
| 2026-06-07 | JAKAL20 | - | Jun 7, 00:25 UTC | Jun 7, 00:55 UTC | 30m |
| 2026-06-05 | JAKAL20 | - | Jun 5, 18:55 UTC | Jun 5, 19:40 UTC | 45m |
| 2026-06-03 | ZORRO55 | - | Jun 3, 17:45 UTC | Jun 3, 19:30 UTC | 1h 45m |
| 2026-05-29 | ZORRO34 | - | May 29, 16:45 UTC | May 29, 18:40 UTC | 1h 55m |
| 2026-05-29 | ZORRO65 | OKC → OKC | May 29, 00:50 UTC | May 29, 02:50 UTC | 2h 0m |
| 2026-05-27 | ZORRO20 | - | May 27, 17:30 UTC | May 27, 18:50 UTC | 1h 20m |
| 2026-05-26 | ZORRO36 | - | May 26, 16:59 UTC | May 26, 18:55 UTC | 1h 55m |
| 2026-05-13 | ZORRO47 | - | May 13, 01:25 UTC | May 13, 03:25 UTC | 2h 0m |
| 2026-05-12 | ZORRO34 | OKC → OKC | May 12, 21:01 UTC | May 12, 23:05 UTC | 2h 5m |
| 2026-05-12 | ZORRO33 | - | May 12, 17:20 UTC | May 12, 19:15 UTC | 1h 55m |
| 2026-05-12 | ZORRO52 | - | May 12, 02:45 UTC | May 12, 03:15 UTC | 30m |
| 2026-05-11 | ZORRO76 | - | May 11, 22:05 UTC | May 11, 22:35 UTC | 29m |
| 2026-05-11 | ZORRO20 | OKC → OKC | May 11, 17:15 UTC | May 11, 19:00 UTC | 1h 45m |
| 2026-05-08 | ZORRO77 | - | May 8, 13:50 UTC | May 8, 16:10 UTC | 2h 20m |
| 2026-05-07 | ZORRO21 | OKC → OKC | May 7, 02:05 UTC | May 7, 03:20 UTC | 1h 15m |
| 2026-05-06 | ZORRO36 | OKC → OKC | May 6, 01:35 UTC | May 6, 02:20 UTC | 45m |
| 2026-05-01 | ZORRO21 | OKC → OKC | May 1, 22:25 UTC | May 1, 22:50 UTC | 25m |
| 2026-04-29 | ZORRO21 | - | Apr 29, 02:50 UTC | Apr 29, 03:19 UTC | 30m |
| 2026-04-29 | ZORRO21 | - | Apr 29, 01:20 UTC | Apr 29, 01:45 UTC | 25m |
| 2026-04-28 | ZORRO17 | OKC → OKC | Apr 28, 01:25 UTC | Apr 28, 01:30 UTC | 5m |
| 2026-04-17 | JAKAL36 | - | Apr 17, 21:25 UTC | Apr 17, 21:35 UTC | 10m |
| 2026-04-17 | JAKAL36 | - | Apr 17, 20:40 UTC | Apr 17, 21:20 UTC | 40m |
| 2026-04-17 | JAKAL36 | - | Apr 17, 19:25 UTC | Apr 17, 20:05 UTC | 40m |
| 2026-04-17 | JAKAL36 | - | Apr 17, 17:40 UTC | Apr 17, 19:05 UTC | 1h 25m |
| 2026-04-16 | JAKAL36 | - | Apr 16, 18:00 UTC | Apr 16, 18:25 UTC | 25m |
| 2026-04-15 | JAKAL36 | - | Apr 15, 19:55 UTC | Apr 15, 20:35 UTC | 40m |
| 2026-04-15 | JAKAL36 | - | Apr 15, 19:05 UTC | Apr 15, 19:50 UTC | 45m |
| 2026-04-15 | JAKAL36 | - | Apr 15, 18:00 UTC | Apr 15, 19:00 UTC | 1h 0m |
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 AF4EE8 frequently asked
What is Mode-S code AF4EE8?
AF4EE8 is an ICAO 24-bit transponder address.
Is AF4EE8 broadcasting right now?
No active broadcast right now. Last signal was 19d ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex AF4EE8, octal 53647350, decimal 11,489,000.