sensors Mode-S transponder
AF3BE4
ICAO 24-bit transponder address
- Hex
- AF3BE4
- Octal
- 53635744
- Decimal
- 11,484,132
No current signal · last broadcast 16d ago
- Flights observed
- 61
- Distinct callsigns
- 1
- Country
- -
- Last broadcast
- 16d ago
Last known position
Callsign history 1 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| C6067 | - | 61 | 2026-06-04 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-04 | C6067 | - | Jun 4, 17:10 UTC | Jun 4, 17:50 UTC | 40m |
| 2026-06-03 | C6067 | CDV → ADQ | Jun 3, 18:20 UTC | Jun 3, 20:50 UTC | 2h 30m |
| 2026-06-01 | C6067 | CDV → CDV | Jun 1, 08:05 UTC | Jun 1, 09:30 UTC | 1h 25m |
| 2026-06-01 | C6067 | CDV → CDV | Jun 1, 05:00 UTC | Jun 1, 05:15 UTC | 15m |
| 2026-05-30 | C6067 | ANC → CDV | May 30, 23:20 UTC | May 31, 00:50 UTC | 1h 30m |
| 2026-05-30 | C6067 | - | May 30, 18:35 UTC | May 30, 19:00 UTC | 25m |
| 2026-05-30 | C6067 | - | May 30, 17:10 UTC | May 30, 17:50 UTC | 40m |
| 2026-05-29 | C6067 | - | May 29, 19:55 UTC | May 29, 23:20 UTC | 3h 25m |
| 2026-05-29 | C6067 | CDV → CDV | May 29, 19:10 UTC | May 29, 19:30 UTC | 20m |
| 2026-05-28 | C6067 | - | May 28, 20:45 UTC | May 28, 20:55 UTC | 10m |
| 2026-05-28 | C6067 | - | May 28, 18:00 UTC | May 28, 18:35 UTC | 35m |
| 2026-05-27 | C6067 | CDV → CDV | May 27, 20:10 UTC | May 27, 20:35 UTC | 25m |
| 2026-05-27 | C6067 | VDZ → CDV | May 27, 18:40 UTC | May 27, 19:30 UTC | 50m |
| 2026-05-27 | C6067 | CKU → VDZ | May 27, 17:45 UTC | May 27, 18:25 UTC | 40m |
| 2026-05-25 | C6067 | - | May 25, 19:54 UTC | May 25, 20:15 UTC | 20m |
| 2026-05-25 | C6067 | - | May 25, 17:10 UTC | May 25, 18:00 UTC | 50m |
| 2026-05-24 | C6067 | - | May 24, 21:30 UTC | May 24, 21:45 UTC | 15m |
| 2026-05-24 | C6067 | - | May 24, 17:55 UTC | May 24, 18:25 UTC | 30m |
| 2026-05-24 | C6067 | - | May 24, 00:15 UTC | May 24, 00:35 UTC | 20m |
| 2026-05-23 | C6067 | - | May 23, 22:50 UTC | May 23, 23:30 UTC | 40m |
| 2026-05-23 | C6067 | - | May 23, 17:45 UTC | May 23, 18:40 UTC | 56m |
| 2026-05-19 | C6067 | - | May 19, 20:05 UTC | May 19, 20:25 UTC | 20m |
| 2026-05-19 | C6067 | - | May 19, 17:30 UTC | May 19, 17:55 UTC | 25m |
| 2026-05-18 | C6067 | VDZ → CDV | May 18, 21:20 UTC | May 18, 22:25 UTC | 1h 5m |
| 2026-05-18 | C6067 | - | May 18, 17:15 UTC | May 18, 17:50 UTC | 35m |
| 2026-05-18 | C6067 | - | May 18, 00:00 UTC | May 18, 00:45 UTC | 45m |
| 2026-05-17 | C6067 | - | May 17, 22:40 UTC | May 17, 23:00 UTC | 20m |
| 2026-05-17 | C6067 | - | May 17, 08:00 UTC | May 17, 08:10 UTC | 10m |
| 2026-05-17 | C6067 | - | May 17, 00:40 UTC | May 17, 01:05 UTC | 25m |
| 2026-05-13 | C6067 | - | May 13, 20:50 UTC | May 13, 21:00 UTC | 10m |
| 2026-05-13 | C6067 | - | May 13, 17:40 UTC | May 13, 17:50 UTC | 10m |
| 2026-05-12 | C6067 | - | May 12, 21:10 UTC | May 12, 21:20 UTC | 10m |
| 2026-05-12 | C6067 | - | May 12, 20:15 UTC | May 12, 21:05 UTC | 50m |
| 2026-05-11 | C6067 | - | May 11, 18:00 UTC | May 11, 20:10 UTC | 2h 10m |
| 2026-05-08 | C6067 | ADQ → ADQ | May 8, 18:55 UTC | May 8, 19:15 UTC | 20m |
| 2026-05-05 | C6067 | - | May 5, 18:50 UTC | May 5, 19:05 UTC | 15m |
| 2026-05-05 | C6067 | - | May 5, 16:45 UTC | May 5, 17:40 UTC | 55m |
| 2026-05-04 | C6067 | - | May 4, 19:00 UTC | May 4, 19:15 UTC | 15m |
| 2026-05-03 | C6067 | - | May 3, 18:20 UTC | May 3, 18:55 UTC | 35m |
| 2026-05-02 | C6067 | - | May 2, 15:40 UTC | May 2, 17:05 UTC | 1h 25m |
| 2026-05-01 | C6067 | - | May 1, 19:15 UTC | May 1, 19:55 UTC | 40m |
| 2026-05-01 | C6067 | - | May 1, 17:35 UTC | May 1, 18:25 UTC | 50m |
| 2026-04-30 | C6067 | - | Apr 30, 18:25 UTC | Apr 30, 18:40 UTC | 15m |
| 2026-04-30 | C6067 | - | Apr 30, 17:10 UTC | Apr 30, 17:45 UTC | 35m |
| 2026-04-30 | C6067 | - | Apr 30, 14:30 UTC | Apr 30, 15:10 UTC | 40m |
| 2026-04-30 | C6067 | - | Apr 30, 12:45 UTC | Apr 30, 13:45 UTC | 1h 0m |
| 2026-04-29 | C6067 | - | Apr 29, 18:10 UTC | Apr 29, 19:25 UTC | 1h 15m |
| 2026-04-29 | C6067 | - | Apr 29, 16:50 UTC | Apr 29, 17:10 UTC | 20m |
| 2026-04-29 | C6067 | - | Apr 29, 12:40 UTC | Apr 29, 15:50 UTC | 3h 10m |
| 2026-04-27 | C6067 | - | Apr 27, 23:45 UTC | Apr 28, 02:45 UTC | 3h 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 AF3BE4 frequently asked
What is Mode-S code AF3BE4?
AF3BE4 is an ICAO 24-bit transponder address.
Is AF3BE4 broadcasting right now?
No active broadcast right now. Last signal was 16d ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex AF3BE4, octal 53635744, decimal 11,484,132.
What flights does AF3BE4 operate?
Mode-S AF3BE4 has broadcast 1 distinct callsign, including C6067.