sensors Mode-S transponder
8963A1
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-EFN · BOEING 777-200LR
- Hex
- 8963A1
- Octal
- 42261641
- Decimal
- 9,003,937
- Country
- AE
- Tail
- A6-EFN
- Type
- B77L
- Flights observed
- 122
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address 8963A1 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 |
|---|---|---|---|
| UAE9841 | Emirates | 6 | 2026-05-30 |
| UAE9830 | - | 6 | 2026-05-29 |
| UAE9988 | Emirates | 5 | 2026-05-17 |
| UAE9942 | Emirates | 5 | 2026-05-28 |
| UAE9880 | Emirates | 4 | 2026-05-24 |
| UAE9655 | - | 4 | 2026-05-15 |
| UAE9921 | Emirates | 3 | 2026-04-29 |
| UAE9920 | Emirates | 3 | 2026-05-08 |
| UAE9919 | Emirates | 3 | 2026-05-07 |
| UAE9912 | Emirates | 3 | 2026-05-11 |
| UAE9911 | Emirates | 3 | 2026-05-10 |
| UAE9861 | Emirates | 3 | 2026-05-03 |
| UAE9850 | Emirates | 3 | 2026-04-21 |
| UAE9848 | Emirates | 3 | 2026-04-27 |
| UAE9846 | Emirates | 3 | 2026-05-19 |
| UAE9833 | Emirates | 3 | 2026-05-12 |
| UAE9831 | - | 3 | 2026-05-29 |
| UAE9394 | Emirates | 3 | 2026-05-21 |
| UAE9941 | - | 2 | 2026-05-27 |
| UAE9935 | Emirates | 2 | 2026-06-04 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-05 | UAE6MR | IAH → FRA | Jun 5, 11:00 UTC | Jun 5, 12:15 UTC | 1h 15m |
| 2026-06-04 | UAE9935 | FRA → MEX | Jun 4, 20:05 UTC | Jun 5, 07:25 UTC | 11h 20m |
| 2026-06-04 | UAE9935 | FRA → MEX | Jun 4, 09:55 UTC | Jun 4, 16:50 UTC | 6h 55m |
| 2026-06-04 | UAE9701 | - | Jun 4, 04:50 UTC | Jun 4, 05:30 UTC | 40m |
| 2026-06-03 | UAE9642 | - | Jun 3, 14:15 UTC | Jun 4, 02:05 UTC | 11h 50m |
| 2026-06-03 | UAE9642 | - | Jun 3, 10:15 UTC | Jun 3, 11:15 UTC | 1h 0m |
| 2026-06-03 | UAE9641 | - | Jun 3, 02:45 UTC | Jun 3, 07:05 UTC | 4h 20m |
| 2026-06-02 | UAE9640 | - | Jun 2, 09:35 UTC | Jun 2, 09:55 UTC | 20m |
| 2026-06-01 | UAE9640 | - | Jun 1, 23:05 UTC | Jun 2, 07:55 UTC | 8h 50m |
| 2026-05-31 | UAE9837 | HKG → HKG | May 31, 13:45 UTC | May 31, 16:20 UTC | 2h 35m |
| 2026-05-31 | UAE9836 | DWC → HKG | May 31, 10:05 UTC | May 31, 10:25 UTC | 20m |
| 2026-05-30 | UAE9841 | HKG → DWC | May 30, 17:50 UTC | May 30, 22:55 UTC | 5h 5m |
| 2026-05-30 | UAE9841 | HKG → DWC | May 30, 17:10 UTC | May 30, 17:20 UTC | 10m |
| 2026-05-29 | UAE9840 | DWC → HKG | May 29, 22:30 UTC | May 30, 14:35 UTC | 16h 5m |
| 2026-05-29 | UAE9831 | - | May 29, 21:45 UTC | May 29, 21:55 UTC | 10m |
| 2026-05-29 | UAE9830 | - | May 29, 00:25 UTC | May 29, 19:20 UTC | 18h 55m |
| 2026-05-28 | UAE9830 | - | May 28, 22:20 UTC | May 29, 19:20 UTC | 21h 0m |
| 2026-05-28 | UAE9830 | - | May 28, 20:20 UTC | May 29, 19:20 UTC | 23h 0m |
| 2026-05-28 | UAE9942 | JFK → AMS | May 28, 18:55 UTC | May 29, 17:00 UTC | 22h 6m |
| 2026-05-28 | UAE9942 | JFK → AMS | May 28, 06:05 UTC | May 28, 14:20 UTC | 8h 15m |
| 2026-05-28 | UAE9942 | JFK → AMS | May 28, 03:00 UTC | May 28, 03:35 UTC | 35m |
| 2026-05-28 | UAE9942 | JFK → AMS | May 28, 00:30 UTC | May 28, 00:40 UTC | 10m |
| 2026-05-27 | UAE9942 | JFK → AMS | May 27, 15:40 UTC | May 27, 21:40 UTC | 6h 0m |
| 2026-05-27 | UAE9941 | - | May 27, 10:30 UTC | May 27, 12:55 UTC | 2h 25m |
| 2026-05-27 | UAE9941 | - | May 27, 06:55 UTC | May 27, 08:30 UTC | 1h 35m |
| 2026-05-25 | UAE9879 | PVG → DWC | May 25, 10:40 UTC | May 26, 03:19 UTC | 16h 39m |
| 2026-05-25 | UAE9879 | PVG → DWC | May 25, 04:20 UTC | May 26, 03:19 UTC | 23h 0m |
| 2026-05-25 | UAE9878 | DWC → PVG | May 25, 03:25 UTC | May 26, 01:24 UTC | 22h 0m |
| 2026-05-24 | UAE9878 | DWC → PVG | May 24, 14:20 UTC | May 25, 13:40 UTC | 23h 20m |
| 2026-05-24 | UAE9880 | DWC → HKG | May 24, 12:20 UTC | May 25, 11:25 UTC | 23h 5m |
| 2026-05-24 | UAE9880 | DWC → HKG | May 24, 11:50 UTC | May 25, 04:20 UTC | 16h 30m |
| 2026-05-24 | UAE9880 | DWC → HKG | May 24, 04:50 UTC | May 25, 04:15 UTC | 23h 25m |
| 2026-05-24 | UAE9700 | - | May 24, 01:25 UTC | May 24, 02:10 UTC | 45m |
| 2026-05-22 | UAE9841 | HKG → DWC | May 22, 13:15 UTC | May 22, 17:05 UTC | 3h 50m |
| 2026-05-22 | UAE9841 | HKG → DWC | May 22, 11:20 UTC | May 22, 11:35 UTC | 15m |
| 2026-05-21 | UAE9394 | BRU → DWC | May 21, 14:45 UTC | May 22, 08:50 UTC | 18h 5m |
| 2026-05-21 | UAE9394 | BRU → DWC | May 21, 10:20 UTC | May 22, 08:50 UTC | 22h 30m |
| 2026-05-21 | UAE9394 | BRU → DWC | May 21, 09:10 UTC | May 22, 08:15 UTC | 23h 5m |
| 2026-05-20 | UAE9393 | BRU → ORD | May 20, 21:15 UTC | May 21, 05:50 UTC | 8h 35m |
| 2026-05-20 | UAE9393 | BRU → ORD | May 20, 03:30 UTC | May 20, 19:20 UTC | 15h 51m |
| 2026-05-20 | UAE9831 | - | May 20, 01:25 UTC | May 20, 01:40 UTC | 15m |
| 2026-05-19 | UAE9830 | - | May 19, 07:45 UTC | May 19, 23:00 UTC | 15h 15m |
| 2026-05-19 | UAE9847 | JFK → DXB | May 19, 05:40 UTC | May 19, 05:55 UTC | 15m |
| 2026-05-19 | UAE9846 | HKG → TOL | May 19, 02:40 UTC | May 19, 03:00 UTC | 20m |
| 2026-05-18 | UAE9846 | HKG → TOL | May 18, 21:25 UTC | May 19, 00:10 UTC | 2h 45m |
| 2026-05-18 | UAE9846 | HKG → TOL | May 18, 20:05 UTC | May 18, 20:25 UTC | 20m |
| 2026-05-17 | UAE9816 | DWC → AMD | May 17, 16:55 UTC | May 18, 04:40 UTC | 11h 45m |
| 2026-05-17 | UAE9988 | ORD → DWC | May 17, 08:20 UTC | May 18, 04:40 UTC | 20h 20m |
| 2026-05-17 | UAE9988 | ORD → DWC | May 17, 06:20 UTC | May 18, 04:40 UTC | 22h 20m |
| 2026-05-17 | UAE9988 | ORD → DWC | May 17, 05:10 UTC | May 18, 04:15 UTC | 23h 5m |
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-EFN page for operator, model, and routing details .