sensors Mode-S transponder
8964B4
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-EVF · AIRBUS A-380-800
- Hex
- 8964B4
- Octal
- 42262264
- Decimal
- 9,004,212
- Country
- AE
- Tail
- A6-EVF
- Type
- A388
- Flights observed
- 94
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 2h ago
Last known position
Country allocation
The ICAO 24-bit address 8964B4 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 |
|---|---|---|---|
| UAE5CL | Emirates | 16 | 2026-05-26 |
| UAE3HJ | Emirates | 14 | 2026-05-24 |
| UAE4CK | Emirates | 9 | 2026-05-08 |
| UAE6 | Emirates | 6 | 2026-05-08 |
| UAE7CN | Emirates | 5 | 2026-04-15 |
| UAE51N | Emirates | 5 | 2026-05-29 |
| UAE1 | Emirates | 5 | 2026-05-16 |
| UAE569 | Emirates | 3 | 2026-05-11 |
| UAE43P | Emirates | 3 | 2026-05-16 |
| UAE41P | Emirates | 3 | 2026-05-18 |
| UAE373 | Emirates | 3 | 2026-05-26 |
| UAE88 | Emirates | 2 | 2026-05-28 |
| UAE568 | Emirates | 2 | 2026-05-10 |
| UAE4 | Emirates | 2 | 2026-05-13 |
| UAE372 | Emirates | 2 | 2026-05-26 |
| UAE1CR | Emirates | 2 | 2026-05-14 |
| UAE9LT | Emirates | 1 | 2026-05-06 |
| UAE804 | Emirates | 1 | 2026-05-07 |
| UAE70M | Emirates | 1 | 2026-05-13 |
| UAE501 | Emirates | 1 | 2026-04-18 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | UAE51N | DXB → SFO | May 29, 09:15 UTC | May 29, 22:25 UTC | 13h 11m |
| 2026-05-28 | UAE88 | ZRH → DXB | May 28, 14:00 UTC | May 28, 20:05 UTC | 6h 5m |
| 2026-05-27 | UAE319 | NRT → DXB | May 27, 13:55 UTC | May 28, 00:25 UTC | 10h 30m |
| 2026-05-27 | UAE318 | DXB → NRT | May 27, 05:29 UTC | May 27, 08:25 UTC | 2h 56m |
| 2026-05-26 | UAE373 | BKK → DXB | May 26, 14:24 UTC | May 26, 20:15 UTC | 5h 50m |
| 2026-05-26 | UAE372 | DXB → BKK | May 26, 07:24 UTC | May 26, 12:05 UTC | 4h 40m |
| 2026-05-26 | UAE5CL | SYD → DXB | May 26, 00:44 UTC | May 26, 01:00 UTC | 15m |
| 2026-05-25 | UAE5CL | SYD → DXB | May 25, 11:20 UTC | May 25, 23:04 UTC | 11h 44m |
| 2026-05-25 | UAE5CL | SYD → DXB | May 25, 05:35 UTC | May 25, 08:45 UTC | 3h 10m |
| 2026-05-24 | UAE3HJ | DXB → SYD | May 24, 08:20 UTC | May 24, 20:25 UTC | 12h 5m |
| 2026-05-24 | UAE5CL | SYD → DXB | May 24, 00:45 UTC | May 24, 00:55 UTC | 10m |
| 2026-05-23 | UAE5CL | SYD → DXB | May 23, 11:00 UTC | May 23, 22:00 UTC | 11h 1m |
| 2026-05-23 | UAE5CL | SYD → DXB | May 23, 05:45 UTC | May 23, 08:30 UTC | 2h 45m |
| 2026-05-22 | UAE3HJ | DXB → SYD | May 22, 22:25 UTC | May 23, 01:05 UTC | 2h 40m |
| 2026-05-21 | UAE88 | ZRH → DXB | May 21, 13:50 UTC | May 21, 20:00 UTC | 6h 10m |
| 2026-05-20 | UAE5CL | SYD → DXB | May 20, 11:00 UTC | May 21, 01:15 UTC | 14h 15m |
| 2026-05-20 | UAE5CL | SYD → DXB | May 20, 05:35 UTC | May 20, 08:25 UTC | 2h 50m |
| 2026-05-20 | UAE3HJ | DXB → SYD | May 20, 00:30 UTC | May 20, 00:45 UTC | 15m |
| 2026-05-19 | UAE3HJ | DXB → SYD | May 19, 22:20 UTC | May 19, 22:50 UTC | 30m |
| 2026-05-19 | UAE3HJ | DXB → SYD | May 19, 09:35 UTC | May 19, 20:10 UTC | 10h 35m |
| 2026-05-19 | UAE3HJ | DXB → SYD | May 19, 06:40 UTC | May 19, 07:00 UTC | 20m |
| 2026-05-18 | UAE41P | SFO → DXB | May 18, 00:30 UTC | May 18, 15:25 UTC | 14h 55m |
| 2026-05-17 | UAE51N | DXB → SFO | May 17, 07:10 UTC | May 17, 21:05 UTC | 13h 55m |
| 2026-05-17 | UAE51N | DXB → SFO | May 17, 05:15 UTC | May 17, 05:30 UTC | 15m |
| 2026-05-16 | UAE2 | LHR → DXB | May 16, 14:16 UTC | May 16, 20:50 UTC | 6h 35m |
| 2026-05-16 | UAE1 | DXB → LHR | May 16, 04:40 UTC | May 16, 11:41 UTC | 7h 1m |
| 2026-05-16 | UAE43P | MEL → DXB | May 16, 00:45 UTC | May 16, 01:05 UTC | 20m |
| 2026-05-15 | UAE43P | MEL → DXB | May 15, 11:35 UTC | May 15, 21:50 UTC | 10h 14m |
| 2026-05-14 | UAE1CR | DXB → MEL | May 14, 06:25 UTC | May 14, 19:15 UTC | 12h 50m |
| 2026-05-13 | UAE4 | LHR → DXB | May 13, 20:40 UTC | May 14, 03:20 UTC | 6h 40m |
| 2026-05-13 | UAE70M | DXB → LHR | May 13, 09:25 UTC | May 13, 17:20 UTC | 7h 55m |
| 2026-05-12 | UAE43P | MEL → DXB | May 12, 11:30 UTC | May 12, 22:01 UTC | 10h 30m |
| 2026-05-11 | UAE1CR | DXB → MEL | May 11, 16:00 UTC | May 11, 19:30 UTC | 3h 31m |
| 2026-05-11 | UAE569 | BLR → DXB | May 11, 02:30 UTC | May 11, 02:50 UTC | 20m |
| 2026-05-10 | UAE569 | BLR → DXB | May 10, 23:35 UTC | May 11, 00:00 UTC | 25m |
| 2026-05-10 | UAE568 | DXB → BLR | May 10, 20:20 UTC | May 10, 20:54 UTC | 35m |
| 2026-05-09 | UAE4 | LHR → DXB | May 9, 20:05 UTC | May 10, 03:04 UTC | 7h 0m |
| 2026-05-08 | UAE6 | LHR → DXB | May 8, 21:35 UTC | May 9, 04:30 UTC | 6h 55m |
| 2026-05-08 | UAE4CK | DXB → LHR | May 8, 12:10 UTC | May 8, 19:05 UTC | 6h 55m |
| 2026-05-07 | UAE804 | JED → DXB | May 7, 19:20 UTC | May 7, 20:25 UTC | 1h 5m |
| 2026-05-06 | UAE39L | MXP → DXB | May 6, 20:55 UTC | May 7, 02:55 UTC | 6h 0m |
| 2026-05-06 | UAE9LT | DXB → MXP | May 6, 14:25 UTC | May 6, 18:30 UTC | 4h 4m |
| 2026-05-04 | UAE2507 | DXB → DME | May 4, 16:25 UTC | May 4, 16:40 UTC | 15m |
| 2026-05-03 | UAE5CL | SYD → DXB | May 3, 11:05 UTC | May 4, 01:10 UTC | 14h 5m |
| 2026-05-03 | UAE5CL | SYD → DXB | May 3, 05:30 UTC | May 3, 08:25 UTC | 2h 55m |
| 2026-05-02 | UAE3HJ | DXB → SYD | May 2, 22:25 UTC | May 3, 01:00 UTC | 2h 35m |
| 2026-05-02 | UAE3HJ | DXB → SYD | May 2, 06:40 UTC | May 2, 20:10 UTC | 13h 30m |
| 2026-05-01 | UAE5CL | SYD → DXB | May 1, 11:00 UTC | May 2, 01:05 UTC | 14h 5m |
| 2026-05-01 | UAE5CL | SYD → DXB | May 1, 07:40 UTC | May 1, 08:30 UTC | 50m |
| 2026-05-01 | UAE5CL | SYD → DXB | May 1, 05:40 UTC | May 1, 05:50 UTC | 10m |
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-EVF page for operator, model, and routing details .