sensors Mode-S transponder
8966F0
ICAO 24-bit transponder address · allocated to United Arab Emirates
- Hex
- 8966F0
- Octal
- 42263360
- Decimal
- 9,004,784
- Country
- AE
- Flights observed
- 117
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address 8966F0 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 |
|---|---|---|---|
| UAE9901 | Emirates | 7 | 2026-05-13 |
| UAE9917 | Emirates | 5 | 2026-05-05 |
| UAE9394 | Emirates | 5 | 2026-05-24 |
| UAE9846 | Emirates | 4 | 2026-05-15 |
| UAE9393 | Emirates | 4 | 2026-05-23 |
| BOE476 | - | 4 | 2026-04-19 |
| UAE9988 | Emirates | 3 | 2026-06-07 |
| UAE9905 | Emirates | 3 | 2026-05-20 |
| UAE9902 | Emirates | 3 | 2026-05-14 |
| UAE9851 | Emirates | 3 | 2026-05-25 |
| UAE9841 | Emirates | 3 | 2026-05-29 |
| UAE9833 | Emirates | 3 | 2026-05-02 |
| UAE9832 | Emirates | 3 | 2026-06-08 |
| UAE9831 | - | 3 | 2026-04-29 |
| UAE9785 | Emirates | 3 | 2026-06-04 |
| UAE9784 | Emirates | 3 | 2026-06-04 |
| UAE9710 | - | 3 | 2026-06-07 |
| UAE9656 | - | 3 | 2026-06-03 |
| UAE9642 | - | 3 | 2026-05-27 |
| UAE9640 | - | 3 | 2026-05-26 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-08 | UAE9832 | DWC → HKG | Jun 8, 13:25 UTC | Jun 9, 09:10 UTC | 19h 45m |
| 2026-06-07 | UAE9710 | - | Jun 7, 23:40 UTC | Jun 8, 10:50 UTC | 11h 10m |
| 2026-06-07 | UAE9988 | ORD → DWC | Jun 7, 04:55 UTC | Jun 7, 20:10 UTC | 15h 15m |
| 2026-06-07 | UAE9988 | ORD → DWC | Jun 7, 00:05 UTC | Jun 7, 20:10 UTC | 20h 5m |
| 2026-06-06 | UAE9988 | ORD → DWC | Jun 6, 23:00 UTC | Jun 7, 20:10 UTC | 21h 10m |
| 2026-06-06 | UAE9987 | AMS → ORD | Jun 6, 11:19 UTC | Jun 6, 19:19 UTC | 8h 0m |
| 2026-06-05 | UAE9987 | AMS → ORD | Jun 5, 15:45 UTC | Jun 6, 08:35 UTC | 16h 50m |
| 2026-06-04 | UAE9385 | DWC → LGG | Jun 4, 19:55 UTC | Jun 5, 11:05 UTC | 15h 10m |
| 2026-06-04 | UAE9785 | HKG → DWC | Jun 4, 17:55 UTC | Jun 4, 18:10 UTC | 15m |
| 2026-06-04 | UAE9784 | DWC → HKG | Jun 4, 08:40 UTC | Jun 4, 15:40 UTC | 7h 0m |
| 2026-06-03 | UAE9835 | HKG → DWC | Jun 3, 23:45 UTC | Jun 4, 05:00 UTC | 5h 15m |
| 2026-06-03 | UAE9835 | HKG → DWC | Jun 3, 23:05 UTC | Jun 3, 23:15 UTC | 10m |
| 2026-06-03 | UAE9708 | - | Jun 3, 11:05 UTC | Jun 3, 19:30 UTC | 8h 25m |
| 2026-06-03 | UAE9656 | - | Jun 3, 02:45 UTC | Jun 3, 06:00 UTC | 3h 15m |
| 2026-06-02 | UAE9656 | - | Jun 2, 15:25 UTC | Jun 3, 00:20 UTC | 8h 55m |
| 2026-06-02 | UAE9656 | - | Jun 2, 08:45 UTC | Jun 2, 10:55 UTC | 2h 10m |
| 2026-06-01 | UAE9989 | LCK → ORD | Jun 1, 20:20 UTC | Jun 2, 04:00 UTC | 7h 40m |
| 2026-05-31 | UAE9989 | LCK → ORD | May 31, 23:55 UTC | Jun 1, 18:00 UTC | 18h 5m |
| 2026-05-31 | UAE9716 | - | May 31, 09:45 UTC | May 31, 20:30 UTC | 10h 45m |
| 2026-05-30 | UAE9807 | - | May 30, 12:40 UTC | May 30, 21:40 UTC | 9h 0m |
| 2026-05-30 | UAE9806 | - | May 30, 07:00 UTC | May 30, 10:05 UTC | 3h 5m |
| 2026-05-29 | UAE9841 | HKG → DWC | May 29, 08:10 UTC | May 30, 08:00 UTC | 23h 50m |
| 2026-05-29 | UAE9841 | HKG → DWC | May 29, 05:05 UTC | May 29, 09:00 UTC | 3h 55m |
| 2026-05-29 | UAE9841 | HKG → DWC | May 29, 03:10 UTC | May 29, 03:20 UTC | 10m |
| 2026-05-28 | UAE9840 | DWC → HKG | May 28, 19:00 UTC | May 29, 00:50 UTC | 5h 50m |
| 2026-05-28 | UAE9840 | DWC → HKG | May 28, 04:25 UTC | May 29, 00:50 UTC | 20h 25m |
| 2026-05-27 | UAE9642 | - | May 27, 14:05 UTC | May 28, 02:00 UTC | 11h 55m |
| 2026-05-27 | UAE9642 | - | May 27, 10:35 UTC | May 27, 11:30 UTC | 55m |
| 2026-05-27 | UAE9641 | - | May 27, 03:09 UTC | May 27, 07:40 UTC | 4h 30m |
| 2026-05-26 | UAE9640 | - | May 26, 10:05 UTC | May 26, 10:34 UTC | 30m |
| 2026-05-25 | UAE9640 | - | May 25, 12:50 UTC | May 26, 07:45 UTC | 18h 54m |
| 2026-05-25 | UAE9851 | HKG → DWC | May 25, 10:15 UTC | May 26, 07:45 UTC | 21h 29m |
| 2026-05-25 | UAE9851 | HKG → DWC | May 25, 09:45 UTC | May 26, 07:45 UTC | 21h 59m |
| 2026-05-25 | UAE9851 | HKG → DWC | May 25, 07:50 UTC | May 25, 08:00 UTC | 10m |
| 2026-05-25 | UAE9850 | DXB → TPE | May 25, 05:00 UTC | May 25, 05:35 UTC | 35m |
| 2026-05-24 | UAE9394 | BRU → DWC | May 24, 12:45 UTC | May 25, 02:50 UTC | 14h 5m |
| 2026-05-24 | UAE9394 | BRU → DWC | May 24, 06:25 UTC | May 25, 02:50 UTC | 20h 25m |
| 2026-05-23 | UAE9393 | BRU → ORD | May 23, 18:45 UTC | May 24, 03:00 UTC | 8h 15m |
| 2026-05-23 | UAE9393 | BRU → ORD | May 23, 08:15 UTC | May 23, 15:05 UTC | 6h 50m |
| 2026-05-22 | UAE9386 | - | May 22, 20:20 UTC | May 23, 02:30 UTC | 6h 10m |
| 2026-05-22 | UAE9385 | DWC → LGG | May 22, 02:10 UTC | May 22, 16:15 UTC | 14h 5m |
| 2026-05-22 | UAE9785 | HKG → DWC | May 22, 00:05 UTC | May 22, 00:20 UTC | 15m |
| 2026-05-21 | UAE9784 | DWC → HKG | May 21, 13:55 UTC | May 21, 19:35 UTC | 5h 40m |
| 2026-05-20 | UAE9784 | DWC → HKG | May 20, 18:05 UTC | May 21, 17:05 UTC | 23h 0m |
| 2026-05-20 | UAE9905 | OSL → DWC | May 20, 16:05 UTC | May 21, 14:35 UTC | 22h 30m |
| 2026-05-20 | UAE9905 | OSL → DWC | May 20, 14:05 UTC | May 21, 14:00 UTC | 23h 55m |
| 2026-05-20 | UAE9905 | OSL → DWC | May 20, 09:15 UTC | May 20, 11:00 UTC | 1h 45m |
| 2026-05-19 | UAE9961 | DWC → ORD | May 19, 15:20 UTC | May 20, 06:30 UTC | 15h 11m |
| 2026-05-19 | UAE9785 | HKG → DWC | May 19, 12:20 UTC | May 19, 12:35 UTC | 15m |
| 2026-05-18 | UAE9956 | ZAZ → DWC | May 18, 17:10 UTC | May 19, 09:45 UTC | 16h 34m |
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.