sensors Mode-S transponder
8963A3
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-EFS · BOEING 777-200LR
- Hex
- 8963A3
- Octal
- 42261643
- Decimal
- 9,003,939
- Country
- AE
- Tail
- A6-EFS
- Type
- B77L
- Flights observed
- 133
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 53m ago
Current position
Country allocation
The ICAO 24-bit address 8963A3 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 |
|---|---|---|---|
| UAE9656 | - | 8 | 2026-05-08 |
| UAE9655 | - | 7 | 2026-05-07 |
| UAE9873 | Emirates | 6 | 2026-05-09 |
| UAE9871 | Emirates | 6 | 2026-05-14 |
| UAE9861 | Emirates | 5 | 2026-05-13 |
| UAE9806 | - | 5 | 2026-05-15 |
| UAE9618 | - | 5 | 2026-04-22 |
| UAE9807 | - | 4 | 2026-05-16 |
| UAE9988 | Emirates | 3 | 2026-04-28 |
| UAE9922 | Emirates | 3 | 2026-05-28 |
| UAE9906 | Emirates | 3 | 2026-05-03 |
| UAE9881 | - | 3 | 2026-04-13 |
| UAE9880 | - | 3 | 2026-04-13 |
| UAE9860 | Emirates | 3 | 2026-05-12 |
| UAE9817 | Emirates | 3 | 2026-04-27 |
| UAE9657 | - | 3 | 2026-05-02 |
| UAE9616 | Emirates | 3 | 2026-05-24 |
| UAE9341 | Emirates | 3 | 2026-04-23 |
| UAE9989 | Emirates | 2 | 2026-04-27 |
| UAE9987 | Emirates | 2 | 2026-04-25 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | UAE9944 | LHR → DWC | May 30, 00:40 UTC | May 30, 08:45 UTC | 8h 5m |
| 2026-05-29 | UAE9943 | DWC → LHR | May 29, 14:20 UTC | May 29, 21:35 UTC | 7h 15m |
| 2026-05-28 | UAE9943 | DWC → LHR | May 28, 18:40 UTC | May 29, 10:55 UTC | 16h 15m |
| 2026-05-28 | UAE9922 | UIO → BQN | May 28, 14:25 UTC | May 28, 15:35 UTC | 1h 10m |
| 2026-05-27 | UAE9922 | UIO → BQN | May 27, 23:35 UTC | May 28, 11:20 UTC | 11h 45m |
| 2026-05-27 | UAE9922 | UIO → BQN | May 27, 14:50 UTC | May 28, 11:20 UTC | 20h 30m |
| 2026-05-27 | UAE9921 | SYD → HKG | May 27, 11:25 UTC | May 27, 12:00 UTC | 35m |
| 2026-05-25 | UAE9893 | ICN → DWC | May 25, 19:35 UTC | May 26, 10:44 UTC | 15h 10m |
| 2026-05-25 | UAE9893 | ICN → DWC | May 25, 11:45 UTC | May 26, 10:44 UTC | 22h 59m |
| 2026-05-25 | UAE9892 | - | May 25, 09:10 UTC | May 26, 08:19 UTC | 23h 10m |
| 2026-05-25 | UAE9827 | HKG → DXB | May 25, 08:20 UTC | May 25, 22:19 UTC | 13h 59m |
| 2026-05-24 | UAE9827 | HKG → DXB | May 24, 16:40 UTC | May 25, 04:05 UTC | 11h 25m |
| 2026-05-24 | UAE9616 | SYD → MEL | May 24, 11:40 UTC | May 24, 12:00 UTC | 20m |
| 2026-05-24 | UAE9616 | SYD → MEL | May 24, 09:25 UTC | May 24, 09:55 UTC | 30m |
| 2026-05-24 | UAE9616 | SYD → MEL | May 24, 05:25 UTC | May 24, 06:10 UTC | 45m |
| 2026-05-23 | UAE9936 | JFK → AMS | May 23, 03:15 UTC | May 23, 21:15 UTC | 18h 0m |
| 2026-05-22 | UAE9936 | JFK → AMS | May 22, 16:35 UTC | May 23, 01:10 UTC | 8h 35m |
| 2026-05-22 | UAE6MR | IAH → FRA | May 22, 10:45 UTC | May 22, 12:20 UTC | 1h 35m |
| 2026-05-21 | UAE9935 | FRA → MEX | May 21, 19:40 UTC | May 22, 07:10 UTC | 11h 30m |
| 2026-05-21 | UAE9935 | FRA → MEX | May 21, 03:55 UTC | May 21, 16:15 UTC | 12h 20m |
| 2026-05-20 | UAE9642 | - | May 20, 13:35 UTC | May 21, 01:20 UTC | 11h 45m |
| 2026-05-20 | UAE9642 | AMS → CPH | May 20, 09:40 UTC | May 20, 10:35 UTC | 55m |
| 2026-05-20 | UAE9641 | - | May 20, 03:35 UTC | May 20, 07:45 UTC | 4h 11m |
| 2026-05-19 | UAE9641 | - | May 19, 10:05 UTC | May 19, 17:45 UTC | 7h 40m |
| 2026-05-19 | UAE9640 | - | May 19, 07:30 UTC | May 19, 08:05 UTC | 35m |
| 2026-05-18 | UAE9640 | - | May 18, 12:35 UTC | May 19, 08:05 UTC | 19h 29m |
| 2026-05-18 | UAE9749 | NBO → DWC | May 18, 07:10 UTC | May 18, 12:40 UTC | 5h 30m |
| 2026-05-17 | UAE9795 | - | May 17, 14:55 UTC | May 17, 15:10 UTC | 15m |
| 2026-05-17 | UAE9794 | DWC → ICN | May 17, 12:15 UTC | May 17, 12:35 UTC | 20m |
| 2026-05-17 | UAE9794 | DWC → ICN | May 17, 11:05 UTC | May 17, 11:20 UTC | 15m |
| 2026-05-16 | UAE9807 | - | May 16, 13:11 UTC | May 17, 11:20 UTC | 22h 10m |
| 2026-05-16 | UAE9807 | - | May 16, 05:10 UTC | May 16, 14:01 UTC | 8h 51m |
| 2026-05-15 | UAE9806 | - | May 15, 07:40 UTC | May 16, 02:15 UTC | 18h 34m |
| 2026-05-14 | UAE9871 | CAN → DWC | May 14, 22:50 UTC | May 15, 20:30 UTC | 21h 39m |
| 2026-05-14 | UAE9871 | CAN → DWC | May 14, 20:50 UTC | May 15, 20:30 UTC | 23h 39m |
| 2026-05-14 | UAE9871 | CAN → DWC | May 14, 20:40 UTC | May 15, 18:20 UTC | 21h 39m |
| 2026-05-14 | UAE9871 | CAN → DWC | May 14, 11:15 UTC | May 15, 10:45 UTC | 23h 30m |
| 2026-05-14 | UAE9870 | DWC → CAN | May 14, 03:20 UTC | May 14, 23:25 UTC | 20h 5m |
| 2026-05-13 | UAE9800 | - | May 13, 15:50 UTC | May 14, 00:55 UTC | 9h 5m |
| 2026-05-13 | UAE9861 | DAC → DWC | May 13, 04:20 UTC | May 13, 07:25 UTC | 3h 5m |
| 2026-05-13 | UAE9861 | DAC → DWC | May 13, 01:20 UTC | May 13, 01:35 UTC | 15m |
| 2026-05-12 | UAE9860 | DWC → DAC | May 12, 16:55 UTC | May 12, 22:40 UTC | 5h 45m |
| 2026-05-11 | UAE9956 | ZAZ → DWC | May 11, 09:00 UTC | May 11, 11:45 UTC | 2h 45m |
| 2026-05-10 | UAE9955 | - | May 10, 13:05 UTC | May 11, 05:35 UTC | 16h 30m |
| 2026-05-10 | UAE9895 | - | May 10, 03:00 UTC | May 11, 02:45 UTC | 23h 45m |
| 2026-05-10 | UAE9895 | - | May 10, 01:09 UTC | May 11, 00:45 UTC | 23h 35m |
| 2026-05-09 | UAE9873 | PVG → DWC | May 9, 10:30 UTC | May 10, 04:19 UTC | 17h 50m |
| 2026-05-09 | UAE9873 | PVG → DWC | May 9, 08:10 UTC | May 10, 04:19 UTC | 20h 10m |
| 2026-05-08 | UAE9656 | - | May 8, 12:10 UTC | May 9, 02:35 UTC | 14h 25m |
| 2026-05-08 | UAE9656 | - | May 8, 08:55 UTC | May 8, 09:54 UTC | 1h 0m |
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-EFS page for operator, model, and routing details .