sensors Mode-S transponder
8964AF
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-EVA · AIRBUS A-380-800
- Hex
- 8964AF
- Octal
- 42262257
- Decimal
- 9,004,207
- Country
- AE
- Tail
- A6-EVA
- Type
- A388
- Flights observed
- 54
- Distinct callsigns
- 17
- Country
- AE
- Last broadcast
- 12h ago
Last known position
Country allocation
The ICAO 24-bit address 8964AF 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 17 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| UAE5GU | Emirates | 9 | 2026-05-16 |
| UAE58Q | Emirates | 9 | 2026-05-16 |
| UAE375 | Emirates | 8 | 2026-05-30 |
| UAE374 | Emirates | 5 | 2026-05-29 |
| UAE9YT | Emirates | 3 | 2026-05-24 |
| UAE369 | Emirates | 3 | 2026-05-09 |
| UAE366 | Emirates | 3 | 2026-05-13 |
| UAE7Q | Emirates | 2 | 2026-04-13 |
| UAE39 | Emirates | 2 | 2026-04-19 |
| UAE367 | Emirates | 2 | 2026-05-13 |
| UAE15K | - | 2 | 2026-04-13 |
| UAE98P | Emirates | 1 | 2026-04-19 |
| UAE804 | - | 1 | 2026-04-12 |
| UAE2552 | Emirates | 1 | 2026-05-23 |
| UAE2503 | Emirates | 1 | 2026-04-29 |
| UAE20 | Emirates | 1 | 2026-04-27 |
| UAE19 | Emirates | 1 | 2026-04-27 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | UAE375 | BKK → DXB | May 30, 08:35 UTC | May 30, 08:55 UTC | 20m |
| 2026-05-30 | UAE375 | BKK → DXB | May 30, 03:05 UTC | May 30, 07:20 UTC | 4h 15m |
| 2026-05-29 | UAE374 | DXB → BKK | May 29, 20:25 UTC | May 30, 00:45 UTC | 4h 20m |
| 2026-05-29 | UAE375 | BKK → DXB | May 29, 03:00 UTC | May 29, 09:05 UTC | 6h 5m |
| 2026-05-28 | UAE374 | DXB → BKK | May 28, 20:25 UTC | May 29, 00:50 UTC | 4h 25m |
| 2026-05-27 | UAE375 | BKK → DXB | May 27, 08:20 UTC | May 27, 08:45 UTC | 25m |
| 2026-05-27 | UAE375 | BKK → DXB | May 27, 02:49 UTC | May 27, 07:20 UTC | 4h 31m |
| 2026-05-26 | UAE374 | DXB → BKK | May 26, 19:15 UTC | May 27, 00:39 UTC | 5h 25m |
| 2026-05-26 | UAE375 | BKK → DXB | May 26, 08:39 UTC | May 26, 08:59 UTC | 20m |
| 2026-05-26 | UAE375 | BKK → DXB | May 26, 03:09 UTC | May 26, 07:34 UTC | 4h 25m |
| 2026-05-25 | UAE374 | DXB → BKK | May 25, 20:24 UTC | May 26, 00:54 UTC | 4h 30m |
| 2026-05-24 | UAE9YT | MRU → DXB | May 24, 23:25 UTC | May 24, 23:46 UTC | 21m |
| 2026-05-23 | UAE2552 | DWC → DXB | May 23, 04:25 UTC | May 23, 04:40 UTC | 15m |
| 2026-05-16 | UAE5GU | DUS → DXB | May 16, 14:16 UTC | May 16, 20:20 UTC | 6h 5m |
| 2026-05-16 | UAE58Q | DXB → DUS | May 16, 05:05 UTC | May 16, 11:46 UTC | 6h 41m |
| 2026-05-14 | UAE9YT | MRU → DXB | May 14, 07:05 UTC | May 15, 00:10 UTC | 17h 5m |
| 2026-05-13 | UAE367 | TPE → DXB | May 13, 15:10 UTC | May 14, 00:10 UTC | 9h 0m |
| 2026-05-13 | UAE366 | DXB → TPE | May 13, 01:45 UTC | May 13, 07:55 UTC | 6h 10m |
| 2026-05-11 | UAE5GU | DUS → DXB | May 11, 14:05 UTC | May 11, 20:35 UTC | 6h 31m |
| 2026-05-11 | UAE58Q | DXB → DUS | May 11, 03:45 UTC | May 11, 10:45 UTC | 7h 0m |
| 2026-05-09 | UAE369 | DPS → DXB | May 9, 02:55 UTC | May 9, 21:00 UTC | 18h 5m |
| 2026-05-08 | UAE5GU | DUS → DXB | May 8, 14:45 UTC | May 8, 21:30 UTC | 6h 45m |
| 2026-05-08 | UAE58Q | DXB → DUS | May 8, 04:34 UTC | May 8, 12:00 UTC | 7h 25m |
| 2026-05-07 | UAE5GU | DUS → DXB | May 7, 15:20 UTC | May 7, 21:45 UTC | 6h 25m |
| 2026-05-07 | UAE58Q | DXB → DUS | May 7, 05:00 UTC | May 7, 12:20 UTC | 7h 20m |
| 2026-05-06 | UAE367 | TPE → DXB | May 6, 15:10 UTC | May 6, 23:55 UTC | 8h 45m |
| 2026-05-06 | UAE366 | DXB → TPE | May 6, 08:15 UTC | May 6, 08:40 UTC | 25m |
| 2026-05-06 | UAE366 | DXB → TPE | May 6, 01:01 UTC | May 6, 07:45 UTC | 6h 45m |
| 2026-04-29 | UAE2503 | DXB → LHR | Apr 29, 16:25 UTC | Apr 29, 16:45 UTC | 20m |
| 2026-04-29 | UAE375 | BKK → DXB | Apr 29, 02:55 UTC | Apr 29, 09:05 UTC | 6h 11m |
| 2026-04-28 | UAE374 | DXB → BKK | Apr 28, 19:10 UTC | Apr 29, 00:34 UTC | 5h 25m |
| 2026-04-27 | UAE20 | MAN → DXB | Apr 27, 20:50 UTC | Apr 28, 03:55 UTC | 7h 5m |
| 2026-04-27 | UAE19 | DXB → MAN | Apr 27, 09:45 UTC | Apr 27, 18:35 UTC | 8h 50m |
| 2026-04-26 | UAE5GU | DUS → DXB | Apr 26, 13:45 UTC | Apr 26, 20:25 UTC | 6h 40m |
| 2026-04-26 | UAE58Q | DXB → DUS | Apr 26, 03:40 UTC | Apr 26, 11:30 UTC | 7h 50m |
| 2026-04-23 | UAE9YT | MRU → DXB | Apr 23, 07:01 UTC | Apr 24, 00:05 UTC | 17h 4m |
| 2026-04-19 | UAE98P | BHX → DXB | Apr 19, 15:10 UTC | Apr 19, 21:55 UTC | 6h 45m |
| 2026-04-19 | UAE39 | DXB → BHX | Apr 19, 05:15 UTC | Apr 19, 12:50 UTC | 7h 35m |
| 2026-04-19 | UAE39 | DXB → BHX | Apr 19, 04:25 UTC | Apr 19, 04:45 UTC | 20m |
| 2026-04-18 | UAE369 | DPS → DXB | Apr 18, 06:05 UTC | Apr 18, 20:45 UTC | 14h 40m |
| 2026-04-18 | UAE369 | DPS → DXB | Apr 18, 00:05 UTC | Apr 18, 20:45 UTC | 20h 40m |
| 2026-04-15 | UAE5GU | DUS → DXB | Apr 15, 23:10 UTC | Apr 15, 23:30 UTC | 20m |
| 2026-04-15 | UAE5GU | DUS → DXB | Apr 15, 22:30 UTC | Apr 15, 23:00 UTC | 30m |
| 2026-04-15 | UAE5GU | DUS → DXB | Apr 15, 19:05 UTC | Apr 15, 20:45 UTC | 1h 40m |
| 2026-04-15 | UAE5GU | DUS → DXB | Apr 15, 17:05 UTC | Apr 15, 19:00 UTC | 1h 55m |
| 2026-04-15 | UAE58Q | DXB → DUS | Apr 15, 13:01 UTC | Apr 15, 14:50 UTC | 1h 49m |
| 2026-04-15 | UAE58Q | DXB → DUS | Apr 15, 11:00 UTC | Apr 15, 12:55 UTC | 1h 55m |
| 2026-04-15 | UAE58Q | DXB → DUS | Apr 15, 10:45 UTC | Apr 15, 10:55 UTC | 10m |
| 2026-04-15 | UAE58Q | DXB → DUS | Apr 15, 07:25 UTC | Apr 15, 08:25 UTC | 1h 0m |
| 2026-04-13 | UAE7Q | KUL → DXB | Apr 13, 21:25 UTC | Apr 13, 22:15 UTC | 50m |
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-EVA page for operator, model, and routing details .