sensors Mode-S transponder
AE6305
ICAO 24-bit transponder address
- Hex
- AE6305
- Octal
- 53461405
- Decimal
- 11,428,613
No current signal · last broadcast 1d ago
- Flights observed
- 82
- Distinct callsigns
- 4
- Country
- -
- Last broadcast
- 1d ago
Last known position
Callsign history 4 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-11 | BLZR294 | NQI → NQI | Jun 11, 19:55 UTC | Jun 11, 20:35 UTC | 40m |
| 2026-06-11 | HAWK294 | NQI → NQI | Jun 11, 16:00 UTC | Jun 11, 16:55 UTC | 55m |
| 2026-06-10 | HAWK294 | NQI → NQI | Jun 10, 21:50 UTC | Jun 10, 22:55 UTC | 1h 5m |
| 2026-06-10 | HAWK294 | - | Jun 10, 18:40 UTC | Jun 10, 19:45 UTC | 1h 5m |
| 2026-06-10 | HAWK294 | NQI → NQI | Jun 10, 15:40 UTC | Jun 10, 16:30 UTC | 50m |
| 2026-06-10 | HAWK294 | NQI → NQI | Jun 10, 13:05 UTC | Jun 10, 14:15 UTC | 1h 10m |
| 2026-06-09 | HAWK294 | NQI → NQI | Jun 9, 22:35 UTC | Jun 9, 23:20 UTC | 45m |
| 2026-06-09 | HAWK294 | - | Jun 9, 19:25 UTC | Jun 9, 20:10 UTC | 45m |
| 2026-06-09 | HAWK294 | - | Jun 9, 16:45 UTC | Jun 9, 17:00 UTC | 15m |
| 2026-06-09 | HAWK294 | - | Jun 9, 15:45 UTC | Jun 9, 15:50 UTC | 5m |
| 2026-06-08 | HAWK294 | - | Jun 8, 22:25 UTC | Jun 8, 23:10 UTC | 45m |
| 2026-06-08 | HAWK294 | - | Jun 8, 21:10 UTC | Jun 8, 21:50 UTC | 40m |
| 2026-06-08 | BLZR294 | NQI → NQI | Jun 8, 14:35 UTC | Jun 8, 15:45 UTC | 1h 10m |
| 2026-06-07 | SPIN294 | - | Jun 7, 16:45 UTC | Jun 7, 17:35 UTC | 50m |
| 2026-06-05 | HAWK294 | - | Jun 5, 16:45 UTC | Jun 5, 17:35 UTC | 50m |
| 2026-06-04 | HAWK294 | NQI → NQI | Jun 4, 21:40 UTC | Jun 4, 22:30 UTC | 50m |
| 2026-06-04 | HAWK294 | - | Jun 4, 19:35 UTC | Jun 4, 19:45 UTC | 10m |
| 2026-06-04 | HAWK294 | - | Jun 4, 02:35 UTC | Jun 4, 03:00 UTC | 25m |
| 2026-06-04 | HAWK294 | NQI → NQI | Jun 4, 01:25 UTC | Jun 4, 01:55 UTC | 30m |
| 2026-06-02 | BLZR294 | NQI → NQI | Jun 2, 18:10 UTC | Jun 2, 18:35 UTC | 25m |
| 2026-06-02 | BLZR294 | NQI → NQI | Jun 2, 14:45 UTC | Jun 2, 15:30 UTC | 45m |
| 2026-06-01 | BLZR294 | NQI → NQI | Jun 1, 21:50 UTC | Jun 1, 22:50 UTC | 1h 0m |
| 2026-06-01 | HAWK294 | - | Jun 1, 19:05 UTC | Jun 1, 19:45 UTC | 40m |
| 2026-05-29 | HAWK294 | - | May 29, 01:35 UTC | May 29, 02:50 UTC | 1h 15m |
| 2026-05-28 | BLZR294 | NQI → NQI | May 28, 16:50 UTC | May 28, 17:50 UTC | 1h 0m |
| 2026-05-27 | HAWK294 | NQI → NQI | May 27, 21:45 UTC | May 27, 22:50 UTC | 1h 5m |
| 2026-05-27 | LTHL294 | - | May 27, 01:29 UTC | May 27, 01:54 UTC | 25m |
| 2026-05-26 | BLZR294 | NQI → NQI | May 26, 14:50 UTC | May 26, 15:45 UTC | 55m |
| 2026-05-21 | BLZR294 | - | May 21, 21:15 UTC | May 21, 21:45 UTC | 30m |
| 2026-05-21 | BLZR294 | - | May 21, 19:55 UTC | May 21, 20:40 UTC | 45m |
| 2026-05-21 | HAWK294 | NQI → NQI | May 21, 17:10 UTC | May 21, 17:30 UTC | 20m |
| 2026-05-20 | HAWK294 | NQI → NQI | May 20, 19:10 UTC | May 20, 20:50 UTC | 1h 40m |
| 2026-05-20 | BLZR294 | - | May 20, 16:55 UTC | May 20, 17:40 UTC | 45m |
| 2026-05-20 | HAWK294 | NQI → NQI | May 20, 14:25 UTC | May 20, 15:25 UTC | 1h 0m |
| 2026-05-19 | BLZR294 | NQI → NQI | May 19, 20:25 UTC | May 19, 21:35 UTC | 1h 10m |
| 2026-05-19 | BLZR294 | NQI → NQI | May 19, 17:20 UTC | May 19, 18:35 UTC | 1h 15m |
| 2026-05-19 | HAWK294 | NQI → NQI | May 19, 13:05 UTC | May 19, 13:45 UTC | 40m |
| 2026-05-19 | BLZR294 | NQI → NQI | May 19, 01:25 UTC | May 19, 01:45 UTC | 20m |
| 2026-05-19 | BLZR294 | NQI → NQI | May 19, 00:05 UTC | May 19, 00:30 UTC | 25m |
| 2026-05-18 | BLZR294 | NQI → NQI | May 18, 19:45 UTC | May 18, 20:30 UTC | 45m |
| 2026-05-17 | HAWK294 | NQI → NQI | May 17, 14:30 UTC | May 17, 14:50 UTC | 20m |
| 2026-05-15 | BLZR294 | - | May 15, 15:45 UTC | May 15, 16:05 UTC | 20m |
| 2026-05-14 | BLZR294 | NQI → NQI | May 14, 16:50 UTC | May 14, 17:45 UTC | 55m |
| 2026-05-14 | BLZR294 | NQI → NQI | May 14, 02:00 UTC | May 14, 03:10 UTC | 1h 10m |
| 2026-05-13 | HAWK294 | NQI → NQI | May 13, 21:00 UTC | May 13, 22:00 UTC | 1h 0m |
| 2026-05-13 | HAWK294 | - | May 13, 14:35 UTC | May 13, 15:20 UTC | 45m |
| 2026-05-12 | HAWK294 | - | May 12, 22:31 UTC | May 12, 23:05 UTC | 35m |
| 2026-05-12 | BLZR294 | NQI → NQI | May 12, 15:55 UTC | May 12, 16:40 UTC | 45m |
| 2026-05-12 | BLZR294 | NQI → NQI | May 12, 03:00 UTC | May 12, 03:15 UTC | 15m |
| 2026-05-11 | HAWK294 | - | May 11, 21:30 UTC | May 11, 22:35 UTC | 1h 4m |
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 AE6305 frequently asked
What is Mode-S code AE6305?
AE6305 is an ICAO 24-bit transponder address.
Is AE6305 broadcasting right now?
No active broadcast right now. Last signal was 1d ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex AE6305, octal 53461405, decimal 11,428,613.