sensors Mode-S transponder
89645A
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-EUE · AIRBUS A-380-800
- Hex
- 89645A
- Octal
- 42262132
- Decimal
- 9,004,122
- Country
- AE
- Tail
- A6-EUE
- Type
- A388
- Flights observed
- 36
- Distinct callsigns
- 19
- Country
- AE
- Last broadcast
- 26d ago
Last known position
Country allocation
The ICAO 24-bit address 89645A 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 19 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| UAE262 | Emirates | 4 | 2026-05-12 |
| UAE80T | Emirates | 3 | 2026-05-03 |
| UAE70M | Emirates | 3 | 2026-05-02 |
| UAE4 | Emirates | 3 | 2026-05-02 |
| UAE381 | Emirates | 3 | 2026-04-29 |
| UAE261 | Emirates | 3 | 2026-05-11 |
| UAE5AM | Emirates | 2 | 2026-05-05 |
| UAE380 | Emirates | 2 | 2026-04-28 |
| UAE373 | Emirates | 2 | 2026-04-24 |
| UAE2 | Emirates | 2 | 2026-05-13 |
| UAE98P | Emirates | 1 | 2026-05-10 |
| UAE501 | Emirates | 1 | 2026-05-07 |
| UAE500 | Emirates | 1 | 2026-05-06 |
| UAE4PY | Emirates | 1 | 2026-05-05 |
| UAE39 | Emirates | 1 | 2026-05-10 |
| UAE372 | Emirates | 1 | 2026-04-24 |
| UAE2506 | - | 1 | 2026-04-23 |
| UAE1J | Emirates | 1 | 2026-05-05 |
| UAE1 | Emirates | 1 | 2026-04-25 |
Recent flights last 36
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-13 | UAE2 | LHR → DXB | May 13, 14:40 UTC | May 13, 21:15 UTC | 6h 35m |
| 2026-05-12 | UAE262 | GRU → DXB | May 12, 18:45 UTC | May 12, 19:05 UTC | 20m |
| 2026-05-12 | UAE262 | GRU → DXB | May 12, 04:45 UTC | May 12, 11:35 UTC | 6h 50m |
| 2026-05-11 | UAE261 | DXB → GRU | May 11, 05:20 UTC | May 11, 20:05 UTC | 14h 45m |
| 2026-05-10 | UAE98P | BHX → DXB | May 10, 14:00 UTC | May 10, 21:14 UTC | 7h 15m |
| 2026-05-10 | UAE39 | DXB → BHX | May 10, 05:45 UTC | May 10, 10:55 UTC | 5h 10m |
| 2026-05-08 | UAE262 | GRU → DXB | May 8, 04:54 UTC | May 8, 19:05 UTC | 14h 10m |
| 2026-05-07 | UAE261 | DXB → GRU | May 7, 06:40 UTC | May 7, 21:45 UTC | 15h 5m |
| 2026-05-07 | UAE501 | BOM → DXB | May 7, 01:30 UTC | May 7, 01:50 UTC | 20m |
| 2026-05-06 | UAE500 | DXB → BOM | May 6, 18:40 UTC | May 6, 19:00 UTC | 20m |
| 2026-05-05 | UAE1J | LHR → DXB | May 5, 19:15 UTC | May 6, 02:10 UTC | 6h 55m |
| 2026-05-05 | UAE4PY | DXB → LHR | May 5, 08:00 UTC | May 5, 16:00 UTC | 8h 0m |
| 2026-05-05 | UAE5AM | AKL → DXB | May 5, 01:15 UTC | May 5, 01:30 UTC | 15m |
| 2026-05-04 | UAE5AM | AKL → DXB | May 4, 09:00 UTC | May 4, 23:30 UTC | 14h 31m |
| 2026-05-03 | UAE80T | DXB → AKL | May 3, 21:35 UTC | May 3, 22:00 UTC | 25m |
| 2026-05-03 | UAE80T | DXB → AKL | May 3, 09:50 UTC | May 3, 20:00 UTC | 10h 10m |
| 2026-05-03 | UAE80T | DXB → AKL | May 3, 06:50 UTC | May 3, 07:10 UTC | 20m |
| 2026-05-02 | UAE4 | LHR → DXB | May 2, 20:20 UTC | May 3, 03:20 UTC | 7h 0m |
| 2026-05-02 | UAE70M | DXB → LHR | May 2, 09:40 UTC | May 2, 17:30 UTC | 7h 50m |
| 2026-04-30 | UAE262 | GRU → DXB | Apr 30, 05:05 UTC | Apr 30, 19:05 UTC | 14h 0m |
| 2026-04-29 | UAE261 | DXB → GRU | Apr 29, 05:50 UTC | Apr 29, 20:40 UTC | 14h 51m |
| 2026-04-29 | UAE381 | HKG → DXB | Apr 29, 00:25 UTC | Apr 29, 00:45 UTC | 20m |
| 2026-04-28 | UAE381 | HKG → DXB | Apr 28, 19:05 UTC | Apr 28, 21:10 UTC | 2h 5m |
| 2026-04-28 | UAE381 | HKG → DXB | Apr 28, 16:55 UTC | Apr 28, 17:10 UTC | 15m |
| 2026-04-28 | UAE380 | DXB → HKG | Apr 28, 12:40 UTC | Apr 28, 13:10 UTC | 30m |
| 2026-04-28 | UAE380 | DXB → HKG | Apr 28, 06:15 UTC | Apr 28, 10:35 UTC | 4h 20m |
| 2026-04-27 | UAE4 | LHR → DXB | Apr 27, 19:55 UTC | Apr 28, 02:50 UTC | 6h 55m |
| 2026-04-27 | UAE70M | DXB → LHR | Apr 27, 09:20 UTC | Apr 27, 17:40 UTC | 8h 20m |
| 2026-04-26 | UAE4 | LHR → DXB | Apr 26, 20:05 UTC | Apr 27, 02:55 UTC | 6h 50m |
| 2026-04-26 | UAE70M | DXB → LHR | Apr 26, 09:35 UTC | Apr 26, 17:35 UTC | 8h 0m |
| 2026-04-25 | UAE2 | LHR → DXB | Apr 25, 14:00 UTC | Apr 25, 20:55 UTC | 6h 55m |
| 2026-04-25 | UAE1 | DXB → LHR | Apr 25, 03:25 UTC | Apr 25, 11:40 UTC | 8h 15m |
| 2026-04-24 | UAE373 | BKK → DXB | Apr 24, 20:20 UTC | Apr 24, 20:45 UTC | 25m |
| 2026-04-24 | UAE373 | BKK → DXB | Apr 24, 14:40 UTC | Apr 24, 18:30 UTC | 3h 50m |
| 2026-04-24 | UAE372 | DXB → BKK | Apr 24, 06:05 UTC | Apr 24, 11:50 UTC | 5h 45m |
| 2026-04-23 | UAE2506 | - | Apr 23, 02:15 UTC | Apr 23, 02:30 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-EUE page for operator, model, and routing details .