sensors Mode-S transponder
8963DF
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-EPP · BOEING 777-300ER
- Hex
- 8963DF
- Octal
- 42261737
- Decimal
- 9,003,999
- Country
- AE
- Tail
- A6-EPP
- Type
- B77W
- Flights observed
- 70
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 12d ago
Last known position
Country allocation
The ICAO 24-bit address 8963DF 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 |
|---|---|---|---|
| UAE185 | Emirates | 11 | 2026-05-06 |
| UAE186 | Emirates | 7 | 2026-04-17 |
| UAE34Y | Emirates | 4 | 2026-05-10 |
| UAE2MJ | Emirates | 4 | 2026-05-14 |
| UAE396 | Emirates | 3 | 2026-05-05 |
| UAE8T | Emirates | 2 | 2026-05-08 |
| UAE83F | Emirates | 2 | 2026-05-12 |
| UAE766 | Emirates | 2 | 2026-04-28 |
| UAE73J | Emirates | 2 | 2026-05-11 |
| UAE6AL | Emirates | 2 | 2026-05-09 |
| UAE397 | Emirates | 2 | 2026-04-29 |
| UAE33N | Emirates | 2 | 2026-04-18 |
| UAE306 | Emirates | 2 | 2026-04-16 |
| UAE29V | Emirates | 2 | 2026-05-14 |
| UAE2610 | - | 2 | 2026-05-16 |
| UAE1LJ | Emirates | 2 | 2026-04-22 |
| UAE1GP | Emirates | 2 | 2026-05-08 |
| UAE96 | Emirates | 1 | 2026-05-04 |
| UAE95 | Emirates | 1 | 2026-05-04 |
| UAE815 | Emirates | 1 | 2026-04-18 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-16 | UAE2610 | - | May 16, 17:50 UTC | May 17, 13:25 UTC | 19h 35m |
| 2026-05-16 | UAE2610 | - | May 16, 16:31 UTC | May 17, 13:25 UTC | 20h 55m |
| 2026-05-15 | UAE13U | FRA → DXB | May 15, 20:40 UTC | May 16, 14:20 UTC | 17h 41m |
| 2026-05-14 | UAE29V | DXB → FRA | May 14, 21:50 UTC | May 15, 17:30 UTC | 19h 39m |
| 2026-05-14 | UAE29V | DXB → FRA | May 14, 20:20 UTC | May 15, 17:30 UTC | 21h 9m |
| 2026-05-14 | UAE2MJ | DXB → ZRH | May 14, 14:15 UTC | May 14, 17:20 UTC | 3h 5m |
| 2026-05-12 | UAE83F | JNB → DXB | May 12, 11:45 UTC | May 12, 12:05 UTC | 20m |
| 2026-05-11 | UAE73J | MAN → DXB | May 11, 13:50 UTC | May 12, 08:10 UTC | 18h 21m |
| 2026-05-11 | UAE73J | MAN → DXB | May 11, 13:15 UTC | May 12, 08:10 UTC | 18h 56m |
| 2026-05-10 | UAE34Y | DXB → MAN | May 10, 15:49 UTC | May 11, 10:10 UTC | 18h 20m |
| 2026-05-10 | UAE34Y | DXB → MAN | May 10, 13:49 UTC | May 11, 10:10 UTC | 20h 20m |
| 2026-05-10 | UAE34Y | DXB → MAN | May 10, 13:19 UTC | May 11, 10:10 UTC | 20h 50m |
| 2026-05-10 | UAE34Y | DXB → MAN | May 10, 05:34 UTC | May 10, 10:40 UTC | 5h 5m |
| 2026-05-09 | UAE6AL | NCE → DXB | May 9, 14:05 UTC | May 9, 19:30 UTC | 5h 25m |
| 2026-05-08 | UAE1GP | DXB → NCE | May 8, 16:50 UTC | May 9, 11:25 UTC | 18h 35m |
| 2026-05-08 | UAE23C | DXB → CPT | May 8, 12:20 UTC | May 8, 14:30 UTC | 2h 10m |
| 2026-05-08 | UAE8T | ZRH → DXB | May 8, 02:39 UTC | May 8, 03:14 UTC | 35m |
| 2026-05-07 | UAE8T | ZRH → DXB | May 7, 20:40 UTC | May 7, 23:45 UTC | 3h 5m |
| 2026-05-07 | UAE2MJ | DXB → ZRH | May 7, 00:55 UTC | May 7, 18:25 UTC | 17h 30m |
| 2026-05-06 | UAE2MJ | DXB → ZRH | May 6, 19:50 UTC | May 7, 18:25 UTC | 22h 35m |
| 2026-05-06 | UAE2MJ | DXB → ZRH | May 6, 19:40 UTC | May 7, 17:45 UTC | 22h 5m |
| 2026-05-06 | UAE185 | DXB → BCN | May 6, 04:50 UTC | May 6, 11:30 UTC | 6h 40m |
| 2026-05-05 | UAE185 | DXB → BCN | May 5, 10:45 UTC | May 6, 09:45 UTC | 23h 0m |
| 2026-05-05 | UAE396 | DXB → HKT | May 5, 08:05 UTC | May 5, 08:25 UTC | 20m |
| 2026-05-04 | UAE96 | FCO → DXB | May 4, 20:25 UTC | May 5, 01:15 UTC | 4h 50m |
| 2026-05-04 | UAE95 | DXB → FCO | May 4, 10:50 UTC | May 4, 17:20 UTC | 6h 30m |
| 2026-05-04 | UAE7P | CMB → DXB | May 4, 04:50 UTC | May 4, 08:45 UTC | 3h 55m |
| 2026-05-03 | UAE5K | DXB → CMB | May 3, 23:00 UTC | May 4, 02:30 UTC | 3h 30m |
| 2026-05-03 | UAE379 | HKT → DXB | May 3, 02:10 UTC | May 3, 19:55 UTC | 17h 44m |
| 2026-05-01 | UAE83F | JNB → DXB | May 1, 11:35 UTC | May 1, 19:20 UTC | 7h 45m |
| 2026-05-01 | UAE37R | DXB → JNB | May 1, 00:35 UTC | May 1, 08:00 UTC | 7h 25m |
| 2026-04-30 | UAE51P | MAD → DXB | Apr 30, 14:05 UTC | Apr 30, 20:50 UTC | 6h 45m |
| 2026-04-30 | UAE7AM | DXB → MAD | Apr 30, 03:50 UTC | Apr 30, 11:50 UTC | 8h 0m |
| 2026-04-29 | UAE397 | HKT → DXB | Apr 29, 22:35 UTC | Apr 29, 23:00 UTC | 25m |
| 2026-04-29 | UAE396 | DXB → HKT | Apr 29, 06:29 UTC | Apr 29, 20:55 UTC | 14h 26m |
| 2026-04-28 | UAE766 | JNB → DXB | Apr 28, 20:40 UTC | Apr 29, 04:00 UTC | 7h 20m |
| 2026-04-22 | UAE1LJ | DXB → JNB | Apr 22, 10:35 UTC | Apr 22, 18:15 UTC | 7h 40m |
| 2026-04-21 | UAE766 | JNB → DXB | Apr 21, 20:40 UTC | Apr 22, 04:15 UTC | 7h 35m |
| 2026-04-21 | UAE1LJ | DXB → JNB | Apr 21, 10:50 UTC | Apr 21, 18:35 UTC | 7h 45m |
| 2026-04-21 | UAE6K | MLE → DXB | Apr 21, 07:55 UTC | Apr 21, 08:10 UTC | 15m |
| 2026-04-20 | UAE656 | DXB → MLE | Apr 20, 22:50 UTC | Apr 20, 23:10 UTC | 20m |
| 2026-04-20 | UAE6AL | NCE → DXB | Apr 20, 13:55 UTC | Apr 20, 19:40 UTC | 5h 45m |
| 2026-04-20 | UAE1GP | DXB → NCE | Apr 20, 04:25 UTC | Apr 20, 11:40 UTC | 7h 15m |
| 2026-04-19 | UAE726 | DAR → DXB | Apr 19, 17:20 UTC | Apr 19, 17:50 UTC | 30m |
| 2026-04-19 | UAE725 | DXB → DAR | Apr 19, 06:00 UTC | Apr 19, 06:20 UTC | 20m |
| 2026-04-18 | UAE815 | DXB → RUH | Apr 18, 21:10 UTC | Apr 19, 02:45 UTC | 5h 35m |
| 2026-04-18 | UAE33N | BOM → DXB | Apr 18, 07:40 UTC | Apr 18, 08:05 UTC | 25m |
| 2026-04-18 | UAE33N | BOM → DXB | Apr 18, 00:10 UTC | Apr 18, 08:05 UTC | 7h 55m |
| 2026-04-17 | UAE186 | BCN → DXB | Apr 17, 19:40 UTC | Apr 17, 20:55 UTC | 1h 15m |
| 2026-04-17 | UAE186 | BCN → DXB | Apr 17, 15:20 UTC | Apr 17, 16:25 UTC | 1h 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-EPP page for operator, model, and routing details .