sensors Mode-S transponder
8966EF
ICAO 24-bit transponder address · allocated to United Arab Emirates
- Hex
- 8966EF
- Octal
- 42263357
- Decimal
- 9,004,783
- Country
- AE
- Flights observed
- 123
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 3h ago
Current position
Country allocation
The ICAO 24-bit address 8966EF 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 |
|---|---|---|---|
| UAE9903 | Emirates | 13 | 2026-06-06 |
| UAE9917 | Emirates | 12 | 2026-06-09 |
| UAE9394 | Emirates | 8 | 2026-06-04 |
| UAE9393 | Emirates | 6 | 2026-06-04 |
| UAE9989 | Emirates | 5 | 2026-05-12 |
| UAE9785 | Emirates | 5 | 2026-05-14 |
| UAE9784 | Emirates | 5 | 2026-05-14 |
| UAE9849 | Emirates | 4 | 2026-06-08 |
| UAE9422 | - | 4 | 2026-05-07 |
| UAE9901 | Emirates | 3 | 2026-05-27 |
| UAE9858 | - | 3 | 2026-05-06 |
| UAE9835 | Emirates | 3 | 2026-05-13 |
| UAE9656 | - | 3 | 2026-05-13 |
| UAE9423 | - | 3 | 2026-04-29 |
| UAE9385 | Emirates | 3 | 2026-05-14 |
| BOE435 | - | 3 | 2026-04-17 |
| UAE9990 | Emirates | 2 | 2026-05-05 |
| UAE9902 | Emirates | 2 | 2026-05-28 |
| UAE9861 | Emirates | 2 | 2026-05-17 |
| UAE9860 | Emirates | 2 | 2026-05-16 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-09 | UAE9917 | ORD → UIO | Jun 9, 02:25 UTC | Jun 9, 10:20 UTC | 7h 55m |
| 2026-06-08 | UAE9917 | ORD → UIO | Jun 8, 10:10 UTC | Jun 9, 00:10 UTC | 14h 0m |
| 2026-06-08 | UAE9849 | CAN → DWC | Jun 8, 07:10 UTC | Jun 8, 09:00 UTC | 1h 50m |
| 2026-06-08 | UAE9849 | CAN → DWC | Jun 8, 05:10 UTC | Jun 8, 05:25 UTC | 15m |
| 2026-06-07 | UAE9848 | DWC → CAN | Jun 7, 09:20 UTC | Jun 7, 23:55 UTC | 14h 35m |
| 2026-06-07 | UAE9710 | - | Jun 7, 06:30 UTC | Jun 7, 06:50 UTC | 20m |
| 2026-06-06 | UAE9903 | FRA → DWC | Jun 6, 18:50 UTC | Jun 7, 05:40 UTC | 10h 50m |
| 2026-06-06 | UAE9903 | FRA → DWC | Jun 6, 15:19 UTC | Jun 6, 16:04 UTC | 45m |
| 2026-06-05 | UAE9903 | FRA → DWC | Jun 5, 17:50 UTC | Jun 6, 12:10 UTC | 18h 20m |
| 2026-06-05 | UAE9903 | FRA → DWC | Jun 5, 17:30 UTC | Jun 6, 12:10 UTC | 18h 40m |
| 2026-06-05 | UAE9903 | FRA → DWC | Jun 5, 13:55 UTC | Jun 6, 12:10 UTC | 22h 15m |
| 2026-06-05 | UAE9903 | FRA → DWC | Jun 5, 13:20 UTC | Jun 6, 11:45 UTC | 22h 25m |
| 2026-06-04 | UAE9394 | BRU → DWC | Jun 4, 21:50 UTC | Jun 5, 21:25 UTC | 23h 35m |
| 2026-06-04 | UAE9394 | BRU → DWC | Jun 4, 19:50 UTC | Jun 5, 19:45 UTC | 23h 55m |
| 2026-06-04 | UAE9394 | BRU → DWC | Jun 4, 18:50 UTC | Jun 5, 17:45 UTC | 22h 55m |
| 2026-06-04 | UAE9394 | BRU → DWC | Jun 4, 13:50 UTC | Jun 5, 13:35 UTC | 23h 45m |
| 2026-06-04 | UAE9394 | BRU → DWC | Jun 4, 12:50 UTC | Jun 4, 23:30 UTC | 10h 40m |
| 2026-06-04 | UAE9393 | BRU → ORD | Jun 4, 00:55 UTC | Jun 4, 09:10 UTC | 8h 15m |
| 2026-06-03 | UAE9393 | BRU → ORD | Jun 3, 05:10 UTC | Jun 3, 21:40 UTC | 16h 30m |
| 2026-06-03 | UAE9831 | - | Jun 3, 03:00 UTC | Jun 3, 03:10 UTC | 10m |
| 2026-06-03 | UAE9830 | - | Jun 3, 00:40 UTC | Jun 3, 01:10 UTC | 30m |
| 2026-06-02 | UAE9830 | - | Jun 2, 19:00 UTC | Jun 2, 21:25 UTC | 2h 25m |
| 2026-05-31 | UAE9795 | - | May 31, 15:20 UTC | May 31, 15:35 UTC | 15m |
| 2026-05-31 | UAE9794 | DWC → ICN | May 31, 12:25 UTC | May 31, 12:45 UTC | 20m |
| 2026-05-30 | UAE9903 | FRA → DWC | May 30, 19:40 UTC | May 31, 01:11 UTC | 5h 31m |
| 2026-05-30 | UAE9903 | FRA → DWC | May 30, 15:30 UTC | May 30, 16:05 UTC | 35m |
| 2026-05-29 | UAE9903 | FRA → DWC | May 29, 18:55 UTC | May 30, 12:00 UTC | 17h 5m |
| 2026-05-29 | UAE9903 | FRA → DWC | May 29, 16:00 UTC | May 30, 12:00 UTC | 20h 0m |
| 2026-05-29 | UAE9903 | FRA → DWC | May 29, 14:50 UTC | May 30, 11:45 UTC | 20h 55m |
| 2026-05-29 | UAE9853 | HAN → DWC | May 29, 14:05 UTC | May 29, 14:15 UTC | 10m |
| 2026-05-29 | UAE9852 | DWC → HAN | May 29, 11:05 UTC | May 29, 11:50 UTC | 45m |
| 2026-05-28 | UAE9902 | LHR → DWC | May 28, 16:25 UTC | May 29, 08:55 UTC | 16h 30m |
| 2026-05-27 | UAE9901 | BHX → FRA | May 27, 18:15 UTC | May 28, 12:30 UTC | 18h 15m |
| 2026-05-27 | UAE37N | - | May 27, 04:04 UTC | May 27, 12:15 UTC | 8h 11m |
| 2026-05-26 | UAE9917 | ORD → UIO | May 26, 16:35 UTC | May 27, 01:09 UTC | 8h 35m |
| 2026-05-26 | UAE9917 | ORD → UIO | May 26, 11:44 UTC | May 26, 14:30 UTC | 2h 45m |
| 2026-05-26 | UAE9917 | ORD → UIO | May 26, 00:35 UTC | May 26, 09:09 UTC | 8h 35m |
| 2026-05-25 | UAE9917 | ORD → UIO | May 25, 17:35 UTC | May 25, 21:54 UTC | 4h 20m |
| 2026-05-24 | UAE9917 | ORD → UIO | May 24, 23:10 UTC | May 25, 21:45 UTC | 22h 35m |
| 2026-05-24 | UAE9917 | ORD → UIO | May 24, 19:50 UTC | May 25, 19:44 UTC | 23h 55m |
| 2026-05-24 | UAE9716 | - | May 24, 18:35 UTC | May 25, 17:45 UTC | 23h 10m |
| 2026-05-24 | UAE9716 | - | May 24, 09:45 UTC | May 24, 23:10 UTC | 13h 25m |
| 2026-05-23 | UAE9903 | FRA → DWC | May 23, 18:25 UTC | May 24, 07:00 UTC | 12h 35m |
| 2026-05-23 | UAE9903 | FRA → DWC | May 23, 14:15 UTC | May 23, 14:55 UTC | 40m |
| 2026-05-22 | UAE9906 | MAD → DWC | May 22, 18:10 UTC | May 23, 11:45 UTC | 17h 34m |
| 2026-05-22 | UAE9391 | DWC → DWC | May 22, 09:05 UTC | May 22, 13:25 UTC | 4h 20m |
| 2026-05-22 | UAE9391 | DWC → DWC | May 22, 06:05 UTC | May 22, 06:15 UTC | 10m |
| 2026-05-21 | UAE9902 | LHR → DWC | May 21, 15:55 UTC | May 21, 22:05 UTC | 6h 10m |
| 2026-05-20 | UAE9901 | BHX → FRA | May 20, 17:50 UTC | May 21, 12:10 UTC | 18h 20m |
| 2026-05-20 | UAE9901 | BHX → FRA | May 20, 16:40 UTC | May 21, 12:10 UTC | 19h 30m |
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.