sensors Mode-S transponder
8963A2
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-EFO · BOEING 777-200LR
- Hex
- 8963A2
- Octal
- 42261642
- Decimal
- 9,003,938
- Country
- AE
- Tail
- A6-EFO
- Type
- B77L
- Flights observed
- 141
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 1h ago
Current position
Country allocation
The ICAO 24-bit address 8963A2 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 |
|---|---|---|---|
| UAE9831 | - | 9 | 2026-05-26 |
| UAE9830 | - | 8 | 2026-05-26 |
| UAE9936 | Emirates | 6 | 2026-05-26 |
| UAE9935 | Emirates | 6 | 2026-05-24 |
| UAE9920 | Emirates | 6 | 2026-05-29 |
| UAE9919 | Emirates | 6 | 2026-05-28 |
| UAE9917 | Emirates | 5 | 2026-05-12 |
| UAE9888 | - | 5 | 2026-05-23 |
| UAE9620 | Emirates | 5 | 2026-04-20 |
| UAE9389 | Emirates | 5 | 2026-04-15 |
| UAE9943 | Emirates | 4 | 2026-05-15 |
| UAE9882 | - | 4 | 2026-05-22 |
| UAE9879 | Emirates | 4 | 2026-05-01 |
| UAE9944 | Emirates | 3 | 2026-05-16 |
| UAE9942 | Emirates | 3 | 2026-05-07 |
| UAE9906 | - | 3 | 2026-04-13 |
| UAE9903 | Emirates | 3 | 2026-05-02 |
| UAE9889 | Emirates | 3 | 2026-05-23 |
| UAE9883 | Emirates | 3 | 2026-05-23 |
| UAE9878 | Emirates | 3 | 2026-04-30 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | UAE9792 | - | May 30, 06:30 UTC | May 30, 07:10 UTC | 40m |
| 2026-05-29 | UAE9920 | AMS → DWC | May 29, 13:55 UTC | May 30, 04:25 UTC | 14h 30m |
| 2026-05-29 | UAE9920 | AMS → DWC | May 29, 10:15 UTC | May 29, 10:55 UTC | 40m |
| 2026-05-28 | UAE9920 | AMS → DWC | May 28, 23:50 UTC | May 29, 07:15 UTC | 7h 25m |
| 2026-05-28 | UAE9919 | MEX → UIO | May 28, 11:50 UTC | May 28, 20:10 UTC | 8h 20m |
| 2026-05-27 | UAE9919 | MEX → UIO | May 27, 20:05 UTC | May 28, 07:05 UTC | 11h 0m |
| 2026-05-27 | UAE9919 | MEX → UIO | May 27, 00:55 UTC | May 27, 17:10 UTC | 16h 16m |
| 2026-05-26 | UAE9831 | - | May 26, 22:59 UTC | May 26, 23:10 UTC | 10m |
| 2026-05-26 | UAE9830 | - | May 26, 20:15 UTC | May 26, 20:54 UTC | 40m |
| 2026-05-26 | UAE9936 | JFK → AMS | May 26, 03:30 UTC | May 26, 18:05 UTC | 14h 35m |
| 2026-05-25 | UAE9936 | JFK → AMS | May 25, 16:00 UTC | May 26, 00:44 UTC | 8h 44m |
| 2026-05-25 | UAE6MR | IAH → FRA | May 25, 10:45 UTC | May 25, 12:25 UTC | 1h 40m |
| 2026-05-24 | UAE9935 | FRA → MEX | May 24, 19:40 UTC | May 25, 07:15 UTC | 11h 35m |
| 2026-05-24 | UAE9935 | FRA → MEX | May 24, 01:25 UTC | May 24, 15:50 UTC | 14h 25m |
| 2026-05-23 | UAE9889 | PVG → BKK | May 23, 13:55 UTC | May 24, 12:30 UTC | 22h 35m |
| 2026-05-23 | UAE9889 | PVG → BKK | May 23, 11:50 UTC | May 24, 04:55 UTC | 17h 6m |
| 2026-05-23 | UAE9888 | - | May 23, 04:35 UTC | May 24, 04:30 UTC | 23h 56m |
| 2026-05-23 | UAE9888 | - | May 23, 03:50 UTC | May 24, 02:30 UTC | 22h 41m |
| 2026-05-23 | UAE9883 | HKG → DWC | May 23, 01:35 UTC | May 23, 14:30 UTC | 12h 54m |
| 2026-05-22 | UAE9883 | HKG → DWC | May 22, 14:35 UTC | May 23, 14:30 UTC | 23h 55m |
| 2026-05-22 | UAE9883 | HKG → DWC | May 22, 12:35 UTC | May 23, 12:25 UTC | 23h 49m |
| 2026-05-22 | UAE9882 | - | May 22, 12:05 UTC | May 23, 04:40 UTC | 16h 34m |
| 2026-05-22 | UAE9882 | - | May 22, 06:35 UTC | May 23, 04:40 UTC | 22h 4m |
| 2026-05-22 | UAE9882 | - | May 22, 04:35 UTC | May 23, 04:30 UTC | 23h 54m |
| 2026-05-22 | UAE9882 | - | May 22, 03:15 UTC | May 23, 02:20 UTC | 23h 5m |
| 2026-05-21 | UAE9869 | HAN → DWC | May 21, 21:50 UTC | May 22, 15:00 UTC | 17h 10m |
| 2026-05-21 | UAE9868 | DWC → TPE | May 21, 04:25 UTC | May 21, 19:55 UTC | 15h 30m |
| 2026-05-21 | UAE9825 | HKG → DWC | May 21, 02:25 UTC | May 21, 02:35 UTC | 10m |
| 2026-05-20 | UAE9412 | - | May 20, 23:10 UTC | May 20, 23:30 UTC | 20m |
| 2026-05-20 | UAE9412 | - | May 20, 17:50 UTC | May 20, 20:45 UTC | 2h 55m |
| 2026-05-18 | UAE9877 | CAN → DWC | May 18, 04:40 UTC | May 18, 07:35 UTC | 2h 55m |
| 2026-05-17 | UAE9876 | DWC → CAN | May 17, 06:30 UTC | May 17, 17:35 UTC | 11h 5m |
| 2026-05-16 | UAE9876 | DWC → CAN | May 16, 18:35 UTC | May 17, 17:35 UTC | 23h 0m |
| 2026-05-16 | UAE9888 | - | May 16, 17:01 UTC | May 17, 15:31 UTC | 22h 30m |
| 2026-05-16 | UAE9888 | - | May 16, 11:55 UTC | May 17, 09:25 UTC | 21h 30m |
| 2026-05-16 | UAE9944 | LHR → DWC | May 16, 08:36 UTC | May 17, 07:00 UTC | 22h 25m |
| 2026-05-16 | UAE9944 | LHR → DWC | May 16, 06:35 UTC | May 17, 06:30 UTC | 23h 55m |
| 2026-05-16 | UAE9944 | LHR → DWC | May 16, 00:35 UTC | May 16, 19:45 UTC | 19h 11m |
| 2026-05-15 | UAE9943 | DWC → LHR | May 15, 14:35 UTC | May 15, 21:50 UTC | 7h 14m |
| 2026-05-14 | UAE9943 | DWC → LHR | May 14, 19:50 UTC | May 15, 11:55 UTC | 16h 5m |
| 2026-05-14 | UAE9943 | DWC → LHR | May 14, 14:50 UTC | May 15, 11:55 UTC | 21h 5m |
| 2026-05-14 | UAE9943 | DWC → LHR | May 14, 13:45 UTC | May 15, 11:55 UTC | 22h 10m |
| 2026-05-13 | UAE9868 | DWC → TPE | May 13, 16:35 UTC | May 14, 11:30 UTC | 18h 55m |
| 2026-05-13 | UAE9868 | DWC → TPE | May 13, 14:35 UTC | May 14, 11:30 UTC | 20h 55m |
| 2026-05-13 | UAE37N | - | May 13, 14:20 UTC | May 14, 11:30 UTC | 21h 10m |
| 2026-05-13 | UAE37N | - | May 13, 02:30 UTC | May 13, 10:35 UTC | 8h 5m |
| 2026-05-12 | UAE9917 | ORD → UIO | May 12, 15:05 UTC | May 12, 23:50 UTC | 8h 45m |
| 2026-05-12 | UAE9917 | ORD → UIO | May 12, 10:30 UTC | May 12, 12:55 UTC | 2h 25m |
| 2026-05-12 | UAE9917 | ORD → UIO | May 12, 07:25 UTC | May 12, 08:15 UTC | 50m |
| 2026-05-11 | UAE9917 | ORD → UIO | May 11, 17:40 UTC | May 11, 21:50 UTC | 4h 10m |
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-EFO page for operator, model, and routing details .