sensors Mode-S transponder
896523
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-EVM · AIRBUS A-380-800
- Hex
- 896523
- Octal
- 42262443
- Decimal
- 9,004,323
- Country
- AE
- Tail
- A6-EVM
- Type
- A388
- Flights observed
- 126
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- Jul 26, 14:35 UTC
Last known position
Country allocation
The ICAO 24-bit address 896523 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 |
|---|---|---|---|
| UAE80T | - | 10 | 2026-07-11 |
| UAE5AM | - | 8 | 2026-07-12 |
| UAE1CR | Emirates | 7 | 2026-07-22 |
| UAE6 | - | 6 | 2026-06-24 |
| UAE43P | Emirates | 6 | 2026-07-23 |
| UAE2VL | Emirates | 6 | 2026-07-25 |
| UAE5V | - | 5 | 2026-07-10 |
| UAE8ER | - | 4 | 2026-07-09 |
| UAE83M | Emirates | 4 | 2026-06-18 |
| UAE4CK | Emirates | 4 | 2026-06-23 |
| UAE318 | Emirates | 4 | 2026-05-19 |
| UAE216 | Emirates | 4 | 2026-06-19 |
| UAE1Y | Emirates | 4 | 2026-07-24 |
| UAE75T | Emirates | 3 | 2026-06-12 |
| UAE62P | Emirates | 3 | 2026-07-26 |
| UAE5CL | Emirates | 3 | 2026-05-07 |
| UAE501 | - | 3 | 2026-07-19 |
| UAE500 | - | 3 | 2026-07-19 |
| UAE319 | Emirates | 3 | 2026-05-19 |
| UAE9LT | Emirates | 2 | 2026-07-01 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | UAE62P | DXB → MEL | Jul 26, 11:10 UTC | Jul 26, 14:25 UTC | 3h 15m |
| 2026-07-26 | UAE62P | DXB → MEL | Jul 26, 02:00 UTC | Jul 26, 02:20 UTC | 20m |
| 2026-07-25 | UAE2VL | IAH → DXB | Jul 25, 00:30 UTC | Jul 25, 15:30 UTC | 15h 0m |
| 2026-07-24 | UAE1Y | DXB → IAH | Jul 24, 05:45 UTC | Jul 24, 21:50 UTC | 16h 5m |
| 2026-07-23 | UAE43P | MEL → DXB | Jul 23, 11:55 UTC | Jul 24, 00:50 UTC | 12h 55m |
| 2026-07-22 | UAE1CR | DXB → MEL | Jul 22, 11:10 UTC | Jul 22, 20:05 UTC | 8h 55m |
| 2026-07-21 | UAE4 | LHR → DXB | Jul 21, 20:30 UTC | Jul 22, 03:50 UTC | 7h 20m |
| 2026-07-21 | UAE70M | - | Jul 21, 10:35 UTC | Jul 21, 18:05 UTC | 7h 30m |
| 2026-07-20 | UAE88 | ZRH → DXB | Jul 20, 13:50 UTC | Jul 20, 20:35 UTC | 6h 45m |
| 2026-07-20 | UAE11M | DXB → ZRH | Jul 20, 04:55 UTC | Jul 20, 11:30 UTC | 6h 35m |
| 2026-07-19 | UAE501 | - | Jul 19, 23:50 UTC | Jul 20, 02:10 UTC | 2h 20m |
| 2026-07-19 | UAE500 | - | Jul 19, 20:30 UTC | Jul 19, 21:25 UTC | 55m |
| 2026-07-19 | UAE500 | - | Jul 19, 18:35 UTC | Jul 19, 19:00 UTC | 25m |
| 2026-07-19 | UAE569 | - | Jul 19, 00:00 UTC | Jul 19, 03:00 UTC | 3h 0m |
| 2026-07-18 | UAE568 | - | Jul 18, 18:20 UTC | Jul 18, 21:45 UTC | 3h 25m |
| 2026-07-12 | UAE5AM | - | Jul 12, 11:30 UTC | Jul 13, 01:20 UTC | 13h 50m |
| 2026-07-12 | UAE5AM | - | Jul 12, 09:10 UTC | Jul 12, 09:25 UTC | 15m |
| 2026-07-11 | UAE80T | - | Jul 11, 22:35 UTC | Jul 11, 22:55 UTC | 20m |
| 2026-07-11 | UAE80T | - | Jul 11, 10:45 UTC | Jul 11, 21:05 UTC | 10h 20m |
| 2026-07-11 | UAE80T | - | Jul 11, 07:35 UTC | Jul 11, 07:55 UTC | 20m |
| 2026-07-10 | UAE5V | - | Jul 10, 15:55 UTC | Jul 11, 04:01 UTC | 12h 6m |
| 2026-07-09 | UAE8ER | - | Jul 9, 23:10 UTC | Jul 10, 12:55 UTC | 13h 45m |
| 2026-07-09 | UAE2VL | - | Jul 9, 01:00 UTC | Jul 9, 15:40 UTC | 14h 40m |
| 2026-07-08 | UAE1Y | - | Jul 8, 08:40 UTC | Jul 8, 22:25 UTC | 13h 45m |
| 2026-07-08 | UAE1Y | - | Jul 8, 06:35 UTC | Jul 8, 07:30 UTC | 55m |
| 2026-07-07 | UAE4 | - | Jul 7, 20:35 UTC | Jul 8, 02:50 UTC | 6h 15m |
| 2026-07-07 | UAE70M | DXB → LHR | Jul 7, 11:05 UTC | Jul 7, 18:10 UTC | 7h 5m |
| 2026-07-06 | UAE5AM | AKL → DXB | Jul 6, 08:40 UTC | Jul 7, 01:10 UTC | 16h 30m |
| 2026-07-05 | UAE80T | DXB → AKL | Jul 5, 09:50 UTC | Jul 5, 22:10 UTC | 12h 20m |
| 2026-07-05 | UAE80T | DXB → AKL | Jul 5, 06:55 UTC | Jul 5, 07:20 UTC | 25m |
| 2026-07-04 | UAE5AM | AKL → DXB | Jul 4, 09:05 UTC | Jul 5, 02:05 UTC | 17h 0m |
| 2026-07-03 | UAE80T | DXB → AKL | Jul 3, 19:00 UTC | Jul 3, 21:40 UTC | 2h 40m |
| 2026-07-03 | UAE80T | DXB → AKL | Jul 3, 06:45 UTC | Jul 3, 07:10 UTC | 25m |
| 2026-07-01 | UAE39L | - | Jul 1, 20:50 UTC | Jul 2, 02:30 UTC | 5h 40m |
| 2026-07-01 | UAE9LT | DXB → MXP | Jul 1, 12:00 UTC | Jul 1, 18:10 UTC | 6h 10m |
| 2026-06-24 | UAE6 | - | Jun 24, 04:05 UTC | Jun 24, 04:34 UTC | 30m |
| 2026-06-23 | UAE6 | - | Jun 23, 21:34 UTC | Jun 24, 04:00 UTC | 6h 25m |
| 2026-06-23 | UAE4CK | DXB → LHR | Jun 23, 11:54 UTC | Jun 23, 19:10 UTC | 7h 15m |
| 2026-06-22 | UAE6 | - | Jun 22, 21:35 UTC | Jun 23, 04:39 UTC | 7h 5m |
| 2026-06-22 | UAE4CK | DXB → LHR | Jun 22, 12:10 UTC | Jun 22, 19:05 UTC | 6h 55m |
| 2026-06-19 | UAE216 | LAX → DXB | Jun 19, 00:00 UTC | Jun 19, 15:54 UTC | 15h 54m |
| 2026-06-18 | UAE83M | DXB → LAX | Jun 18, 04:35 UTC | Jun 18, 21:00 UTC | 16h 25m |
| 2026-06-16 | UAE242 | - | Jun 16, 19:10 UTC | Jun 17, 07:40 UTC | 12h 31m |
| 2026-06-16 | UAE30Y | DXB → YYZ | Jun 16, 00:35 UTC | Jun 16, 13:19 UTC | 12h 45m |
| 2026-06-15 | UAE67M | MEL → DXB | Jun 15, 08:54 UTC | Jun 15, 09:10 UTC | 15m |
| 2026-06-14 | UAE67M | MEL → DXB | Jun 14, 19:25 UTC | Jun 14, 20:10 UTC | 45m |
| 2026-06-14 | UAE62P | DXB → MEL | Jun 14, 10:40 UTC | Jun 14, 11:55 UTC | 1h 15m |
| 2026-06-13 | UAE41P | - | Jun 13, 01:00 UTC | Jun 13, 16:40 UTC | 15h 39m |
| 2026-06-12 | UAE51N | DXB → SFO | Jun 12, 18:30 UTC | Jun 12, 21:10 UTC | 2h 40m |
| 2026-06-12 | UAE75T | BNE → DXB | Jun 12, 00:30 UTC | Jun 12, 00:50 UTC | 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-EVM page for operator, model, and routing details .