sensors Mode-S transponder
89655F
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-EVS · AIRBUS A-380-800
- Hex
- 89655F
- Octal
- 42262537
- Decimal
- 9,004,383
- Country
- AE
- Tail
- A6-EVS
- Type
- A388
- Flights observed
- 172
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- Jul 26, 20:40 UTC
Last known position
Country allocation
The ICAO 24-bit address 89655F 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 | Emirates | 27 | 2026-07-24 |
| UAE5AM | Emirates | 23 | 2026-07-25 |
| UAE41P | - | 19 | 2026-07-10 |
| UAE51N | - | 16 | 2026-07-09 |
| UAE1Y | Emirates | 7 | 2026-06-30 |
| UAE62P | - | 5 | 2026-07-11 |
| UAE319 | Emirates | 5 | 2026-06-12 |
| UAE261 | Emirates | 5 | 2026-07-26 |
| UAE83M | - | 4 | 2026-07-19 |
| UAE75T | Emirates | 4 | 2026-06-05 |
| UAE2VL | Emirates | 4 | 2026-07-01 |
| UAE262 | Emirates | 4 | 2026-07-05 |
| UAE9LT | Emirates | 3 | 2026-07-23 |
| UAE8ER | Emirates | 3 | 2026-06-01 |
| UAE5V | Emirates | 3 | 2026-06-02 |
| UAE569 | - | 3 | 2026-06-29 |
| UAE568 | Emirates | 3 | 2026-06-29 |
| UAE4CK | - | 3 | 2026-07-12 |
| UAE434 | Emirates | 3 | 2026-06-03 |
| UAE318 | Emirates | 3 | 2026-06-11 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | UAE261 | DXB → GRU | Jul 26, 06:05 UTC | Jul 26, 20:40 UTC | 14h 36m |
| 2026-07-25 | UAE5AM | AKL → DXB | Jul 25, 11:45 UTC | Jul 26, 01:20 UTC | 13h 35m |
| 2026-07-25 | UAE5AM | AKL → DXB | Jul 25, 08:45 UTC | Jul 25, 09:00 UTC | 15m |
| 2026-07-24 | UAE80T | DXB → AKL | Jul 24, 21:40 UTC | Jul 24, 21:55 UTC | 15m |
| 2026-07-24 | UAE80T | DXB → AKL | Jul 24, 10:40 UTC | Jul 24, 20:05 UTC | 9h 25m |
| 2026-07-24 | UAE80T | DXB → AKL | Jul 24, 07:25 UTC | Jul 24, 07:50 UTC | 25m |
| 2026-07-23 | UAE39L | MXP → DXB | Jul 23, 21:15 UTC | Jul 24, 03:45 UTC | 6h 30m |
| 2026-07-23 | UAE9LT | DXB → MXP | Jul 23, 12:25 UTC | Jul 23, 18:45 UTC | 6h 20m |
| 2026-07-20 | UAE216 | - | Jul 20, 00:15 UTC | Jul 20, 16:30 UTC | 16h 15m |
| 2026-07-19 | UAE83M | - | Jul 19, 05:00 UTC | Jul 19, 21:45 UTC | 16h 45m |
| 2026-07-18 | UAE216 | - | Jul 18, 00:04 UTC | Jul 18, 16:00 UTC | 15h 56m |
| 2026-07-17 | UAE83M | - | Jul 17, 18:05 UTC | Jul 17, 21:25 UTC | 3h 20m |
| 2026-07-17 | UAE83M | - | Jul 17, 04:44 UTC | Jul 17, 05:04 UTC | 20m |
| 2026-07-16 | UAE5AM | - | Jul 16, 10:55 UTC | Jul 17, 00:30 UTC | 13h 35m |
| 2026-07-16 | UAE5AM | - | Jul 16, 08:50 UTC | Jul 16, 09:05 UTC | 15m |
| 2026-07-15 | UAE80T | - | Jul 15, 23:15 UTC | Jul 15, 23:45 UTC | 30m |
| 2026-07-15 | UAE80T | - | Jul 15, 08:25 UTC | Jul 15, 08:50 UTC | 25m |
| 2026-07-14 | UAE5AM | - | Jul 14, 09:30 UTC | Jul 15, 01:55 UTC | 16h 24m |
| 2026-07-13 | UAE80T | - | Jul 13, 22:05 UTC | Jul 13, 22:20 UTC | 15m |
| 2026-07-13 | UAE80T | - | Jul 13, 10:20 UTC | Jul 13, 20:25 UTC | 10h 5m |
| 2026-07-13 | UAE80T | - | Jul 13, 07:15 UTC | Jul 13, 07:40 UTC | 25m |
| 2026-07-12 | UAE6 | - | Jul 12, 22:15 UTC | Jul 13, 04:40 UTC | 6h 25m |
| 2026-07-12 | UAE4CK | - | Jul 12, 12:40 UTC | Jul 12, 19:55 UTC | 7h 15m |
| 2026-07-11 | UAE67M | - | Jul 11, 19:30 UTC | Jul 12, 08:55 UTC | 13h 25m |
| 2026-07-11 | UAE62P | - | Jul 11, 10:55 UTC | Jul 11, 12:05 UTC | 1h 10m |
| 2026-07-10 | UAE62P | - | Jul 10, 23:35 UTC | Jul 11, 00:00 UTC | 25m |
| 2026-07-10 | UAE41P | - | Jul 10, 01:20 UTC | Jul 10, 16:45 UTC | 15h 25m |
| 2026-07-09 | UAE51N | - | Jul 9, 19:40 UTC | Jul 9, 22:10 UTC | 2h 30m |
| 2026-07-09 | UAE51N | - | Jul 9, 05:50 UTC | Jul 9, 06:15 UTC | 25m |
| 2026-07-07 | UAE5AM | AKL → DXB | Jul 7, 11:35 UTC | Jul 8, 01:00 UTC | 13h 25m |
| 2026-07-07 | UAE5AM | AKL → DXB | Jul 7, 08:50 UTC | Jul 7, 09:05 UTC | 15m |
| 2026-07-06 | UAE80T | DXB → AKL | Jul 6, 22:00 UTC | Jul 6, 22:25 UTC | 25m |
| 2026-07-06 | UAE80T | DXB → AKL | Jul 6, 10:10 UTC | Jul 6, 20:25 UTC | 10h 15m |
| 2026-07-06 | UAE80T | DXB → AKL | Jul 6, 07:05 UTC | Jul 6, 07:25 UTC | 20m |
| 2026-07-05 | UAE262 | GRU → DXB | Jul 5, 04:10 UTC | Jul 5, 18:20 UTC | 14h 10m |
| 2026-07-04 | UAE261 | DXB → GRU | Jul 4, 05:55 UTC | Jul 4, 20:25 UTC | 14h 30m |
| 2026-07-03 | UAE35Q | - | Jul 3, 21:00 UTC | Jul 4, 02:25 UTC | 5h 25m |
| 2026-07-03 | UAE1DM | DXB → MUC | Jul 3, 12:50 UTC | Jul 3, 18:45 UTC | 5h 55m |
| 2026-07-02 | UAE1DP | - | Jul 2, 20:25 UTC | Jul 3, 10:10 UTC | 13h 45m |
| 2026-07-02 | UAE414 | CBX → SYD | Jul 2, 11:15 UTC | Jul 2, 11:50 UTC | 35m |
| 2026-07-01 | UAE414 | - | Jul 1, 22:45 UTC | Jul 1, 23:05 UTC | 20m |
| 2026-07-01 | UAE2VL | IAH → DXB | Jul 1, 00:55 UTC | Jul 1, 15:30 UTC | 14h 35m |
| 2026-06-30 | UAE1Y | DXB → IAH | Jun 30, 05:45 UTC | Jun 30, 21:15 UTC | 15h 30m |
| 2026-06-29 | UAE569 | - | Jun 29, 23:44 UTC | Jun 30, 02:50 UTC | 3h 6m |
| 2026-06-29 | UAE568 | DXB → BLR | Jun 29, 17:59 UTC | Jun 29, 21:24 UTC | 3h 25m |
| 2026-06-28 | UAE67M | MEL → DXB | Jun 28, 19:34 UTC | Jun 29, 08:35 UTC | 13h 0m |
| 2026-06-28 | UAE62P | DXB → MEL | Jun 28, 12:35 UTC | Jun 28, 12:39 UTC | 5m |
| 2026-06-28 | UAE62P | DXB → MEL | Jun 28, 08:44 UTC | Jun 28, 11:55 UTC | 3h 10m |
| 2026-06-27 | UAE62P | DXB → MEL | Jun 27, 23:14 UTC | Jun 27, 23:34 UTC | 20m |
| 2026-06-27 | UAE8UW | - | Jun 27, 03:15 UTC | Jun 27, 15:24 UTC | 12h 10m |
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-EVS page for operator, model, and routing details .