sensors Mode-S transponder
896473
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-EUI · AIRBUS A-380-800
- Hex
- 896473
- Octal
- 42262163
- Decimal
- 9,004,147
- Country
- AE
- Tail
- A6-EUI
- Type
- A388
- Flights observed
- 48
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 896473 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 |
|---|---|---|---|
| UAE51N | Emirates | 6 | 2026-05-30 |
| UAE261 | Emirates | 6 | 2026-05-27 |
| UAE41P | Emirates | 5 | 2026-05-31 |
| UAE262 | Emirates | 5 | 2026-05-28 |
| UAE569 | Emirates | 3 | 2026-06-04 |
| UAE568 | Emirates | 3 | 2026-06-03 |
| UAE8ER | Emirates | 2 | 2026-05-23 |
| UAE83M | Emirates | 2 | 2026-05-25 |
| UAE319 | Emirates | 2 | 2026-05-29 |
| UAE318 | Emirates | 2 | 2026-05-28 |
| UAE2VL | Emirates | 2 | 2026-06-05 |
| UAE1Y | Emirates | 2 | 2026-06-04 |
| UAE926 | Emirates | 1 | 2026-06-03 |
| UAE5V | Emirates | 1 | 2026-05-23 |
| UAE500 | Emirates | 1 | 2026-05-24 |
| UAE29N | Emirates | 1 | 2026-06-02 |
| UAE2558 | - | 1 | 2026-05-05 |
| UAE2504 | Emirates | 1 | 2026-04-21 |
| UAE216 | Emirates | 1 | 2026-05-26 |
| UAE1 | Emirates | 1 | 2026-04-29 |
Recent flights last 48
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-05 | UAE2VL | IAH → DXB | Jun 5, 01:15 UTC | Jun 5, 16:05 UTC | 14h 50m |
| 2026-06-04 | UAE1Y | DXB → IAH | Jun 4, 05:50 UTC | Jun 4, 22:10 UTC | 16h 20m |
| 2026-06-04 | UAE569 | BLR → DXB | Jun 4, 00:30 UTC | Jun 4, 02:45 UTC | 2h 15m |
| 2026-06-03 | UAE568 | DXB → BLR | Jun 3, 19:30 UTC | Jun 3, 21:00 UTC | 1h 30m |
| 2026-06-03 | UAE568 | DXB → BLR | Jun 3, 17:40 UTC | Jun 3, 18:05 UTC | 25m |
| 2026-06-03 | UAE926 | CAI → DXB | Jun 3, 00:15 UTC | Jun 3, 03:20 UTC | 3h 5m |
| 2026-06-02 | UAE29N | DXB → CAI | Jun 2, 19:05 UTC | Jun 2, 21:35 UTC | 2h 30m |
| 2026-06-02 | UAE2VL | IAH → DXB | Jun 2, 00:55 UTC | Jun 2, 15:25 UTC | 14h 30m |
| 2026-06-01 | UAE1Y | DXB → IAH | Jun 1, 08:05 UTC | Jun 1, 21:30 UTC | 13h 25m |
| 2026-05-31 | UAE41P | SFO → DXB | May 31, 15:30 UTC | May 31, 15:50 UTC | 20m |
| 2026-05-31 | UAE41P | SFO → DXB | May 31, 00:30 UTC | May 31, 10:30 UTC | 10h 0m |
| 2026-05-30 | UAE51N | DXB → SFO | May 30, 07:20 UTC | May 30, 21:40 UTC | 14h 20m |
| 2026-05-30 | UAE51N | DXB → SFO | May 30, 05:10 UTC | May 30, 05:35 UTC | 25m |
| 2026-05-29 | UAE319 | NRT → DXB | May 29, 13:40 UTC | May 30, 00:15 UTC | 10h 35m |
| 2026-05-28 | UAE318 | DXB → NRT | May 28, 23:05 UTC | May 29, 08:30 UTC | 9h 25m |
| 2026-05-28 | UAE262 | GRU → DXB | May 28, 04:55 UTC | May 28, 18:55 UTC | 14h 0m |
| 2026-05-27 | UAE261 | DXB → GRU | May 27, 19:10 UTC | May 27, 20:45 UTC | 1h 35m |
| 2026-05-26 | UAE216 | LAX → DXB | May 26, 00:04 UTC | May 26, 16:15 UTC | 16h 10m |
| 2026-05-25 | UAE83M | DXB → LAX | May 25, 18:30 UTC | May 25, 21:24 UTC | 2h 55m |
| 2026-05-24 | UAE83M | DXB → LAX | May 24, 23:25 UTC | May 25, 21:24 UTC | 21h 59m |
| 2026-05-24 | UAE500 | DXB → BOM | May 24, 20:00 UTC | May 24, 20:50 UTC | 50m |
| 2026-05-23 | UAE5V | JFK → DXB | May 23, 15:45 UTC | May 24, 04:25 UTC | 12h 40m |
| 2026-05-23 | UAE8ER | DXB → JFK | May 23, 05:20 UTC | May 23, 12:45 UTC | 7h 25m |
| 2026-05-22 | UAE8ER | DXB → JFK | May 22, 23:05 UTC | May 23, 05:15 UTC | 6h 9m |
| 2026-05-22 | UAE41P | SFO → DXB | May 22, 00:10 UTC | May 22, 16:10 UTC | 16h 0m |
| 2026-05-21 | UAE51N | DXB → SFO | May 21, 04:55 UTC | May 21, 20:55 UTC | 16h 0m |
| 2026-05-20 | UAE262 | GRU → DXB | May 20, 04:50 UTC | May 20, 18:55 UTC | 14h 5m |
| 2026-05-19 | UAE261 | DXB → GRU | May 19, 18:55 UTC | May 19, 20:35 UTC | 1h 40m |
| 2026-05-18 | UAE319 | NRT → DXB | May 18, 13:40 UTC | May 19, 00:10 UTC | 10h 29m |
| 2026-05-18 | UAE318 | DXB → NRT | May 18, 00:35 UTC | May 18, 08:50 UTC | 8h 15m |
| 2026-05-17 | UAE41P | SFO → DXB | May 17, 00:50 UTC | May 17, 16:10 UTC | 15h 20m |
| 2026-05-16 | UAE51N | DXB → SFO | May 16, 05:30 UTC | May 16, 21:25 UTC | 15h 55m |
| 2026-05-15 | UAE41P | SFO → DXB | May 15, 00:20 UTC | May 15, 15:15 UTC | 14h 54m |
| 2026-05-14 | UAE51N | DXB → SFO | May 14, 18:25 UTC | May 14, 21:10 UTC | 2h 45m |
| 2026-05-14 | UAE51N | DXB → SFO | May 14, 04:55 UTC | May 14, 05:15 UTC | 20m |
| 2026-05-05 | UAE2558 | - | May 5, 09:35 UTC | May 5, 16:35 UTC | 7h 0m |
| 2026-04-29 | UAE1 | DXB → LHR | Apr 29, 03:24 UTC | Apr 29, 11:55 UTC | 8h 31m |
| 2026-04-28 | UAE262 | GRU → DXB | Apr 28, 04:55 UTC | Apr 28, 18:50 UTC | 13h 55m |
| 2026-04-27 | UAE261 | DXB → GRU | Apr 27, 05:30 UTC | Apr 27, 20:05 UTC | 14h 35m |
| 2026-04-26 | UAE262 | GRU → DXB | Apr 26, 04:50 UTC | Apr 26, 18:40 UTC | 13h 50m |
| 2026-04-25 | UAE261 | DXB → GRU | Apr 25, 05:45 UTC | Apr 25, 20:30 UTC | 14h 45m |
| 2026-04-24 | UAE262 | GRU → DXB | Apr 24, 05:05 UTC | Apr 24, 18:50 UTC | 13h 45m |
| 2026-04-23 | UAE261 | DXB → GRU | Apr 23, 13:00 UTC | Apr 23, 20:45 UTC | 7h 45m |
| 2026-04-23 | UAE261 | DXB → GRU | Apr 23, 05:55 UTC | Apr 23, 06:15 UTC | 20m |
| 2026-04-23 | UAE569 | BLR → DXB | Apr 23, 02:30 UTC | Apr 23, 02:55 UTC | 25m |
| 2026-04-23 | UAE569 | BLR → DXB | Apr 23, 00:20 UTC | Apr 23, 00:45 UTC | 25m |
| 2026-04-22 | UAE568 | DXB → BLR | Apr 22, 17:45 UTC | Apr 22, 20:50 UTC | 3h 5m |
| 2026-04-21 | UAE2504 | LGW → DXB | Apr 21, 18:50 UTC | Apr 21, 19:05 UTC | 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-EUI page for operator, model, and routing details .