sensors Mode-S transponder
8964B1
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-EVC · AIRBUS A-380-800
- Hex
- 8964B1
- Octal
- 42262261
- Decimal
- 9,004,209
- Country
- AE
- Tail
- A6-EVC
- Type
- A388
- Flights observed
- 164
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 3d ago
Last known position
Country allocation
The ICAO 24-bit address 8964B1 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 |
|---|---|---|---|
| UAE3HJ | Emirates | 22 | 2026-06-28 |
| UAE5CL | Emirates | 19 | 2026-06-28 |
| UAE41P | Emirates | 9 | 2026-04-28 |
| UAE1CR | - | 9 | 2026-07-09 |
| UAE8ER | Emirates | 8 | 2026-06-13 |
| UAE501 | - | 8 | 2026-07-03 |
| UAE43P | - | 8 | 2026-07-11 |
| UAE5V | Emirates | 7 | 2026-06-14 |
| UAE51N | Emirates | 6 | 2026-04-27 |
| UAE500 | - | 5 | 2026-07-02 |
| UAE75T | - | 4 | 2026-07-08 |
| UAE80T | Emirates | 3 | 2026-06-29 |
| UAE6AL | Emirates | 3 | 2026-06-13 |
| UAE569 | Emirates | 3 | 2026-05-26 |
| UAE373 | Emirates | 3 | 2026-05-18 |
| UAE319 | Emirates | 3 | 2026-06-01 |
| UAE318 | Emirates | 3 | 2026-06-01 |
| UAE2 | Emirates | 3 | 2026-06-22 |
| UAE1GP | Emirates | 3 | 2026-06-13 |
| UAE1 | - | 3 | 2026-06-22 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-11 | UAE43P | - | Jul 11, 00:40 UTC | Jul 11, 01:05 UTC | 25m |
| 2026-07-10 | UAE43P | - | Jul 10, 11:35 UTC | Jul 10, 22:10 UTC | 10h 35m |
| 2026-07-09 | UAE1CR | - | Jul 9, 16:10 UTC | Jul 9, 19:30 UTC | 3h 20m |
| 2026-07-09 | UAE1CR | - | Jul 9, 06:50 UTC | Jul 9, 07:10 UTC | 20m |
| 2026-07-08 | UAE75T | - | Jul 8, 21:50 UTC | Jul 9, 01:35 UTC | 3h 45m |
| 2026-07-08 | UAE75T | - | Jul 8, 11:35 UTC | Jul 8, 12:00 UTC | 25m |
| 2026-07-07 | UAE434 | - | Jul 7, 07:35 UTC | Jul 7, 20:35 UTC | 13h 0m |
| 2026-07-04 | UAE2VL | - | Jul 4, 00:55 UTC | Jul 4, 15:15 UTC | 14h 20m |
| 2026-07-03 | UAE1Y | DXB → IAH | Jul 3, 05:50 UTC | Jul 3, 21:50 UTC | 16h 0m |
| 2026-07-03 | UAE501 | - | Jul 3, 01:25 UTC | Jul 3, 01:55 UTC | 30m |
| 2026-07-02 | UAE501 | - | Jul 2, 23:35 UTC | Jul 3, 00:00 UTC | 25m |
| 2026-07-02 | UAE500 | - | Jul 2, 18:25 UTC | Jul 2, 21:10 UTC | 2h 45m |
| 2026-07-02 | UAE7CN | - | Jul 2, 08:30 UTC | Jul 2, 14:55 UTC | 6h 25m |
| 2026-07-01 | UAE7 | - | Jul 1, 23:20 UTC | Jul 2, 06:00 UTC | 6h 40m |
| 2026-07-01 | UAE2LT | CAI → DXB | Jul 1, 17:30 UTC | Jul 1, 20:35 UTC | 3h 5m |
| 2026-07-01 | UAE2K | - | Jul 1, 11:50 UTC | Jul 1, 14:40 UTC | 2h 50m |
| 2026-06-30 | UAE5AM | AKL → DXB | Jun 30, 08:55 UTC | Jul 1, 01:20 UTC | 16h 25m |
| 2026-06-29 | UAE80T | DXB → AKL | Jun 29, 21:39 UTC | Jun 29, 22:05 UTC | 25m |
| 2026-06-29 | UAE80T | DXB → AKL | Jun 29, 06:54 UTC | Jun 29, 20:04 UTC | 13h 10m |
| 2026-06-28 | UAE5CL | SYD → DXB | Jun 28, 11:14 UTC | Jun 29, 01:00 UTC | 13h 45m |
| 2026-06-28 | UAE5CL | SYD → DXB | Jun 28, 07:29 UTC | Jun 28, 08:34 UTC | 1h 5m |
| 2026-06-28 | UAE5CL | SYD → DXB | Jun 28, 05:29 UTC | Jun 28, 05:40 UTC | 10m |
| 2026-06-28 | UAE3HJ | DXB → SYD | Jun 28, 01:04 UTC | Jun 28, 01:19 UTC | 15m |
| 2026-06-27 | UAE3HJ | DXB → SYD | Jun 27, 22:45 UTC | Jun 27, 23:14 UTC | 30m |
| 2026-06-27 | UAE3HJ | DXB → SYD | Jun 27, 06:50 UTC | Jun 27, 20:29 UTC | 13h 40m |
| 2026-06-26 | UAE5CL | SYD → DXB | Jun 26, 11:05 UTC | Jun 27, 01:00 UTC | 13h 55m |
| 2026-06-26 | UAE5CL | SYD → DXB | Jun 26, 07:39 UTC | Jun 26, 08:30 UTC | 50m |
| 2026-06-26 | UAE5CL | SYD → DXB | Jun 26, 05:30 UTC | Jun 26, 05:44 UTC | 15m |
| 2026-06-26 | UAE3HJ | DXB → SYD | Jun 26, 00:50 UTC | Jun 26, 01:05 UTC | 15m |
| 2026-06-25 | UAE3HJ | DXB → SYD | Jun 25, 22:29 UTC | Jun 25, 22:59 UTC | 30m |
| 2026-06-25 | UAE3HJ | DXB → SYD | Jun 25, 16:24 UTC | Jun 25, 20:19 UTC | 3h 55m |
| 2026-06-25 | UAE3HJ | DXB → SYD | Jun 25, 07:09 UTC | Jun 25, 07:30 UTC | 20m |
| 2026-06-24 | UAE43P | - | Jun 24, 11:45 UTC | Jun 25, 00:55 UTC | 13h 10m |
| 2026-06-23 | UAE1CR | DXB → MEL | Jun 23, 08:25 UTC | Jun 23, 19:24 UTC | 11h 0m |
| 2026-06-23 | UAE1CR | DXB → MEL | Jun 23, 06:39 UTC | Jun 23, 06:59 UTC | 20m |
| 2026-06-22 | UAE2 | LHR → DXB | Jun 22, 14:29 UTC | Jun 22, 21:30 UTC | 7h 0m |
| 2026-06-22 | UAE1 | - | Jun 22, 04:00 UTC | Jun 22, 11:00 UTC | 7h 0m |
| 2026-06-21 | UAE1DP | SYD → DXB | Jun 21, 09:49 UTC | Jun 21, 10:09 UTC | 20m |
| 2026-06-20 | UAE1DP | SYD → DXB | Jun 20, 20:20 UTC | Jun 21, 08:10 UTC | 11h 50m |
| 2026-06-20 | UAE414 | DXB → SYD | Jun 20, 08:05 UTC | Jun 20, 11:54 UTC | 3h 50m |
| 2026-06-19 | UAE414 | DXB → SYD | Jun 19, 22:45 UTC | Jun 19, 23:04 UTC | 20m |
| 2026-06-18 | UAE2 | LHR → DXB | Jun 18, 13:45 UTC | Jun 18, 20:50 UTC | 7h 5m |
| 2026-06-18 | UAE1 | - | Jun 18, 04:00 UTC | Jun 18, 11:05 UTC | 7h 5m |
| 2026-06-17 | UAE75T | BNE → DXB | Jun 17, 00:45 UTC | Jun 17, 01:05 UTC | 20m |
| 2026-06-16 | UAE75T | BNE → DXB | Jun 16, 11:35 UTC | Jun 16, 23:20 UTC | 11h 46m |
| 2026-06-15 | UAE434 | DXB → BNE | Jun 15, 09:49 UTC | Jun 15, 19:55 UTC | 10h 5m |
| 2026-06-14 | UAE5V | JFK → DXB | Jun 14, 15:50 UTC | Jun 15, 04:04 UTC | 12h 14m |
| 2026-06-13 | UAE8ER | DXB → JFK | Jun 13, 23:45 UTC | Jun 14, 12:40 UTC | 12h 55m |
| 2026-06-13 | UAE6AL | NCE → DXB | Jun 13, 14:20 UTC | Jun 13, 20:20 UTC | 6h 0m |
| 2026-06-13 | UAE1GP | DXB → NCE | Jun 13, 11:10 UTC | Jun 13, 11:25 UTC | 15m |
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-EVC page for operator, model, and routing details .