sensors Mode-S transponder
8963E5
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-EOH · AIRBUS A-380-800
- Hex
- 8963E5
- Octal
- 42261745
- Decimal
- 9,004,005
- Country
- AE
- Tail
- A6-EOH
- Type
- A388
- Flights observed
- 59
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 18h ago
Last known position
Country allocation
The ICAO 24-bit address 8963E5 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 |
|---|---|---|---|
| UAE30Y | Emirates | 10 | 2026-06-08 |
| UAE242 | Emirates | 9 | 2026-06-08 |
| UAE7Q | Emirates | 8 | 2026-06-05 |
| UAE15K | Emirates | 7 | 2026-06-04 |
| UAE804 | Emirates | 5 | 2026-06-07 |
| UAE373 | Emirates | 2 | 2026-05-05 |
| UAE2LT | Emirates | 2 | 2026-05-22 |
| UAE2K | Emirates | 2 | 2026-05-22 |
| UAE9CL | Emirates | 1 | 2026-05-24 |
| UAE78L | Emirates | 1 | 2026-04-24 |
| UAE73J | Emirates | 1 | 2026-05-28 |
| UAE73 | Emirates | 1 | 2026-06-05 |
| UAE6JL | Emirates | 1 | 2026-04-24 |
| UAE65W | Emirates | 1 | 2026-06-05 |
| UAE5T | Emirates | 1 | 2026-05-24 |
| UAE5GU | Emirates | 1 | 2026-06-03 |
| UAE58Q | Emirates | 1 | 2026-06-03 |
| UAE372 | Emirates | 1 | 2026-05-05 |
| UAE34Y | Emirates | 1 | 2026-05-28 |
| UAE2X | Emirates | 1 | 2026-06-06 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-08 | UAE242 | YYZ → DXB | Jun 8, 19:25 UTC | Jun 9, 08:10 UTC | 12h 45m |
| 2026-06-08 | UAE30Y | DXB → YYZ | Jun 8, 02:35 UTC | Jun 8, 13:25 UTC | 10h 50m |
| 2026-06-07 | UAE804 | JED → DXB | Jun 7, 18:35 UTC | Jun 7, 19:50 UTC | 1h 15m |
| 2026-06-06 | UAE2X | BCN → DXB | Jun 6, 19:50 UTC | Jun 7, 02:10 UTC | 6h 20m |
| 2026-06-06 | UAE185 | DXB → BCN | Jun 6, 05:05 UTC | Jun 6, 11:05 UTC | 6h 0m |
| 2026-06-05 | UAE65W | CDG → DXB | Jun 5, 14:15 UTC | Jun 5, 20:55 UTC | 6h 40m |
| 2026-06-05 | UAE73 | DXB → CDG | Jun 5, 05:15 UTC | Jun 5, 11:50 UTC | 6h 35m |
| 2026-06-05 | UAE7Q | KUL → DXB | Jun 5, 00:40 UTC | Jun 5, 01:00 UTC | 20m |
| 2026-06-04 | UAE7Q | KUL → DXB | Jun 4, 18:40 UTC | Jun 4, 23:10 UTC | 4h 30m |
| 2026-06-04 | UAE15K | DXB → KUL | Jun 4, 01:30 UTC | Jun 4, 06:15 UTC | 4h 45m |
| 2026-06-03 | UAE5GU | DUS → DXB | Jun 3, 14:00 UTC | Jun 3, 20:30 UTC | 6h 30m |
| 2026-06-03 | UAE58Q | DXB → DUS | Jun 3, 04:45 UTC | Jun 3, 11:25 UTC | 6h 40m |
| 2026-06-02 | UAE7Q | KUL → DXB | Jun 2, 18:35 UTC | Jun 3, 00:55 UTC | 6h 20m |
| 2026-06-02 | UAE15K | DXB → KUL | Jun 2, 06:00 UTC | Jun 2, 06:20 UTC | 20m |
| 2026-06-02 | UAE15K | DXB → KUL | Jun 2, 01:40 UTC | Jun 2, 03:20 UTC | 1h 40m |
| 2026-06-01 | UAE15K | DXB → KUL | Jun 1, 23:55 UTC | Jun 2, 00:20 UTC | 25m |
| 2026-06-01 | UAE804 | JED → DXB | Jun 1, 12:50 UTC | Jun 1, 19:50 UTC | 7h 0m |
| 2026-05-30 | UAE804 | JED → DXB | May 30, 18:50 UTC | May 30, 20:00 UTC | 1h 10m |
| 2026-05-29 | UAE242 | YYZ → DXB | May 29, 19:15 UTC | May 30, 08:05 UTC | 12h 50m |
| 2026-05-28 | UAE30Y | DXB → YYZ | May 28, 23:50 UTC | May 29, 13:25 UTC | 13h 35m |
| 2026-05-28 | UAE73J | MAN → DXB | May 28, 13:25 UTC | May 28, 20:35 UTC | 7h 10m |
| 2026-05-28 | UAE34Y | DXB → MAN | May 28, 03:40 UTC | May 28, 10:55 UTC | 7h 15m |
| 2026-05-26 | UAE7Q | KUL → DXB | May 26, 00:00 UTC | May 26, 00:24 UTC | 25m |
| 2026-05-25 | UAE7Q | KUL → DXB | May 25, 20:04 UTC | May 25, 20:19 UTC | 15m |
| 2026-05-25 | UAE15K | DXB → KUL | May 25, 01:55 UTC | May 25, 06:45 UTC | 4h 50m |
| 2026-05-24 | UAE5T | MUC → DXB | May 24, 14:05 UTC | May 24, 20:00 UTC | 5h 55m |
| 2026-05-24 | UAE9CL | DXB → MUC | May 24, 07:35 UTC | May 24, 11:10 UTC | 3h 35m |
| 2026-05-23 | UAE804 | JED → DXB | May 23, 18:35 UTC | May 23, 19:40 UTC | 1h 5m |
| 2026-05-22 | UAE2LT | CAI → DXB | May 22, 17:55 UTC | May 22, 21:10 UTC | 3h 15m |
| 2026-05-22 | UAE2K | DXB → CAI | May 22, 13:00 UTC | May 22, 15:25 UTC | 2h 25m |
| 2026-05-22 | UAE7Q | KUL → DXB | May 22, 00:40 UTC | May 22, 01:05 UTC | 25m |
| 2026-05-21 | UAE7Q | KUL → DXB | May 21, 22:30 UTC | May 21, 23:25 UTC | 55m |
| 2026-05-21 | UAE7Q | KUL → DXB | May 21, 18:30 UTC | May 21, 18:45 UTC | 15m |
| 2026-05-21 | UAE15K | DXB → KUL | May 21, 06:00 UTC | May 21, 06:25 UTC | 25m |
| 2026-05-21 | UAE15K | DXB → KUL | May 21, 01:15 UTC | May 21, 01:55 UTC | 40m |
| 2026-05-13 | UAE242 | YYZ → DXB | May 13, 19:10 UTC | May 14, 08:00 UTC | 12h 50m |
| 2026-05-13 | UAE30Y | DXB → YYZ | May 13, 02:30 UTC | May 13, 13:35 UTC | 11h 5m |
| 2026-05-11 | UAE242 | YYZ → DXB | May 11, 19:15 UTC | May 12, 07:55 UTC | 12h 40m |
| 2026-05-11 | UAE30Y | DXB → YYZ | May 11, 12:20 UTC | May 11, 13:50 UTC | 1h 30m |
| 2026-05-10 | UAE30Y | DXB → YYZ | May 10, 23:29 UTC | May 11, 12:15 UTC | 12h 45m |
| 2026-05-09 | UAE242 | YYZ → DXB | May 9, 19:25 UTC | May 10, 08:20 UTC | 12h 55m |
| 2026-05-09 | UAE30Y | DXB → YYZ | May 9, 02:40 UTC | May 9, 13:30 UTC | 10h 50m |
| 2026-05-05 | UAE373 | BKK → DXB | May 5, 20:15 UTC | May 5, 20:55 UTC | 40m |
| 2026-05-05 | UAE373 | BKK → DXB | May 5, 14:30 UTC | May 5, 17:05 UTC | 2h 35m |
| 2026-05-05 | UAE372 | DXB → BKK | May 5, 06:40 UTC | May 5, 12:10 UTC | 5h 30m |
| 2026-05-04 | UAE804 | JED → DXB | May 4, 12:10 UTC | May 4, 21:50 UTC | 9h 41m |
| 2026-05-03 | UAE242 | YYZ → DXB | May 3, 19:20 UTC | May 4, 08:10 UTC | 12h 50m |
| 2026-05-03 | UAE30Y | DXB → YYZ | May 3, 00:05 UTC | May 3, 13:20 UTC | 13h 14m |
| 2026-05-02 | UAE2LT | CAI → DXB | May 2, 17:55 UTC | May 2, 20:50 UTC | 2h 55m |
| 2026-05-02 | UAE2K | DXB → CAI | May 2, 11:45 UTC | May 2, 15:20 UTC | 3h 35m |
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-EOH page for operator, model, and routing details .