sensors Mode-S transponder
8964E1
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-EVJ · AIRBUS A-380-800
- Hex
- 8964E1
- Octal
- 42262341
- Decimal
- 9,004,257
- Country
- AE
- Tail
- A6-EVJ
- Type
- A388
- Flights observed
- 134
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 5h ago
Current position
Country allocation
The ICAO 24-bit address 8964E1 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 |
|---|---|---|---|
| UAE51N | - | 8 | 2026-07-08 |
| UAE568 | Emirates | 7 | 2026-07-05 |
| UAE41P | - | 7 | 2026-07-09 |
| UAE80T | Emirates | 6 | 2026-06-14 |
| UAE569 | - | 6 | 2026-07-05 |
| UAE4CK | Emirates | 6 | 2026-05-31 |
| UAE4 | Emirates | 6 | 2026-06-01 |
| UAE7CN | Emirates | 5 | 2026-04-14 |
| UAE5AM | Emirates | 5 | 2026-06-15 |
| UAE43P | - | 5 | 2026-06-19 |
| UAE319 | - | 5 | 2026-07-10 |
| UAE262 | Emirates | 5 | 2026-07-07 |
| UAE261 | Emirates | 5 | 2026-07-06 |
| UAE83M | - | 4 | 2026-07-11 |
| UAE70M | Emirates | 4 | 2026-06-01 |
| UAE414 | - | 4 | 2026-07-04 |
| UAE3HJ | Emirates | 4 | 2026-04-17 |
| UAE216 | - | 4 | 2026-07-12 |
| UAE1DP | - | 4 | 2026-07-04 |
| UAE1CR | Emirates | 4 | 2026-06-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | UAE1Y | - | Jul 14, 07:20 UTC | Jul 14, 14:25 UTC | 7h 5m |
| 2026-07-12 | UAE216 | - | Jul 12, 00:30 UTC | Jul 12, 16:01 UTC | 15h 30m |
| 2026-07-11 | UAE83M | - | Jul 11, 05:05 UTC | Jul 11, 21:45 UTC | 16h 40m |
| 2026-07-10 | UAE319 | - | Jul 10, 23:00 UTC | Jul 10, 23:20 UTC | 20m |
| 2026-07-10 | UAE319 | - | Jul 10, 13:50 UTC | Jul 10, 22:00 UTC | 8h 11m |
| 2026-07-09 | UAE318 | - | Jul 9, 23:35 UTC | Jul 10, 09:00 UTC | 9h 25m |
| 2026-07-09 | UAE41P | - | Jul 9, 01:30 UTC | Jul 9, 16:50 UTC | 15h 20m |
| 2026-07-08 | UAE51N | - | Jul 8, 04:55 UTC | Jul 8, 20:30 UTC | 15h 35m |
| 2026-07-07 | UAE262 | GRU → DXB | Jul 7, 04:25 UTC | Jul 7, 18:10 UTC | 13h 45m |
| 2026-07-06 | UAE261 | DXB → GRU | Jul 6, 05:55 UTC | Jul 6, 20:35 UTC | 14h 40m |
| 2026-07-05 | UAE569 | - | Jul 5, 23:35 UTC | Jul 6, 02:45 UTC | 3h 10m |
| 2026-07-05 | UAE568 | DXB → BLR | Jul 5, 18:10 UTC | Jul 5, 21:30 UTC | 3h 20m |
| 2026-07-04 | UAE1DP | - | Jul 4, 20:15 UTC | Jul 5, 09:55 UTC | 13h 40m |
| 2026-07-04 | UAE414 | - | Jul 4, 08:00 UTC | Jul 4, 11:50 UTC | 3h 50m |
| 2026-07-03 | UAE414 | - | Jul 3, 22:50 UTC | Jul 3, 23:15 UTC | 25m |
| 2026-07-03 | UAE2VL | - | Jul 3, 01:10 UTC | Jul 3, 15:30 UTC | 14h 20m |
| 2026-07-02 | UAE1Y | DXB → IAH | Jul 2, 06:00 UTC | Jul 2, 22:15 UTC | 16h 15m |
| 2026-07-01 | UAE51P | MAD → DXB | Jul 1, 13:50 UTC | Jul 1, 20:35 UTC | 6h 45m |
| 2026-07-01 | UAE7AM | - | Jul 1, 04:05 UTC | Jul 1, 11:20 UTC | 7h 15m |
| 2026-06-30 | UAE262 | GRU → DXB | Jun 30, 04:30 UTC | Jun 30, 18:50 UTC | 14h 20m |
| 2026-06-29 | UAE261 | DXB → GRU | Jun 29, 05:15 UTC | Jun 29, 20:00 UTC | 14h 45m |
| 2026-06-28 | UAE41P | - | Jun 28, 00:30 UTC | Jun 28, 16:19 UTC | 15h 50m |
| 2026-06-27 | UAE51N | DXB → SFO | Jun 27, 04:59 UTC | Jun 27, 20:55 UTC | 15h 55m |
| 2026-06-26 | UAE262 | GRU → DXB | Jun 26, 04:45 UTC | Jun 26, 18:54 UTC | 14h 10m |
| 2026-06-25 | UAE261 | DXB → GRU | Jun 25, 05:05 UTC | Jun 25, 19:39 UTC | 14h 35m |
| 2026-06-24 | UAE216 | LAX → DXB | Jun 24, 00:40 UTC | Jun 24, 16:14 UTC | 15h 35m |
| 2026-06-23 | UAE83M | DXB → LAX | Jun 23, 05:15 UTC | Jun 23, 21:59 UTC | 16h 45m |
| 2026-06-21 | UAE5V | JFK → DXB | Jun 21, 15:40 UTC | Jun 22, 03:54 UTC | 12h 15m |
| 2026-06-20 | UAE8ER | DXB → JFK | Jun 20, 22:54 UTC | Jun 21, 12:35 UTC | 13h 40m |
| 2026-06-20 | UAE41P | - | Jun 20, 00:39 UTC | Jun 20, 16:29 UTC | 15h 50m |
| 2026-06-19 | UAE51N | DXB → SFO | Jun 19, 05:09 UTC | Jun 19, 21:04 UTC | 15h 55m |
| 2026-06-19 | UAE43P | - | Jun 19, 00:29 UTC | Jun 19, 00:45 UTC | 15m |
| 2026-06-18 | UAE43P | - | Jun 18, 11:35 UTC | Jun 18, 21:30 UTC | 9h 55m |
| 2026-06-17 | UAE1CR | DXB → MEL | Jun 17, 06:30 UTC | Jun 17, 19:30 UTC | 13h 0m |
| 2026-06-16 | UAE39L | - | Jun 16, 20:25 UTC | Jun 17, 02:30 UTC | 6h 5m |
| 2026-06-16 | UAE9LT | DXB → MXP | Jun 16, 11:40 UTC | Jun 16, 17:49 UTC | 6h 10m |
| 2026-06-15 | UAE5AM | AKL → DXB | Jun 15, 10:50 UTC | Jun 16, 00:55 UTC | 14h 5m |
| 2026-06-15 | UAE5AM | AKL → DXB | Jun 15, 08:40 UTC | Jun 15, 09:05 UTC | 25m |
| 2026-06-14 | UAE80T | DXB → AKL | Jun 14, 19:05 UTC | Jun 14, 21:55 UTC | 2h 50m |
| 2026-06-13 | UAE569 | BLR → DXB | Jun 13, 23:30 UTC | Jun 14, 02:40 UTC | 3h 10m |
| 2026-06-13 | UAE568 | DXB → BLR | Jun 13, 19:30 UTC | Jun 13, 21:05 UTC | 1h 35m |
| 2026-06-13 | UAE1DP | SYD → DXB | Jun 13, 09:30 UTC | Jun 13, 09:50 UTC | 20m |
| 2026-06-12 | UAE1DP | SYD → DXB | Jun 12, 20:15 UTC | Jun 13, 08:05 UTC | 11h 49m |
| 2026-06-12 | UAE414 | DXB → SYD | Jun 12, 01:30 UTC | Jun 12, 11:25 UTC | 9h 55m |
| 2026-06-11 | UAE262 | GRU → DXB | Jun 11, 04:35 UTC | Jun 11, 18:35 UTC | 14h 0m |
| 2026-06-10 | UAE261 | DXB → GRU | Jun 10, 20:20 UTC | Jun 10, 22:00 UTC | 1h 40m |
| 2026-06-08 | UAE1DP | SYD → DXB | Jun 8, 20:15 UTC | Jun 9, 10:00 UTC | 13h 45m |
| 2026-06-08 | UAE414 | DXB → SYD | Jun 8, 09:00 UTC | Jun 8, 12:05 UTC | 3h 5m |
| 2026-06-07 | UAE41P | SFO → DXB | Jun 7, 00:34 UTC | Jun 7, 16:15 UTC | 15h 40m |
| 2026-06-06 | UAE51N | DXB → SFO | Jun 6, 18:29 UTC | Jun 6, 21:00 UTC | 2h 30m |
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-EVJ page for operator, model, and routing details .