sensors Mode-S transponder
8963D3
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-EPD · BOEING 777-300ER
- Hex
- 8963D3
- Octal
- 42261723
- Decimal
- 9,003,987
- Country
- AE
- Tail
- A6-EPD
- Type
- B77W
- Flights observed
- 101
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 9h ago
Last known position
Country allocation
The ICAO 24-bit address 8963D3 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 |
|---|---|---|---|
| UAE1X | Emirates | 7 | 2026-04-30 |
| UAE161 | Emirates | 7 | 2026-04-30 |
| UAE5JM | Emirates | 4 | 2026-05-11 |
| UAE397 | Emirates | 4 | 2026-05-31 |
| UAE307 | Emirates | 4 | 2026-04-26 |
| UAE1GP | Emirates | 4 | 2026-04-15 |
| UAE194 | Emirates | 4 | 2026-05-18 |
| UAE110 | Emirates | 4 | 2026-06-01 |
| UAE8Y | Emirates | 3 | 2026-05-20 |
| UAE6AL | Emirates | 3 | 2026-04-15 |
| UAE5K | Emirates | 3 | 2026-05-11 |
| UAE3MV | Emirates | 3 | 2026-04-27 |
| UAE37R | Emirates | 3 | 2026-05-25 |
| UAE378 | Emirates | 3 | 2026-05-14 |
| UAE306 | Emirates | 3 | 2026-04-25 |
| UAE304 | Emirates | 3 | 2026-06-02 |
| UAE192 | Emirates | 3 | 2026-04-27 |
| UAE766 | Emirates | 2 | 2026-05-28 |
| UAE60L | Emirates | 2 | 2026-04-21 |
| UAE5M | Emirates | 2 | 2026-05-18 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | UAE304 | DXB → PVG | Jun 2, 07:20 UTC | Jun 2, 10:05 UTC | 2h 45m |
| 2026-06-01 | UAE110 | LCA → DXB | Jun 1, 17:50 UTC | Jun 1, 20:30 UTC | 2h 40m |
| 2026-06-01 | UAE110 | LCA → DXB | Jun 1, 13:55 UTC | Jun 1, 16:00 UTC | 2h 5m |
| 2026-06-01 | - | AMM → MLA | Jun 1, 09:45 UTC | Jun 1, 11:55 UTC | 2h 10m |
| 2026-05-31 | UAE397 | HKT → DXB | May 31, 08:55 UTC | May 31, 21:10 UTC | 12h 15m |
| 2026-05-28 | UAE766 | JNB → DXB | May 28, 20:40 UTC | May 28, 21:00 UTC | 20m |
| 2026-05-28 | UAE1LJ | DXB → JNB | May 28, 17:55 UTC | May 28, 18:25 UTC | 30m |
| 2026-05-27 | UAE305 | PVG → DXB | May 27, 03:20 UTC | May 27, 06:29 UTC | 3h 10m |
| 2026-05-26 | UAE305 | PVG → DXB | May 26, 09:40 UTC | May 27, 06:29 UTC | 20h 50m |
| 2026-05-26 | UAE304 | DXB → PVG | May 26, 07:29 UTC | May 26, 10:39 UTC | 3h 10m |
| 2026-05-25 | UAE304 | DXB → PVG | May 25, 11:35 UTC | May 26, 10:39 UTC | 23h 4m |
| 2026-05-25 | UAE37R | DXB → JNB | May 25, 07:20 UTC | May 25, 07:50 UTC | 30m |
| 2026-05-23 | UAE4DT | STN → DXB | May 23, 14:20 UTC | May 23, 20:45 UTC | 6h 25m |
| 2026-05-22 | UAE9J | DXB → STN | May 22, 19:40 UTC | May 23, 11:45 UTC | 16h 4m |
| 2026-05-22 | UAE187 | DXB → BCN | May 22, 13:10 UTC | May 22, 17:00 UTC | 3h 50m |
| 2026-05-21 | UAE187 | DXB → BCN | May 21, 18:05 UTC | May 22, 16:45 UTC | 22h 40m |
| 2026-05-21 | UAE315 | SIN → DXB | May 21, 02:45 UTC | May 21, 18:35 UTC | 15h 50m |
| 2026-05-20 | UAE314 | DXB → SIN | May 20, 06:40 UTC | May 21, 00:10 UTC | 17h 30m |
| 2026-05-20 | UAE8Y | KUL → DXB | May 20, 02:40 UTC | May 20, 02:55 UTC | 15m |
| 2026-05-18 | UAE194 | LIS → DXB | May 18, 20:45 UTC | May 19, 13:25 UTC | 16h 40m |
| 2026-05-18 | UAE5M | DXB → LIS | May 18, 11:00 UTC | May 18, 18:30 UTC | 7h 29m |
| 2026-05-17 | UAE9H | GLA → DXB | May 17, 14:10 UTC | May 18, 02:40 UTC | 12h 30m |
| 2026-05-17 | UAE33T | DXB → GLA | May 17, 03:55 UTC | May 17, 11:35 UTC | 7h 40m |
| 2026-05-16 | UAE397 | HKT → DXB | May 16, 22:20 UTC | May 16, 22:40 UTC | 20m |
| 2026-05-16 | UAE194 | LIS → DXB | May 16, 00:50 UTC | May 16, 20:35 UTC | 19h 45m |
| 2026-05-15 | UAE194 | LIS → DXB | May 15, 22:50 UTC | May 16, 20:35 UTC | 21h 45m |
| 2026-05-15 | UAE194 | LIS → DXB | May 15, 20:50 UTC | May 16, 20:35 UTC | 23h 45m |
| 2026-05-15 | UAE5M | DXB → LIS | May 15, 12:45 UTC | May 15, 18:40 UTC | 5h 54m |
| 2026-05-14 | UAE379 | HKT → DXB | May 14, 18:35 UTC | May 14, 18:55 UTC | 20m |
| 2026-05-14 | UAE378 | DXB → HKT | May 14, 00:25 UTC | May 14, 02:50 UTC | 2h 25m |
| 2026-05-13 | UAE378 | DXB → HKT | May 13, 05:30 UTC | May 14, 02:50 UTC | 21h 20m |
| 2026-05-13 | UAE378 | DXB → HKT | May 13, 02:50 UTC | May 14, 02:45 UTC | 23h 55m |
| 2026-05-13 | UAE8Y | KUL → DXB | May 13, 02:40 UTC | May 14, 00:45 UTC | 22h 5m |
| 2026-05-11 | UAE5JM | DXB → KUL | May 11, 20:35 UTC | May 12, 13:20 UTC | 16h 45m |
| 2026-05-11 | UAE5K | DXB → CMB | May 11, 01:45 UTC | May 11, 18:25 UTC | 16h 41m |
| 2026-05-10 | UAE5K | DXB → CMB | May 10, 11:50 UTC | May 11, 05:25 UTC | 17h 35m |
| 2026-05-10 | UAE37R | DXB → JNB | May 10, 07:34 UTC | May 10, 08:05 UTC | 30m |
| 2026-05-09 | UAE12W | CCU → DXB | May 9, 19:35 UTC | May 9, 19:45 UTC | 10m |
| 2026-05-09 | UAE12W | CCU → DXB | May 9, 15:30 UTC | May 9, 18:15 UTC | 2h 45m |
| 2026-05-09 | UAE98N | DXB → CCU | May 9, 12:40 UTC | May 9, 13:20 UTC | 40m |
| 2026-05-05 | UAE766 | JNB → DXB | May 5, 21:20 UTC | May 5, 21:45 UTC | 25m |
| 2026-05-05 | UAE1LJ | DXB → JNB | May 5, 18:05 UTC | May 5, 18:45 UTC | 40m |
| 2026-05-05 | UAE820 | RUH → DXB | May 5, 07:20 UTC | May 5, 08:25 UTC | 1h 5m |
| 2026-05-04 | UAE397 | HKT → DXB | May 4, 08:30 UTC | May 4, 23:25 UTC | 14h 56m |
| 2026-05-04 | UAE396 | DXB → HKT | May 4, 06:40 UTC | May 4, 06:55 UTC | 15m |
| 2026-05-03 | UAE2X | BCN → DXB | May 3, 19:40 UTC | May 4, 01:55 UTC | 6h 15m |
| 2026-05-03 | UAE185 | DXB → BCN | May 3, 04:20 UTC | May 3, 11:10 UTC | 6h 50m |
| 2026-05-02 | UAE185 | DXB → BCN | May 2, 11:45 UTC | May 3, 10:45 UTC | 22h 59m |
| 2026-05-02 | UAE37R | DXB → JNB | May 2, 00:25 UTC | May 2, 07:55 UTC | 7h 30m |
| 2026-05-01 | UAE110 | LCA → DXB | May 1, 18:05 UTC | May 1, 21:25 UTC | 3h 20m |
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-EPD page for operator, model, and routing details .