sensors Mode-S transponder
896615
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-EFW · BOEING 777-200LR
- Hex
- 896615
- Octal
- 42263025
- Decimal
- 9,004,565
- Country
- AE
- Tail
- A6-EFW
- Type
- B77L
- Flights observed
- 129
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 18h ago
Last known position
Country allocation
The ICAO 24-bit address 896615 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 |
|---|---|---|---|
| UAE9935 | Emirates | 11 | 2026-05-17 |
| UAE9618 | - | 10 | 2026-05-28 |
| UAE9936 | Emirates | 7 | 2026-05-19 |
| UAE9915 | Emirates | 5 | 2026-05-23 |
| UAE9642 | - | 5 | 2026-05-25 |
| UAE6MR | Emirates | 5 | 2026-05-18 |
| UAE9881 | Emirates | 4 | 2026-05-11 |
| UAE9811 | - | 4 | 2026-05-22 |
| UAE9964 | Emirates | 3 | 2026-05-14 |
| UAE9963 | Emirates | 3 | 2026-05-14 |
| UAE9922 | Emirates | 3 | 2026-05-07 |
| UAE9889 | Emirates | 3 | 2026-05-10 |
| UAE9873 | Emirates | 3 | 2026-05-16 |
| UAE9871 | Emirates | 3 | 2026-05-29 |
| UAE9841 | Emirates | 3 | 2026-05-26 |
| UAE9827 | Emirates | 3 | 2026-04-27 |
| UAE9783 | Emirates | 3 | 2026-04-28 |
| UAE9616 | Emirates | 3 | 2026-04-26 |
| UAE9921 | Emirates | 2 | 2026-05-06 |
| UAE9894 | Emirates | 2 | 2026-05-03 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | UAE9871 | CAN → DWC | May 29, 07:25 UTC | May 29, 11:00 UTC | 3h 35m |
| 2026-05-28 | UAE9825 | HKG → DWC | May 28, 05:20 UTC | May 28, 23:40 UTC | 18h 20m |
| 2026-05-28 | UAE9618 | - | May 28, 02:35 UTC | May 28, 02:50 UTC | 15m |
| 2026-05-27 | UAE9618 | - | May 27, 15:20 UTC | May 28, 01:40 UTC | 10h 20m |
| 2026-05-27 | UAE9618 | - | May 27, 11:35 UTC | May 27, 11:55 UTC | 20m |
| 2026-05-27 | UAE9618 | - | May 27, 09:35 UTC | May 27, 10:10 UTC | 35m |
| 2026-05-27 | UAE9618 | - | May 27, 05:59 UTC | May 27, 06:55 UTC | 55m |
| 2026-05-26 | UAE9841 | HKG → DWC | May 26, 01:20 UTC | May 26, 21:20 UTC | 20h 0m |
| 2026-05-26 | UAE9841 | HKG → DWC | May 26, 00:19 UTC | May 26, 21:20 UTC | 21h 0m |
| 2026-05-25 | UAE9841 | HKG → DWC | May 25, 22:19 UTC | May 25, 22:30 UTC | 10m |
| 2026-05-25 | UAE9642 | - | May 25, 02:30 UTC | May 25, 19:10 UTC | 16h 40m |
| 2026-05-24 | UAE9642 | - | May 24, 15:55 UTC | May 24, 23:46 UTC | 7h 51m |
| 2026-05-24 | UAE9642 | - | May 24, 10:45 UTC | May 24, 12:15 UTC | 1h 30m |
| 2026-05-23 | UAE9915 | MEX → UIO | May 23, 20:15 UTC | May 24, 07:15 UTC | 11h 0m |
| 2026-05-23 | UAE9915 | MEX → UIO | May 23, 01:00 UTC | May 23, 17:00 UTC | 15h 59m |
| 2026-05-22 | UAE9831 | - | May 22, 22:05 UTC | May 22, 22:20 UTC | 15m |
| 2026-05-22 | UAE9830 | - | May 22, 19:00 UTC | May 22, 19:20 UTC | 20m |
| 2026-05-22 | UAE9830 | - | May 22, 07:50 UTC | May 22, 16:45 UTC | 8h 55m |
| 2026-05-22 | UAE9811 | - | May 22, 04:50 UTC | May 22, 05:05 UTC | 15m |
| 2026-05-22 | UAE9811 | - | May 22, 00:25 UTC | May 22, 00:50 UTC | 25m |
| 2026-05-21 | UAE9341 | AKL → SIN | May 21, 03:30 UTC | May 21, 20:45 UTC | 17h 15m |
| 2026-05-20 | UAE9341 | AKL → SIN | May 20, 15:25 UTC | May 20, 18:30 UTC | 3h 5m |
| 2026-05-20 | UAE9618 | - | May 20, 11:50 UTC | May 20, 12:10 UTC | 20m |
| 2026-05-20 | UAE9618 | - | May 20, 09:40 UTC | May 20, 10:10 UTC | 30m |
| 2026-05-19 | UAE9618 | - | May 19, 23:45 UTC | May 20, 06:30 UTC | 6h 46m |
| 2026-05-19 | UAE9618 | - | May 19, 16:00 UTC | May 19, 21:20 UTC | 5h 20m |
| 2026-05-19 | UAE9618 | - | May 19, 14:30 UTC | May 19, 14:55 UTC | 25m |
| 2026-05-19 | UAE9936 | JFK → AMS | May 19, 03:45 UTC | May 19, 09:30 UTC | 5h 45m |
| 2026-05-18 | UAE9936 | JFK → AMS | May 18, 16:10 UTC | May 19, 01:25 UTC | 9h 14m |
| 2026-05-18 | UAE6MR | IAH → FRA | May 18, 11:00 UTC | May 18, 12:30 UTC | 1h 30m |
| 2026-05-17 | UAE9935 | FRA → MEX | May 17, 19:35 UTC | May 18, 07:20 UTC | 11h 45m |
| 2026-05-17 | UAE9935 | FRA → MEX | May 17, 00:20 UTC | May 17, 16:35 UTC | 16h 15m |
| 2026-05-16 | UAE9935 | FRA → MEX | May 16, 19:25 UTC | May 17, 16:35 UTC | 21h 10m |
| 2026-05-16 | UAE9935 | FRA → MEX | May 16, 18:35 UTC | May 17, 16:35 UTC | 22h 0m |
| 2026-05-16 | UAE9935 | FRA → MEX | May 16, 16:31 UTC | May 17, 15:15 UTC | 22h 45m |
| 2026-05-16 | UAE9814 | DWC → HAN | May 16, 09:51 UTC | May 17, 04:15 UTC | 18h 25m |
| 2026-05-16 | UAE9873 | PVG → DWC | May 16, 07:20 UTC | May 17, 04:15 UTC | 20h 55m |
| 2026-05-16 | UAE9873 | PVG → DWC | May 16, 07:05 UTC | May 17, 04:15 UTC | 21h 10m |
| 2026-05-15 | UAE9872 | DWC → PVG | May 15, 12:15 UTC | May 15, 23:20 UTC | 11h 4m |
| 2026-05-14 | UAE9964 | FRA → DWC | May 14, 19:45 UTC | May 15, 09:30 UTC | 13h 45m |
| 2026-05-14 | UAE9964 | FRA → DWC | May 14, 13:50 UTC | May 15, 09:30 UTC | 19h 40m |
| 2026-05-14 | UAE9964 | FRA → DWC | May 14, 11:25 UTC | May 15, 09:30 UTC | 22h 5m |
| 2026-05-14 | UAE9963 | DXB → DFW | May 14, 03:55 UTC | May 14, 06:30 UTC | 2h 35m |
| 2026-05-13 | UAE9963 | DXB → DFW | May 13, 15:05 UTC | May 14, 00:55 UTC | 9h 50m |
| 2026-05-13 | UAE9963 | DXB → DFW | May 13, 08:05 UTC | May 13, 12:15 UTC | 4h 10m |
| 2026-05-12 | UAE9795 | - | May 12, 17:15 UTC | May 12, 17:25 UTC | 10m |
| 2026-05-12 | UAE9794 | DWC → ICN | May 12, 14:35 UTC | May 12, 14:45 UTC | 10m |
| 2026-05-11 | UAE9881 | HKG → HKG | May 11, 01:34 UTC | May 11, 16:00 UTC | 14h 25m |
| 2026-05-10 | UAE9881 | HKG → HKG | May 10, 13:40 UTC | May 11, 11:40 UTC | 22h 0m |
| 2026-05-10 | UAE9881 | HKG → HKG | May 10, 11:55 UTC | May 11, 04:50 UTC | 16h 55m |
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-EFW page for operator, model, and routing details .