sensors Mode-S transponder
8964A2
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-EQJ · BOEING 777-300ER
- Hex
- 8964A2
- Octal
- 42262242
- Decimal
- 9,004,194
- Country
- AE
- Tail
- A6-EQJ
- Type
- B77W
- Flights observed
- 115
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 2h ago
Last known position
Country allocation
The ICAO 24-bit address 8964A2 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 |
|---|---|---|---|
| UAE3U | Emirates | 15 | 2026-05-26 |
| UAE5WR | Emirates | 14 | 2026-05-27 |
| UAE56W | Emirates | 9 | 2026-05-21 |
| UAE66V | Emirates | 8 | 2026-05-22 |
| UAE17K | Emirates | 5 | 2026-04-27 |
| UAE2MJ | Emirates | 4 | 2026-05-29 |
| UAE110 | Emirates | 4 | 2026-04-27 |
| UAE8UW | Emirates | 3 | 2026-05-05 |
| UAE83 | Emirates | 3 | 2026-04-30 |
| UAE816 | Emirates | 3 | 2026-04-28 |
| UAE815 | Emirates | 3 | 2026-04-17 |
| UAE62P | Emirates | 3 | 2026-05-28 |
| UAE414 | Emirates | 3 | 2026-05-06 |
| UAE356 | Emirates | 3 | 2026-04-28 |
| UAE316 | Emirates | 3 | 2026-05-08 |
| UAE312 | Emirates | 3 | 2026-05-10 |
| UAE8T | Emirates | 2 | 2026-05-29 |
| UAE4AQ | Emirates | 2 | 2026-04-17 |
| UAE313 | Emirates | 2 | 2026-05-10 |
| UAE29U | Emirates | 2 | 2026-04-30 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | UAE8T | ZRH → DXB | May 29, 20:20 UTC | May 30, 06:50 UTC | 10h 30m |
| 2026-05-29 | UAE2MJ | DXB → ZRH | May 29, 01:30 UTC | May 29, 17:35 UTC | 16h 5m |
| 2026-05-28 | UAE2MJ | DXB → ZRH | May 28, 20:35 UTC | May 29, 17:35 UTC | 21h 0m |
| 2026-05-28 | UAE2MJ | DXB → ZRH | May 28, 19:25 UTC | May 29, 17:35 UTC | 22h 10m |
| 2026-05-28 | UAE62P | DXB → MEL | May 28, 08:25 UTC | May 28, 11:40 UTC | 3h 15m |
| 2026-05-27 | UAE62P | DXB → MEL | May 27, 14:35 UTC | May 28, 11:40 UTC | 21h 5m |
| 2026-05-27 | UAE62P | DXB → MEL | May 27, 12:35 UTC | May 28, 11:40 UTC | 23h 5m |
| 2026-05-27 | UAE5WR | ORD → DXB | May 27, 10:35 UTC | May 28, 10:30 UTC | 23h 55m |
| 2026-05-27 | UAE5WR | ORD → DXB | May 27, 08:35 UTC | May 28, 08:30 UTC | 23h 55m |
| 2026-05-27 | UAE5WR | ORD → DXB | May 27, 01:54 UTC | May 27, 14:40 UTC | 12h 45m |
| 2026-05-26 | UAE3U | DXB → ORD | May 26, 07:15 UTC | May 26, 21:34 UTC | 14h 20m |
| 2026-05-25 | UAE3U | DXB → ORD | May 25, 16:50 UTC | May 26, 14:14 UTC | 21h 24m |
| 2026-05-25 | UAE23C | DXB → CPT | May 25, 12:40 UTC | May 25, 14:50 UTC | 2h 10m |
| 2026-05-24 | UAE23C | DXB → CPT | May 24, 14:45 UTC | May 25, 14:30 UTC | 23h 45m |
| 2026-05-24 | UAE5WR | ORD → DXB | May 24, 02:20 UTC | May 24, 15:20 UTC | 13h 0m |
| 2026-05-23 | UAE3U | DXB → ORD | May 23, 10:25 UTC | May 23, 20:45 UTC | 10h 20m |
| 2026-05-22 | UAE3U | DXB → ORD | May 22, 19:00 UTC | May 23, 15:10 UTC | 20h 9m |
| 2026-05-22 | UAE3U | DXB → ORD | May 22, 16:35 UTC | May 23, 15:10 UTC | 22h 34m |
| 2026-05-22 | UAE66V | BRU → DXB | May 22, 14:35 UTC | May 23, 13:35 UTC | 23h 0m |
| 2026-05-22 | UAE66V | BRU → DXB | May 22, 13:40 UTC | May 23, 12:30 UTC | 22h 50m |
| 2026-05-21 | UAE56W | DXB → BRU | May 21, 19:10 UTC | May 22, 11:40 UTC | 16h 30m |
| 2026-05-21 | UAE56W | DXB → BRU | May 21, 14:35 UTC | May 22, 11:40 UTC | 21h 5m |
| 2026-05-21 | UAE66V | BRU → DXB | May 21, 13:30 UTC | May 22, 11:40 UTC | 22h 10m |
| 2026-05-20 | UAE56W | DXB → BRU | May 20, 16:55 UTC | May 21, 11:05 UTC | 18h 10m |
| 2026-05-19 | UAE8T | ZRH → DXB | May 19, 20:10 UTC | May 20, 14:25 UTC | 18h 16m |
| 2026-05-19 | UAE2MJ | DXB → ZRH | May 19, 07:25 UTC | May 19, 18:05 UTC | 10h 40m |
| 2026-05-18 | UAE66V | BRU → DXB | May 18, 16:35 UTC | May 19, 16:30 UTC | 23h 54m |
| 2026-05-18 | UAE66V | BRU → DXB | May 18, 14:10 UTC | May 19, 07:50 UTC | 17h 39m |
| 2026-05-17 | UAE56W | DXB → BRU | May 17, 19:50 UTC | May 18, 11:35 UTC | 15h 45m |
| 2026-05-17 | UAE56W | DXB → BRU | May 17, 14:50 UTC | May 18, 11:35 UTC | 20h 45m |
| 2026-05-16 | UAE66V | BRU → DXB | May 16, 13:35 UTC | May 17, 08:20 UTC | 18h 45m |
| 2026-05-16 | UAE56W | DXB → BRU | May 16, 04:15 UTC | May 16, 11:25 UTC | 7h 11m |
| 2026-05-14 | UAE66V | BRU → DXB | May 14, 14:50 UTC | May 14, 21:20 UTC | 6h 30m |
| 2026-05-14 | UAE56W | DXB → BRU | May 14, 06:45 UTC | May 14, 10:50 UTC | 4h 5m |
| 2026-05-12 | UAE5WR | ORD → DXB | May 12, 02:45 UTC | May 12, 12:20 UTC | 9h 35m |
| 2026-05-11 | UAE3U | DXB → ORD | May 11, 12:50 UTC | May 11, 20:45 UTC | 7h 55m |
| 2026-05-10 | UAE313 | HND → DXB | May 10, 16:34 UTC | May 11, 13:30 UTC | 20h 55m |
| 2026-05-10 | UAE313 | HND → DXB | May 10, 15:35 UTC | May 11, 13:30 UTC | 21h 55m |
| 2026-05-10 | UAE312 | DXB → HND | May 10, 05:30 UTC | May 10, 13:10 UTC | 7h 40m |
| 2026-05-09 | UAE312 | DXB → HND | May 9, 16:35 UTC | May 10, 13:10 UTC | 20h 35m |
| 2026-05-09 | UAE312 | DXB → HND | May 9, 14:35 UTC | May 10, 13:10 UTC | 22h 35m |
| 2026-05-09 | UAE66V | BRU → DXB | May 9, 14:00 UTC | May 10, 12:30 UTC | 22h 30m |
| 2026-05-09 | UAE56W | DXB → BRU | May 9, 07:20 UTC | May 9, 11:50 UTC | 4h 30m |
| 2026-05-08 | UAE56W | DXB → BRU | May 8, 14:40 UTC | May 9, 11:50 UTC | 21h 10m |
| 2026-05-08 | UAE316 | DXB → KIX | May 8, 02:35 UTC | May 8, 08:09 UTC | 5h 35m |
| 2026-05-07 | UAE316 | DXB → KIX | May 7, 06:35 UTC | May 8, 03:49 UTC | 21h 15m |
| 2026-05-07 | UAE316 | DXB → KIX | May 7, 06:25 UTC | May 8, 03:49 UTC | 21h 25m |
| 2026-05-06 | UAE1DP | SYD → DXB | May 6, 20:20 UTC | May 7, 06:55 UTC | 10h 35m |
| 2026-05-06 | UAE414 | DXB → SYD | May 6, 01:25 UTC | May 6, 11:40 UTC | 10h 15m |
| 2026-05-05 | UAE414 | DXB → SYD | May 5, 14:50 UTC | May 6, 11:40 UTC | 20h 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-EQJ page for operator, model, and routing details .