sensors Mode-S transponder
8960DC
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-EBU · BOEING 777-300ER
- Hex
- 8960DC
- Octal
- 42260334
- Decimal
- 9,003,228
- Country
- AE
- Tail
- A6-EBU
- Type
- B77W
- Flights observed
- 80
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 1h ago
Current position
Country allocation
The ICAO 24-bit address 8960DC 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 |
|---|---|---|---|
| UAE333 | Emirates | 12 | 2026-04-18 |
| UAE332 | Emirates | 12 | 2026-04-18 |
| UAE583 | Emirates | 6 | 2026-04-19 |
| UAE9U | Emirates | 5 | 2026-04-18 |
| UAE9989 | Emirates | 3 | 2026-05-28 |
| UAE9974 | Emirates | 3 | 2026-05-07 |
| UAE9966 | Emirates | 3 | 2026-05-28 |
| UAE9973 | Emirates | 2 | 2026-05-07 |
| UAE9965 | - | 2 | 2026-05-27 |
| UAE9940 | Emirates | 2 | 2026-05-20 |
| UAE9818 | - | 2 | 2026-05-08 |
| UAE9398 | - | 2 | 2026-05-11 |
| UAE9397 | - | 2 | 2026-05-11 |
| UAE508 | Emirates | 2 | 2026-04-17 |
| UAE2584 | - | 2 | 2026-05-21 |
| UAE9978 | Emirates | 1 | 2026-05-15 |
| UAE9977 | Emirates | 1 | 2026-05-15 |
| UAE9964 | Emirates | 1 | 2026-04-24 |
| UAE9963 | Emirates | 1 | 2026-04-24 |
| UAE9928 | Emirates | 1 | 2026-05-30 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | UAE9869 | HAN → DWC | May 30, 05:20 UTC | May 30, 19:50 UTC | 14h 30m |
| 2026-05-30 | UAE9928 | DWC → HKG | May 30, 02:30 UTC | May 30, 02:40 UTC | 10m |
| 2026-05-29 | UAE7GV | AMS → DWC | May 29, 12:10 UTC | May 30, 01:55 UTC | 13h 45m |
| 2026-05-28 | UAE9989 | LCK → ORD | May 28, 13:05 UTC | May 29, 07:25 UTC | 18h 20m |
| 2026-05-28 | UAE9989 | LCK → ORD | May 28, 11:05 UTC | May 29, 07:25 UTC | 20h 20m |
| 2026-05-28 | UAE9989 | LCK → ORD | May 28, 09:35 UTC | May 29, 07:25 UTC | 21h 50m |
| 2026-05-28 | UAE9966 | JFK → DWC | May 28, 03:05 UTC | May 29, 03:00 UTC | 23h 55m |
| 2026-05-28 | UAE9966 | JFK → DWC | May 28, 02:10 UTC | May 28, 16:40 UTC | 14h 30m |
| 2026-05-27 | UAE9966 | JFK → DWC | May 27, 22:20 UTC | May 27, 23:05 UTC | 45m |
| 2026-05-27 | UAE9965 | - | May 27, 09:50 UTC | May 27, 20:15 UTC | 10h 25m |
| 2026-05-27 | UAE9965 | - | May 27, 03:04 UTC | May 27, 07:20 UTC | 4h 16m |
| 2026-05-22 | UAE9650 | - | May 22, 20:45 UTC | May 22, 21:00 UTC | 15m |
| 2026-05-21 | UAE2585 | - | May 21, 16:30 UTC | May 21, 20:55 UTC | 4h 25m |
| 2026-05-21 | UAE2584 | - | May 21, 14:25 UTC | May 21, 14:45 UTC | 20m |
| 2026-05-21 | UAE2584 | - | May 21, 09:55 UTC | May 21, 11:20 UTC | 1h 25m |
| 2026-05-20 | UAE9940 | IAH → AMS | May 20, 13:45 UTC | May 21, 11:20 UTC | 21h 35m |
| 2026-05-20 | UAE9940 | IAH → AMS | May 20, 09:50 UTC | May 20, 15:50 UTC | 6h 0m |
| 2026-05-20 | UAE9927 | MAD → DWC | May 20, 07:35 UTC | May 20, 08:10 UTC | 35m |
| 2026-05-18 | UAE9731 | - | May 18, 16:50 UTC | May 18, 19:55 UTC | 3h 4m |
| 2026-05-18 | UAE9730 | ADD → DWC | May 18, 12:05 UTC | May 18, 14:25 UTC | 2h 20m |
| 2026-05-15 | UAE9978 | FRA → DXB | May 15, 13:20 UTC | May 15, 19:50 UTC | 6h 29m |
| 2026-05-15 | UAE9977 | MAD → DWC | May 15, 02:35 UTC | May 15, 10:10 UTC | 7h 35m |
| 2026-05-11 | UAE9398 | - | May 11, 14:25 UTC | May 11, 20:25 UTC | 6h 1m |
| 2026-05-11 | UAE9397 | - | May 11, 02:45 UTC | May 11, 09:20 UTC | 6h 35m |
| 2026-05-08 | UAE9818 | - | May 8, 10:44 UTC | May 8, 19:25 UTC | 8h 40m |
| 2026-05-07 | UAE9818 | - | May 7, 20:25 UTC | May 8, 17:50 UTC | 21h 25m |
| 2026-05-07 | UAE9974 | FRA → DXB | May 7, 17:05 UTC | May 8, 17:00 UTC | 23h 55m |
| 2026-05-07 | UAE9974 | FRA → DXB | May 7, 15:20 UTC | May 8, 12:30 UTC | 21h 9m |
| 2026-05-07 | UAE9973 | DXB → FRA | May 7, 04:40 UTC | May 7, 08:35 UTC | 3h 55m |
| 2026-05-05 | UAE9398 | - | May 5, 14:20 UTC | May 5, 19:55 UTC | 5h 35m |
| 2026-05-05 | UAE9397 | - | May 5, 08:20 UTC | May 5, 09:35 UTC | 1h 15m |
| 2026-04-29 | UAE9974 | FRA → DXB | Apr 29, 04:44 UTC | Apr 29, 10:50 UTC | 6h 6m |
| 2026-04-28 | UAE9973 | DXB → FRA | Apr 28, 12:30 UTC | Apr 28, 20:00 UTC | 7h 30m |
| 2026-04-27 | UAE309 | PEK → DXB | Apr 27, 08:35 UTC | Apr 27, 08:55 UTC | 20m |
| 2026-04-26 | UAE308 | DXB → PEK | Apr 26, 12:05 UTC | Apr 26, 12:25 UTC | 20m |
| 2026-04-24 | UAE9964 | FRA → DWC | Apr 24, 10:20 UTC | Apr 24, 17:05 UTC | 6h 45m |
| 2026-04-24 | UAE9963 | DXB → DFW | Apr 24, 00:00 UTC | Apr 24, 07:40 UTC | 7h 40m |
| 2026-04-22 | UAE2507 | DXB → DME | Apr 22, 08:05 UTC | Apr 22, 08:30 UTC | 25m |
| 2026-04-21 | UAE720 | NBO → DXB | Apr 21, 13:45 UTC | Apr 21, 14:15 UTC | 30m |
| 2026-04-20 | UAE719 | DXB → NBO | Apr 20, 06:50 UTC | Apr 20, 07:15 UTC | 25m |
| 2026-04-19 | UAE583 | DAC → DXB | Apr 19, 08:50 UTC | Apr 19, 09:10 UTC | 20m |
| 2026-04-19 | UAE583 | DAC → DXB | Apr 19, 04:35 UTC | Apr 19, 05:35 UTC | 1h 0m |
| 2026-04-18 | UAE9U | DXB → DAC | Apr 18, 22:35 UTC | Apr 19, 02:40 UTC | 4h 5m |
| 2026-04-18 | UAE333 | MNL → DXB | Apr 18, 18:40 UTC | Apr 18, 19:05 UTC | 25m |
| 2026-04-18 | UAE333 | MNL → DXB | Apr 18, 10:35 UTC | Apr 18, 15:30 UTC | 4h 55m |
| 2026-04-18 | UAE332 | DXB → MNL | Apr 18, 07:35 UTC | Apr 18, 08:15 UTC | 40m |
| 2026-04-18 | UAE332 | DXB → MNL | Apr 18, 06:35 UTC | Apr 18, 07:15 UTC | 40m |
| 2026-04-18 | UAE332 | DXB → MNL | Apr 18, 03:30 UTC | Apr 18, 04:35 UTC | 1h 5m |
| 2026-04-18 | UAE332 | DXB → MNL | Apr 18, 00:20 UTC | Apr 18, 00:50 UTC | 30m |
| 2026-04-17 | UAE7Y | BOM → DXB | Apr 17, 20:10 UTC | Apr 17, 20:35 UTC | 25m |
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-EBU page for operator, model, and routing details .