sensors Mode-S transponder
8965EE
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-AUE · AIRBUS A-320
- Hex
- 8965EE
- Octal
- 42262756
- Decimal
- 9,004,526
- Country
- AE
- Tail
- A6-AUE
- Type
- A320
- Flights observed
- 125
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 15d ago
Last known position
Country allocation
The ICAO 24-bit address 8965EE falls within the block assigned to United Arab Emirates (AE) by ICAO Annex 10, Volume III. Every aircraft registered in United Arab Emirates receives a permanent address from this block at the time of registration; the address stays with the airframe even if the aircraft is re-registered to a different operator within the country.
Callsign history 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| ADY425 | Aerodyne | 17 | 2026-05-13 |
| ADY424 | Aerodyne | 15 | 2026-05-07 |
| ADY505 | Aerodyne | 11 | 2026-05-12 |
| ADY504 | Aerodyne | 7 | 2026-05-02 |
| ADY134 | Aerodyne | 7 | 2026-05-03 |
| ADY133 | Aerodyne | 7 | 2026-05-02 |
| ADY432 | Aerodyne | 5 | 2026-05-14 |
| ADY431 | Aerodyne | 4 | 2026-05-14 |
| ADY128 | Aerodyne | 4 | 2026-05-10 |
| ADY405 | Aerodyne | 3 | 2026-05-11 |
| ADY383 | Aerodyne | 3 | 2026-04-26 |
| ADY204 | Aerodyne | 3 | 2026-04-20 |
| ADY203 | Aerodyne | 3 | 2026-04-19 |
| ADY142 | Aerodyne | 3 | 2026-04-26 |
| ADY127 | Aerodyne | 3 | 2026-05-09 |
| ADY126 | Aerodyne | 3 | 2026-04-29 |
| ADY125 | Aerodyne | 3 | 2026-04-29 |
| ADY709 | Aerodyne | 2 | 2026-04-17 |
| ADY708 | Aerodyne | 2 | 2026-04-17 |
| ADY404 | Aerodyne | 2 | 2026-04-16 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-14 | ADY432 | CAI → AUH | May 14, 18:45 UTC | May 14, 21:20 UTC | 2h 35m |
| 2026-05-14 | ADY431 | AUH → CAI | May 14, 14:55 UTC | May 14, 17:05 UTC | 2h 10m |
| 2026-05-14 | ADY335 | AUH → MUX | May 14, 03:55 UTC | May 14, 04:05 UTC | 10m |
| 2026-05-13 | ADY432 | CAI → AUH | May 13, 18:45 UTC | May 13, 21:25 UTC | 2h 40m |
| 2026-05-13 | ADY425 | CAI → AUH | May 13, 00:55 UTC | May 13, 14:51 UTC | 13h 55m |
| 2026-05-12 | ADY505 | DAM → AUH | May 12, 11:05 UTC | May 12, 23:20 UTC | 12h 15m |
| 2026-05-11 | ADY405 | HBE → AUH | May 11, 09:25 UTC | May 11, 12:30 UTC | 3h 5m |
| 2026-05-10 | ADY128 | COK → AUH | May 10, 23:35 UTC | May 10, 23:50 UTC | 15m |
| 2026-05-10 | ADY033 | AMM → AUH | May 10, 07:04 UTC | May 10, 22:30 UTC | 15h 25m |
| 2026-05-10 | ADY128 | COK → AUH | May 10, 00:09 UTC | May 10, 00:20 UTC | 10m |
| 2026-05-09 | ADY127 | AUH → COK | May 9, 22:15 UTC | May 9, 22:25 UTC | 10m |
| 2026-05-09 | ADY425 | CAI → AUH | May 9, 00:55 UTC | May 9, 07:20 UTC | 6h 25m |
| 2026-05-08 | ADY505 | DAM → AUH | May 8, 03:35 UTC | May 8, 23:25 UTC | 19h 50m |
| 2026-05-08 | ADY505 | DAM → AUH | May 8, 03:04 UTC | May 8, 23:25 UTC | 20h 20m |
| 2026-05-08 | ADY425 | CAI → AUH | May 8, 00:54 UTC | May 8, 23:25 UTC | 22h 30m |
| 2026-05-07 | ADY424 | AUH → CAI | May 7, 15:25 UTC | May 7, 23:34 UTC | 8h 10m |
| 2026-05-07 | ADY425 | CAI → AUH | May 7, 02:10 UTC | May 7, 04:45 UTC | 2h 35m |
| 2026-05-07 | ADY424 | AUH → CAI | May 7, 00:10 UTC | May 7, 00:25 UTC | 15m |
| 2026-05-06 | ADY425 | CAI → AUH | May 6, 01:50 UTC | May 6, 04:55 UTC | 3h 4m |
| 2026-05-05 | ADY424 | AUH → CAI | May 5, 07:20 UTC | May 6, 00:10 UTC | 16h 50m |
| 2026-05-04 | ADY432 | CAI → AUH | May 4, 19:00 UTC | May 5, 11:50 UTC | 16h 50m |
| 2026-05-04 | ADY431 | AUH → CAI | May 4, 13:50 UTC | May 4, 17:10 UTC | 3h 20m |
| 2026-05-04 | ADY044 | KTM → AUH | May 4, 05:10 UTC | May 4, 08:50 UTC | 3h 40m |
| 2026-05-04 | ADY044 | KTM → AUH | May 4, 04:29 UTC | May 4, 04:39 UTC | 10m |
| 2026-05-03 | ADY043 | AUH → KTM | May 3, 23:30 UTC | May 4, 03:09 UTC | 3h 40m |
| 2026-05-03 | ADY432 | CAI → AUH | May 3, 18:45 UTC | May 3, 21:20 UTC | 2h 35m |
| 2026-05-03 | ADY431 | AUH → CAI | May 3, 13:30 UTC | May 3, 16:55 UTC | 3h 25m |
| 2026-05-03 | ADY134 | TRV → AUH | May 3, 03:20 UTC | May 3, 03:30 UTC | 9m |
| 2026-05-03 | ADY134 | TRV → AUH | May 3, 00:01 UTC | May 3, 00:10 UTC | 10m |
| 2026-05-02 | ADY133 | AUH → TRV | May 2, 22:25 UTC | May 2, 22:45 UTC | 20m |
| 2026-05-02 | ADY505 | DAM → AUH | May 2, 14:00 UTC | May 2, 14:45 UTC | 45m |
| 2026-05-02 | ADY505 | DAM → AUH | May 2, 10:55 UTC | May 2, 11:05 UTC | 10m |
| 2026-05-02 | ADY504 | AUH → DAM | May 2, 06:25 UTC | May 2, 07:15 UTC | 50m |
| 2026-05-02 | ADY128 | COK → AUH | May 2, 02:40 UTC | May 2, 03:05 UTC | 25m |
| 2026-05-01 | ADY128 | COK → AUH | May 1, 23:30 UTC | May 1, 23:45 UTC | 15m |
| 2026-05-01 | ADY127 | AUH → COK | May 1, 22:15 UTC | May 1, 22:25 UTC | 10m |
| 2026-05-01 | ADY127 | AUH → COK | May 1, 19:05 UTC | May 1, 19:30 UTC | 25m |
| 2026-05-01 | ADY505 | DAM → AUH | May 1, 12:55 UTC | May 1, 15:10 UTC | 2h 15m |
| 2026-05-01 | ADY505 | DAM → AUH | May 1, 11:25 UTC | May 1, 11:35 UTC | 10m |
| 2026-05-01 | ADY504 | AUH → DAM | May 1, 06:45 UTC | May 1, 07:45 UTC | 1h 0m |
| 2026-05-01 | ADY425 | CAI → AUH | May 1, 01:25 UTC | May 1, 04:20 UTC | 2h 55m |
| 2026-04-30 | ADY424 | AUH → CAI | Apr 30, 20:15 UTC | May 1, 00:00 UTC | 3h 45m |
| 2026-04-30 | ADY505 | DAM → AUH | Apr 30, 14:30 UTC | Apr 30, 14:55 UTC | 25m |
| 2026-04-30 | ADY505 | DAM → AUH | Apr 30, 11:15 UTC | Apr 30, 11:25 UTC | 10m |
| 2026-04-30 | ADY504 | AUH → DAM | Apr 30, 06:45 UTC | Apr 30, 07:40 UTC | 55m |
| 2026-04-29 | ADY111 | AUH → AMD | Apr 29, 21:25 UTC | Apr 30, 03:05 UTC | 5h 39m |
| 2026-04-29 | ADY126 | COK → AUH | Apr 29, 19:30 UTC | Apr 29, 19:45 UTC | 15m |
| 2026-04-29 | ADY126 | COK → AUH | Apr 29, 16:20 UTC | Apr 29, 16:35 UTC | 15m |
| 2026-04-29 | ADY125 | AUH → COK | Apr 29, 11:55 UTC | Apr 29, 12:15 UTC | 20m |
| 2026-04-29 | ADY425 | CAI → AUH | Apr 29, 01:15 UTC | Apr 29, 04:10 UTC | 2h 55m |
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.
Prefer a tail-number view? See the A6-AUE page for operator, model, and routing details .