sensors Mode-S transponder
8965B9
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-EFU · BOEING 777-200LR
- Hex
- 8965B9
- Octal
- 42262671
- Decimal
- 9,004,473
- Country
- AE
- Tail
- A6-EFU
- Type
- B77L
- Flights observed
- 147
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 1h ago
Current position
Country allocation
The ICAO 24-bit address 8965B9 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 |
|---|---|---|---|
| UAE9657 | - | 9 | 2026-05-30 |
| UAE9917 | Emirates | 8 | 2026-04-14 |
| UAE9878 | Emirates | 7 | 2026-05-18 |
| UAE9793 | Emirates | 6 | 2026-05-23 |
| UAE9912 | Emirates | 5 | 2026-05-25 |
| UAE9911 | Emirates | 5 | 2026-05-24 |
| UAE37N | - | 5 | 2026-04-15 |
| UAE9903 | Emirates | 4 | 2026-05-16 |
| UAE9882 | - | 4 | 2026-05-08 |
| UAE9869 | Emirates | 4 | 2026-04-17 |
| UAE9868 | Emirates | 4 | 2026-04-16 |
| UAE9811 | - | 4 | 2026-05-01 |
| UAE9620 | Emirates | 4 | 2026-05-04 |
| UAE9393 | Emirates | 4 | 2026-05-07 |
| UAE9314 | - | 4 | 2026-04-29 |
| UAE9964 | Emirates | 3 | 2026-05-28 |
| UAE9963 | Emirates | 3 | 2026-05-28 |
| UAE9915 | Emirates | 3 | 2026-05-10 |
| UAE9863 | - | 3 | 2026-04-13 |
| UAE9849 | Emirates | 3 | 2026-04-20 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | UAE9657 | - | May 30, 02:55 UTC | May 30, 04:15 UTC | 1h 20m |
| 2026-05-29 | UAE9657 | - | May 29, 17:20 UTC | May 29, 17:40 UTC | 20m |
| 2026-05-28 | UAE9964 | FRA → DWC | May 28, 20:20 UTC | May 29, 14:55 UTC | 18h 35m |
| 2026-05-28 | UAE9964 | FRA → DWC | May 28, 19:15 UTC | May 29, 14:55 UTC | 19h 40m |
| 2026-05-28 | UAE9964 | FRA → DWC | May 28, 10:30 UTC | May 28, 23:50 UTC | 13h 20m |
| 2026-05-28 | UAE9963 | DXB → DFW | May 28, 04:45 UTC | May 28, 07:30 UTC | 2h 45m |
| 2026-05-27 | UAE9963 | DXB → DFW | May 27, 15:30 UTC | May 28, 01:30 UTC | 10h 0m |
| 2026-05-26 | UAE9963 | DXB → DFW | May 26, 17:15 UTC | May 27, 11:00 UTC | 17h 45m |
| 2026-05-26 | UAE9833 | HKG → DXB | May 26, 15:20 UTC | May 26, 15:35 UTC | 15m |
| 2026-05-26 | UAE9832 | DWC → HKG | May 26, 12:00 UTC | May 26, 12:24 UTC | 25m |
| 2026-05-25 | UAE9912 | MAD → MXP | May 25, 16:00 UTC | May 26, 09:55 UTC | 17h 54m |
| 2026-05-25 | UAE9912 | MAD → MXP | May 25, 05:00 UTC | May 25, 12:40 UTC | 7h 40m |
| 2026-05-24 | UAE9911 | LOS → GRU | May 24, 15:45 UTC | May 24, 20:20 UTC | 4h 35m |
| 2026-05-24 | UAE9911 | LOS → GRU | May 24, 11:40 UTC | May 24, 13:05 UTC | 1h 25m |
| 2026-05-23 | UAE9911 | LOS → GRU | May 23, 14:20 UTC | May 24, 13:05 UTC | 22h 45m |
| 2026-05-23 | UAE9793 | HKG → HKG | May 23, 13:55 UTC | May 24, 12:15 UTC | 22h 20m |
| 2026-05-23 | UAE9793 | HKG → HKG | May 23, 10:50 UTC | May 23, 14:45 UTC | 3h 55m |
| 2026-05-23 | UAE9793 | HKG → HKG | May 23, 08:55 UTC | May 23, 09:10 UTC | 15m |
| 2026-05-23 | UAE9792 | - | May 23, 06:20 UTC | May 23, 06:55 UTC | 35m |
| 2026-05-22 | UAE9656 | - | May 22, 13:40 UTC | May 23, 03:55 UTC | 14h 14m |
| 2026-05-22 | UAE9656 | - | May 22, 09:25 UTC | May 22, 10:25 UTC | 1h 0m |
| 2026-05-21 | UAE9655 | - | May 21, 15:30 UTC | May 22, 07:35 UTC | 16h 5m |
| 2026-05-20 | UAE9655 | - | May 20, 20:10 UTC | May 21, 16:05 UTC | 19h 55m |
| 2026-05-20 | UAE9891 | - | May 20, 14:25 UTC | May 20, 20:15 UTC | 5h 50m |
| 2026-05-20 | UAE9890 | - | May 20, 10:35 UTC | May 20, 10:45 UTC | 10m |
| 2026-05-19 | UAE9833 | HKG → DXB | May 19, 20:40 UTC | May 20, 00:40 UTC | 4h 0m |
| 2026-05-19 | UAE9833 | HKG → DXB | May 19, 18:40 UTC | May 19, 18:55 UTC | 15m |
| 2026-05-19 | UAE9832 | DWC → HKG | May 19, 15:25 UTC | May 19, 15:45 UTC | 20m |
| 2026-05-19 | UAE9879 | PVG → DWC | May 19, 01:50 UTC | May 19, 13:00 UTC | 11h 10m |
| 2026-05-18 | UAE9879 | PVG → DWC | May 18, 14:20 UTC | May 19, 13:00 UTC | 22h 39m |
| 2026-05-18 | UAE9878 | DWC → PVG | May 18, 12:20 UTC | May 19, 11:00 UTC | 22h 39m |
| 2026-05-18 | UAE9878 | DWC → PVG | May 18, 11:50 UTC | May 19, 04:45 UTC | 16h 54m |
| 2026-05-18 | UAE9878 | DWC → PVG | May 18, 06:20 UTC | May 19, 04:45 UTC | 22h 24m |
| 2026-05-18 | UAE9878 | DWC → PVG | May 18, 06:01 UTC | May 19, 04:15 UTC | 22h 14m |
| 2026-05-18 | UAE9878 | DWC → PVG | May 18, 03:25 UTC | May 19, 02:10 UTC | 22h 44m |
| 2026-05-17 | UAE9878 | DWC → PVG | May 17, 16:20 UTC | May 18, 14:35 UTC | 22h 15m |
| 2026-05-17 | UAE9878 | DWC → PVG | May 17, 14:50 UTC | May 18, 14:15 UTC | 23h 25m |
| 2026-05-16 | UAE9903 | FRA → DWC | May 16, 22:20 UTC | May 17, 16:55 UTC | 18h 35m |
| 2026-05-16 | UAE9903 | FRA → DWC | May 16, 20:30 UTC | May 17, 16:55 UTC | 20h 25m |
| 2026-05-16 | UAE9903 | FRA → DWC | May 16, 17:35 UTC | May 16, 18:10 UTC | 35m |
| 2026-05-15 | UAE9903 | FRA → DWC | May 15, 23:40 UTC | May 16, 15:31 UTC | 15h 51m |
| 2026-05-15 | UAE9831 | - | May 15, 21:40 UTC | May 15, 21:55 UTC | 15m |
| 2026-05-15 | UAE9830 | - | May 15, 18:55 UTC | May 15, 19:15 UTC | 20m |
| 2026-05-15 | UAE9830 | - | May 15, 01:00 UTC | May 15, 16:35 UTC | 15h 34m |
| 2026-05-14 | UAE9881 | HKG → HKG | May 14, 06:10 UTC | May 14, 20:45 UTC | 14h 35m |
| 2026-05-13 | UAE9881 | HKG → HKG | May 13, 16:30 UTC | May 14, 09:35 UTC | 17h 5m |
| 2026-05-13 | UAE9880 | DWC → HKG | May 13, 15:15 UTC | May 13, 15:35 UTC | 20m |
| 2026-05-13 | UAE9873 | PVG → DWC | May 13, 05:10 UTC | May 13, 11:00 UTC | 5h 50m |
| 2026-05-12 | UAE9872 | DWC → PVG | May 12, 09:25 UTC | May 12, 23:40 UTC | 14h 15m |
| 2026-05-11 | UAE21U | AMS → DWC | May 11, 11:20 UTC | May 11, 17:15 UTC | 5h 55m |
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-EFU page for operator, model, and routing details .