sensors Mode-S transponder
8960E7
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-EDF · AIRBUS A-380-800
- Hex
- 8960E7
- Octal
- 42260347
- Decimal
- 9,003,239
- Country
- AE
- Tail
- A6-EDF
- Type
- A388
- Flights observed
- 65
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 3h ago
Current position
Country allocation
The ICAO 24-bit address 8960E7 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 |
|---|---|---|---|
| UAE385 | Emirates | 8 | 2026-05-09 |
| UAE62T | Emirates | 6 | 2026-05-06 |
| UAE4DU | Emirates | 6 | 2026-05-16 |
| UAE384 | Emirates | 6 | 2026-05-08 |
| UAE2AR | Emirates | 4 | 2026-05-16 |
| UAE79Y | Emirates | 3 | 2026-05-06 |
| UAE369 | Emirates | 3 | 2026-04-14 |
| UAE15K | Emirates | 3 | 2026-04-23 |
| UAE7Q | Emirates | 2 | 2026-04-24 |
| UAE7AM | Emirates | 2 | 2026-05-05 |
| UAE752 | Emirates | 2 | 2026-05-13 |
| UAE751 | Emirates | 2 | 2026-05-13 |
| UAE67V | Emirates | 2 | 2026-05-17 |
| UAE54J | Emirates | 2 | 2026-05-17 |
| UAE51P | Emirates | 2 | 2026-05-05 |
| UAE323 | Emirates | 2 | 2026-05-05 |
| UAE93P | Emirates | 1 | 2026-05-15 |
| UAE88 | Emirates | 1 | 2026-05-03 |
| UAE803 | Emirates | 1 | 2026-04-27 |
| UAE7V | Emirates | 1 | 2026-05-15 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | UAE2K | DXB → CAI | May 30, 14:35 UTC | May 30, 14:50 UTC | 15m |
| 2026-05-17 | UAE54J | VIE → DXB | May 17, 14:01 UTC | May 17, 19:20 UTC | 5h 20m |
| 2026-05-17 | UAE67V | DXB → VIE | May 17, 05:40 UTC | May 17, 11:40 UTC | 6h 0m |
| 2026-05-16 | UAE2AR | JNB → DXB | May 16, 17:45 UTC | May 17, 01:05 UTC | 7h 20m |
| 2026-05-16 | UAE4DU | DXB → JNB | May 16, 13:25 UTC | May 16, 13:55 UTC | 30m |
| 2026-05-16 | UAE4DU | DXB → JNB | May 16, 06:16 UTC | May 16, 06:31 UTC | 15m |
| 2026-05-15 | UAE93P | CDG → DXB | May 15, 20:15 UTC | May 16, 02:35 UTC | 6h 20m |
| 2026-05-15 | UAE7V | DXB → CDG | May 15, 12:45 UTC | May 15, 17:35 UTC | 4h 49m |
| 2026-05-15 | UAE2AR | JNB → DXB | May 15, 00:40 UTC | May 15, 01:05 UTC | 25m |
| 2026-05-14 | UAE2AR | JNB → DXB | May 14, 17:30 UTC | May 14, 17:45 UTC | 15m |
| 2026-05-14 | UAE4DU | DXB → JNB | May 14, 13:35 UTC | May 14, 14:20 UTC | 45m |
| 2026-05-14 | UAE4DU | DXB → JNB | May 14, 06:30 UTC | May 14, 06:50 UTC | 20m |
| 2026-05-13 | UAE752 | CMN → DXB | May 13, 15:25 UTC | May 13, 21:55 UTC | 6h 30m |
| 2026-05-13 | UAE751 | DXB → CMN | May 13, 04:00 UTC | May 13, 12:15 UTC | 8h 15m |
| 2026-05-10 | UAE54J | VIE → DXB | May 10, 13:55 UTC | May 10, 19:24 UTC | 5h 30m |
| 2026-05-10 | UAE67V | DXB → VIE | May 10, 05:30 UTC | May 10, 10:55 UTC | 5h 25m |
| 2026-05-09 | UAE385 | BKK → DXB | May 9, 03:20 UTC | May 9, 03:40 UTC | 20m |
| 2026-05-08 | UAE385 | BKK → DXB | May 8, 18:40 UTC | May 8, 21:05 UTC | 2h 25m |
| 2026-05-08 | UAE385 | BKK → DXB | May 8, 15:20 UTC | May 8, 16:00 UTC | 40m |
| 2026-05-08 | UAE385 | BKK → DXB | May 8, 13:35 UTC | May 8, 13:50 UTC | 15m |
| 2026-05-08 | UAE384 | BKK → HKG | May 8, 09:44 UTC | May 8, 09:59 UTC | 15m |
| 2026-05-08 | UAE384 | BKK → HKG | May 8, 07:39 UTC | May 8, 08:19 UTC | 40m |
| 2026-05-08 | UAE384 | BKK → HKG | May 8, 02:44 UTC | May 8, 05:05 UTC | 2h 20m |
| 2026-05-06 | UAE79Y | LHR → DXB | May 6, 18:10 UTC | May 7, 01:05 UTC | 6h 55m |
| 2026-05-06 | UAE62T | DXB → LHR | May 6, 10:55 UTC | May 6, 15:40 UTC | 4h 45m |
| 2026-05-05 | UAE51P | MAD → DXB | May 5, 13:45 UTC | May 5, 20:45 UTC | 7h 0m |
| 2026-05-05 | UAE7AM | DXB → MAD | May 5, 03:30 UTC | May 5, 11:25 UTC | 7h 55m |
| 2026-05-05 | UAE323 | ICN → DXB | May 5, 00:05 UTC | May 5, 00:30 UTC | 25m |
| 2026-05-04 | UAE323 | ICN → DXB | May 4, 15:15 UTC | May 4, 15:30 UTC | 15m |
| 2026-05-04 | UAE322 | DXB → ICN | May 4, 00:25 UTC | May 4, 07:15 UTC | 6h 50m |
| 2026-05-03 | UAE88 | ZRH → DXB | May 3, 13:55 UTC | May 3, 20:20 UTC | 6h 25m |
| 2026-05-03 | UAE11M | DXB → ZRH | May 3, 04:25 UTC | May 3, 10:55 UTC | 6h 30m |
| 2026-05-03 | UAE385 | BKK → DXB | May 3, 00:10 UTC | May 3, 00:30 UTC | 20m |
| 2026-05-02 | UAE385 | BKK → DXB | May 2, 18:35 UTC | May 2, 21:10 UTC | 2h 35m |
| 2026-05-02 | UAE385 | BKK → DXB | May 2, 15:40 UTC | May 2, 16:15 UTC | 35m |
| 2026-05-02 | UAE385 | BKK → DXB | May 2, 13:45 UTC | May 2, 14:00 UTC | 15m |
| 2026-05-02 | UAE384 | BKK → HKG | May 2, 09:35 UTC | May 2, 09:40 UTC | 5m |
| 2026-05-02 | UAE384 | BKK → HKG | May 2, 07:25 UTC | May 2, 07:55 UTC | 30m |
| 2026-05-01 | UAE384 | BKK → HKG | May 1, 23:15 UTC | May 2, 04:45 UTC | 5h 30m |
| 2026-05-01 | UAE51P | MAD → DXB | May 1, 13:45 UTC | May 1, 20:25 UTC | 6h 40m |
| 2026-05-01 | UAE7AM | DXB → MAD | May 1, 03:30 UTC | May 1, 11:20 UTC | 7h 50m |
| 2026-04-30 | UAE752 | CMN → DXB | Apr 30, 15:20 UTC | Apr 30, 22:05 UTC | 6h 45m |
| 2026-04-30 | UAE751 | DXB → CMN | Apr 30, 03:45 UTC | Apr 30, 11:50 UTC | 8h 5m |
| 2026-04-28 | UAE373 | BKK → DXB | Apr 28, 14:35 UTC | Apr 28, 20:50 UTC | 6h 15m |
| 2026-04-28 | UAE372 | DXB → BKK | Apr 28, 06:05 UTC | Apr 28, 11:35 UTC | 5h 30m |
| 2026-04-27 | UAE803 | DXB → JED | Apr 27, 12:10 UTC | Apr 27, 19:40 UTC | 7h 30m |
| 2026-04-25 | UAE2AR | JNB → DXB | Apr 25, 17:30 UTC | Apr 26, 01:10 UTC | 7h 40m |
| 2026-04-25 | UAE4DU | DXB → JNB | Apr 25, 13:25 UTC | Apr 25, 14:00 UTC | 35m |
| 2026-04-25 | UAE4DU | DXB → JNB | Apr 25, 06:15 UTC | Apr 25, 06:35 UTC | 20m |
| 2026-04-24 | UAE79Y | LHR → DXB | Apr 24, 16:10 UTC | Apr 24, 23:15 UTC | 7h 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-EDF page for operator, model, and routing details .