sensors Mode-S transponder
896175
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-EWC · BOEING 777-200LR
- Hex
- 896175
- Octal
- 42260565
- Decimal
- 9,003,381
- Country
- AE
- Tail
- A6-EWC
- Type
- B77L
- Flights observed
- 62
- Distinct callsigns
- 18
- Country
- AE
- Last broadcast
- 6h ago
Last known position
Country allocation
The ICAO 24-bit address 896175 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 18 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| UAE4M | Emirates | 12 | 2026-05-18 |
| UAE221 | Emirates | 12 | 2026-05-23 |
| UAE93Q | Emirates | 8 | 2026-04-28 |
| UAE81W | Emirates | 5 | 2026-05-26 |
| UAE229 | Emirates | 5 | 2026-04-26 |
| UAE328 | Emirates | 4 | 2026-05-29 |
| UAE256 | Emirates | 4 | 2026-05-27 |
| UAE329 | Emirates | 2 | 2026-05-29 |
| UAE810 | Emirates | 1 | 2026-04-29 |
| UAE7P | Emirates | 1 | 2026-05-12 |
| UAE7MY | Emirates | 1 | 2026-05-01 |
| UAE6AU | Emirates | 1 | 2026-05-02 |
| UAE648 | Emirates | 1 | 2026-05-10 |
| UAE56F | Emirates | 1 | 2026-05-10 |
| UAE531 | Emirates | 1 | 2026-05-10 |
| UAE530 | Emirates | 1 | 2026-05-10 |
| UAE222 | Emirates | 1 | 2026-05-24 |
| UAE118 | Emirates | 1 | 2026-05-21 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | UAE329 | SZX → DXB | May 29, 18:00 UTC | May 29, 23:10 UTC | 5h 10m |
| 2026-05-29 | UAE328 | DXB → SZX | May 29, 14:35 UTC | May 29, 14:45 UTC | 10m |
| 2026-05-29 | UAE328 | DXB → SZX | May 29, 09:00 UTC | May 29, 12:15 UTC | 3h 15m |
| 2026-05-27 | UAE256 | MEX → BCN | May 27, 14:40 UTC | May 27, 20:35 UTC | 5h 55m |
| 2026-05-27 | UAE256 | MEX → BCN | May 27, 01:09 UTC | May 27, 12:00 UTC | 10h 50m |
| 2026-05-26 | UAE81W | BCN → MEX | May 26, 09:29 UTC | May 26, 20:54 UTC | 11h 25m |
| 2026-05-26 | UAE81W | BCN → MEX | May 26, 02:15 UTC | May 26, 06:20 UTC | 4h 5m |
| 2026-05-25 | UAE81W | BCN → MEX | May 25, 03:20 UTC | May 26, 03:15 UTC | 23h 55m |
| 2026-05-24 | UAE222 | DFW → DXB | May 24, 16:25 UTC | May 25, 05:00 UTC | 12h 35m |
| 2026-05-23 | UAE221 | DXB → DFW | May 23, 02:30 UTC | May 23, 14:45 UTC | 12h 15m |
| 2026-05-21 | UAE118 | IST → DXB | May 21, 20:45 UTC | May 22, 00:10 UTC | 3h 25m |
| 2026-05-18 | UAE4M | DFW → DXB | May 18, 17:40 UTC | May 19, 07:50 UTC | 14h 9m |
| 2026-05-18 | UAE221 | DXB → DFW | May 18, 01:30 UTC | May 18, 14:35 UTC | 13h 5m |
| 2026-05-15 | UAE4M | DFW → DXB | May 15, 17:45 UTC | May 16, 07:35 UTC | 13h 51m |
| 2026-05-14 | UAE221 | DXB → DFW | May 14, 22:50 UTC | May 15, 14:10 UTC | 15h 20m |
| 2026-05-12 | UAE7P | CMB → DXB | May 12, 05:10 UTC | May 12, 05:50 UTC | 40m |
| 2026-05-10 | UAE56F | CMB → DXB | May 10, 21:54 UTC | May 10, 22:35 UTC | 40m |
| 2026-05-10 | UAE648 | DXB → CMB | May 10, 15:15 UTC | May 10, 15:55 UTC | 40m |
| 2026-05-10 | UAE531 | COK → DXB | May 10, 05:14 UTC | May 10, 05:25 UTC | 10m |
| 2026-05-10 | UAE530 | DXB → COK | May 10, 02:55 UTC | May 10, 03:10 UTC | 15m |
| 2026-05-07 | UAE4M | DFW → DXB | May 7, 17:40 UTC | May 8, 05:35 UTC | 11h 55m |
| 2026-05-07 | UAE221 | DXB → DFW | May 7, 02:00 UTC | May 7, 14:55 UTC | 12h 55m |
| 2026-05-06 | UAE221 | DXB → DFW | May 6, 09:20 UTC | May 7, 06:20 UTC | 20h 59m |
| 2026-05-06 | UAE221 | DXB → DFW | May 6, 08:45 UTC | May 7, 06:20 UTC | 21h 34m |
| 2026-05-06 | UAE221 | DXB → DFW | May 6, 05:20 UTC | May 7, 05:15 UTC | 23h 55m |
| 2026-05-06 | UAE4M | DFW → DXB | May 6, 03:20 UTC | May 7, 03:15 UTC | 23h 54m |
| 2026-05-05 | UAE4M | DFW → DXB | May 5, 19:05 UTC | May 6, 09:20 UTC | 14h 15m |
| 2026-05-05 | UAE221 | DXB → DFW | May 5, 03:20 UTC | May 5, 16:35 UTC | 13h 15m |
| 2026-05-03 | UAE329 | SZX → DXB | May 3, 17:05 UTC | May 4, 00:45 UTC | 7h 40m |
| 2026-05-03 | UAE328 | DXB → SZX | May 3, 14:20 UTC | May 3, 14:35 UTC | 15m |
| 2026-05-03 | UAE328 | DXB → SZX | May 3, 07:55 UTC | May 3, 12:25 UTC | 4h 30m |
| 2026-05-02 | UAE6AU | PER → DXB | May 2, 14:15 UTC | May 3, 00:55 UTC | 10h 40m |
| 2026-05-01 | UAE7MY | DXB → PER | May 1, 23:15 UTC | May 2, 09:20 UTC | 10h 5m |
| 2026-04-29 | UAE810 | MED → DXB | Apr 29, 11:10 UTC | Apr 29, 17:20 UTC | 6h 10m |
| 2026-04-28 | UAE93Q | SEA → DXB | Apr 28, 00:25 UTC | Apr 28, 15:40 UTC | 15h 15m |
| 2026-04-26 | UAE229 | DXB → SEA | Apr 26, 05:10 UTC | Apr 26, 19:50 UTC | 14h 40m |
| 2026-04-25 | UAE93Q | SEA → DXB | Apr 25, 00:45 UTC | Apr 25, 15:05 UTC | 14h 20m |
| 2026-04-23 | UAE229 | DXB → SEA | Apr 23, 18:00 UTC | Apr 23, 19:20 UTC | 1h 20m |
| 2026-04-23 | UAE229 | DXB → SEA | Apr 23, 05:00 UTC | Apr 23, 05:25 UTC | 25m |
| 2026-04-22 | UAE256 | MEX → BCN | Apr 22, 14:05 UTC | Apr 22, 20:25 UTC | 6h 20m |
| 2026-04-22 | UAE256 | MEX → BCN | Apr 22, 01:25 UTC | Apr 22, 12:00 UTC | 10h 35m |
| 2026-04-21 | UAE81W | BCN → MEX | Apr 21, 09:05 UTC | Apr 21, 20:40 UTC | 11h 35m |
| 2026-04-20 | UAE81W | BCN → MEX | Apr 20, 23:20 UTC | Apr 21, 06:55 UTC | 7h 35m |
| 2026-04-20 | UAE93Q | SEA → DXB | Apr 20, 00:35 UTC | Apr 20, 15:35 UTC | 15h 0m |
| 2026-04-18 | UAE229 | DXB → SEA | Apr 18, 05:00 UTC | Apr 18, 20:20 UTC | 15h 20m |
| 2026-04-17 | UAE4M | DFW → DXB | Apr 17, 09:20 UTC | Apr 17, 09:55 UTC | 35m |
| 2026-04-17 | UAE4M | DFW → DXB | Apr 17, 08:45 UTC | Apr 17, 09:15 UTC | 30m |
| 2026-04-17 | UAE4M | DFW → DXB | Apr 17, 03:20 UTC | Apr 17, 05:15 UTC | 1h 56m |
| 2026-04-17 | UAE4M | DFW → DXB | Apr 17, 02:20 UTC | Apr 17, 03:15 UTC | 55m |
| 2026-04-16 | UAE4M | DFW → DXB | Apr 16, 21:14 UTC | Apr 16, 22:30 UTC | 1h 15m |
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-EWC page for operator, model, and routing details .