sensors Mode-S transponder
896176
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-EWD · BOEING 777-200LR
- Hex
- 896176
- Octal
- 42260566
- Decimal
- 9,003,382
- Country
- AE
- Tail
- A6-EWD
- Type
- B77L
- Flights observed
- 184
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- Jul 26, 20:00 UTC
Current position
Country allocation
The ICAO 24-bit address 896176 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 |
|---|---|---|---|
| UAE81W | - | 39 | 2026-07-08 |
| UAE256 | - | 39 | 2026-07-09 |
| UAE329 | Emirates | 16 | 2026-06-13 |
| UAE328 | Emirates | 11 | 2026-06-12 |
| UAE220 | Emirates | 11 | 2026-07-23 |
| UAE213 | Emirates | 10 | 2026-07-26 |
| UAE2J | Emirates | 9 | 2026-07-22 |
| UAE214 | - | 9 | 2026-07-15 |
| UAE221 | Emirates | 8 | 2026-07-23 |
| UAE4M | Emirates | 7 | 2026-07-24 |
| UAE229 | Emirates | 5 | 2026-04-21 |
| UAE9JQ | Emirates | 4 | 2026-05-12 |
| UAE93Q | Emirates | 4 | 2026-04-23 |
| UAE6AQ | Emirates | 2 | 2026-05-20 |
| UAE958 | Emirates | 1 | 2026-05-03 |
| UAE922 | Emirates | 1 | 2026-04-29 |
| UAE921 | Emirates | 1 | 2026-04-29 |
| UAE840 | Emirates | 1 | 2026-06-17 |
| UAE824 | Emirates | 1 | 2026-07-18 |
| UAE822 | Emirates | 1 | 2026-06-16 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | UAE213 | DXB → MIA | Jul 26, 16:50 UTC | Jul 26, 19:55 UTC | 3h 5m |
| 2026-07-25 | UAE213 | DXB → MIA | Jul 25, 22:55 UTC | Jul 26, 14:05 UTC | 15h 11m |
| 2026-07-24 | UAE4M | DFW → DXB | Jul 24, 17:55 UTC | Jul 25, 06:00 UTC | 12h 5m |
| 2026-07-23 | UAE221 | DXB → DFW | Jul 23, 22:40 UTC | Jul 24, 14:55 UTC | 16h 15m |
| 2026-07-23 | UAE220 | MCO → DXB | Jul 23, 15:15 UTC | Jul 23, 15:25 UTC | 10m |
| 2026-07-23 | UAE220 | MCO → DXB | Jul 23, 01:10 UTC | Jul 23, 13:55 UTC | 12h 45m |
| 2026-07-22 | UAE2J | DXB → MCO | Jul 22, 00:30 UTC | Jul 22, 14:35 UTC | 14h 5m |
| 2026-07-18 | UAE824 | DMM → DXB | Jul 18, 03:15 UTC | Jul 18, 05:00 UTC | 1h 45m |
| 2026-07-17 | UAE220 | - | Jul 17, 01:29 UTC | Jul 17, 15:35 UTC | 14h 5m |
| 2026-07-16 | UAE2J | - | Jul 16, 04:00 UTC | Jul 16, 14:40 UTC | 10h 40m |
| 2026-07-15 | UAE2J | - | Jul 15, 15:35 UTC | Jul 16, 14:40 UTC | 23h 5m |
| 2026-07-15 | UAE214 | - | Jul 15, 11:35 UTC | Jul 16, 07:10 UTC | 19h 35m |
| 2026-07-15 | UAE214 | - | Jul 15, 11:20 UTC | Jul 16, 07:10 UTC | 19h 50m |
| 2026-07-15 | UAE214 | - | Jul 15, 04:20 UTC | Jul 15, 16:15 UTC | 11h 55m |
| 2026-07-14 | UAE214 | - | Jul 14, 22:40 UTC | Jul 15, 01:45 UTC | 3h 4m |
| 2026-07-14 | UAE213 | - | Jul 14, 20:10 UTC | Jul 14, 20:30 UTC | 20m |
| 2026-07-14 | UAE213 | - | Jul 14, 17:25 UTC | Jul 14, 17:50 UTC | 25m |
| 2026-07-13 | UAE213 | - | Jul 13, 23:35 UTC | Jul 14, 15:05 UTC | 15h 30m |
| 2026-07-12 | UAE4M | - | Jul 12, 18:01 UTC | Jul 13, 08:45 UTC | 14h 45m |
| 2026-07-11 | UAE221 | - | Jul 11, 23:10 UTC | Jul 12, 14:35 UTC | 15h 25m |
| 2026-07-11 | UAE220 | - | Jul 11, 01:20 UTC | Jul 11, 15:15 UTC | 13h 55m |
| 2026-07-09 | UAE2J | - | Jul 9, 23:25 UTC | Jul 10, 14:25 UTC | 15h 0m |
| 2026-07-09 | UAE256 | - | Jul 9, 14:00 UTC | Jul 9, 20:15 UTC | 6h 15m |
| 2026-07-09 | UAE256 | - | Jul 9, 01:10 UTC | Jul 9, 11:35 UTC | 10h 25m |
| 2026-07-08 | UAE81W | BCN → MEX | Jul 8, 09:30 UTC | Jul 8, 21:00 UTC | 11h 30m |
| 2026-07-07 | UAE81W | BCN → MEX | Jul 7, 23:55 UTC | Jul 8, 06:20 UTC | 6h 25m |
| 2026-07-07 | UAE214 | - | Jul 7, 04:20 UTC | Jul 7, 18:05 UTC | 13h 45m |
| 2026-07-06 | UAE214 | - | Jul 6, 22:35 UTC | Jul 7, 01:35 UTC | 3h 0m |
| 2026-07-06 | UAE213 | - | Jul 6, 20:00 UTC | Jul 6, 20:15 UTC | 15m |
| 2026-07-06 | UAE213 | - | Jul 6, 17:15 UTC | Jul 6, 17:35 UTC | 20m |
| 2026-07-05 | UAE213 | - | Jul 5, 22:25 UTC | Jul 6, 13:25 UTC | 15h 0m |
| 2026-07-05 | UAE214 | - | Jul 5, 07:25 UTC | Jul 5, 18:05 UTC | 10h 40m |
| 2026-07-05 | UAE214 | - | Jul 5, 04:15 UTC | Jul 5, 04:50 UTC | 35m |
| 2026-07-05 | UAE214 | - | Jul 5, 01:05 UTC | Jul 5, 01:35 UTC | 30m |
| 2026-07-04 | UAE213 | - | Jul 4, 17:00 UTC | Jul 4, 17:20 UTC | 20m |
| 2026-07-03 | UAE213 | - | Jul 3, 22:30 UTC | Jul 4, 13:30 UTC | 15h 0m |
| 2026-07-02 | UAE256 | MEX → BCN | Jul 2, 14:10 UTC | Jul 2, 20:20 UTC | 6h 10m |
| 2026-07-02 | UAE256 | MEX → BCN | Jul 2, 01:00 UTC | Jul 2, 11:45 UTC | 10h 45m |
| 2026-07-01 | UAE81W | BCN → MEX | Jul 1, 09:30 UTC | Jul 1, 20:50 UTC | 11h 20m |
| 2026-06-30 | UAE81W | BCN → MEX | Jun 30, 23:45 UTC | Jul 1, 06:05 UTC | 6h 20m |
| 2026-06-30 | UAE724 | - | Jun 30, 07:25 UTC | Jun 30, 17:50 UTC | 10h 25m |
| 2026-06-29 | UAE256 | MEX → BCN | Jun 29, 14:34 UTC | Jun 29, 20:44 UTC | 6h 10m |
| 2026-06-29 | UAE256 | MEX → BCN | Jun 29, 01:39 UTC | Jun 29, 12:05 UTC | 10h 25m |
| 2026-06-28 | UAE81W | BCN → MEX | Jun 28, 09:50 UTC | Jun 28, 21:20 UTC | 11h 30m |
| 2026-06-27 | UAE81W | BCN → MEX | Jun 27, 23:25 UTC | Jun 28, 05:40 UTC | 6h 15m |
| 2026-06-27 | UAE256 | MEX → BCN | Jun 27, 14:00 UTC | Jun 27, 20:19 UTC | 6h 20m |
| 2026-06-27 | UAE256 | MEX → BCN | Jun 27, 01:04 UTC | Jun 27, 11:30 UTC | 10h 25m |
| 2026-06-26 | UAE81W | BCN → MEX | Jun 26, 09:24 UTC | Jun 26, 20:50 UTC | 11h 25m |
| 2026-06-25 | UAE81W | BCN → MEX | Jun 25, 23:24 UTC | Jun 26, 05:44 UTC | 6h 20m |
| 2026-06-25 | UAE256 | MEX → BCN | Jun 25, 13:59 UTC | Jun 25, 20:19 UTC | 6h 20m |
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-EWD page for operator, model, and routing details .