sensors Mode-S transponder
89655E
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-EVR · AIRBUS A-380-800
- Hex
- 89655E
- Octal
- 42262536
- Decimal
- 9,004,382
- Country
- AE
- Tail
- A6-EVR
- Type
- A388
- Flights observed
- 161
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 57m ago
Last known position
Country allocation
The ICAO 24-bit address 89655E 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 | 13 | 2026-06-23 |
| UAE5AM | Emirates | 13 | 2026-06-24 |
| UAE8ER | Emirates | 10 | 2026-07-08 |
| UAE5CL | Emirates | 9 | 2026-07-02 |
| UAE51N | - | 9 | 2026-07-12 |
| UAE5V | - | 7 | 2026-07-09 |
| UAE41P | - | 7 | 2026-07-13 |
| UAE373 | Emirates | 6 | 2026-07-04 |
| UAE372 | - | 6 | 2026-07-04 |
| UAE67M | - | 5 | 2026-07-05 |
| UAE62P | - | 5 | 2026-07-14 |
| UAE500 | - | 5 | 2026-07-06 |
| UAE414 | Emirates | 5 | 2026-06-29 |
| UAE3HJ | Emirates | 5 | 2026-07-01 |
| UAE83M | Emirates | 4 | 2026-06-27 |
| UAE501 | - | 4 | 2026-07-06 |
| UAE216 | Emirates | 4 | 2026-06-28 |
| UAE1DP | Emirates | 4 | 2026-06-29 |
| UAE569 | Emirates | 3 | 2026-06-05 |
| UAE568 | Emirates | 3 | 2026-06-05 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | UAE62P | - | Jul 14, 09:00 UTC | Jul 14, 11:30 UTC | 2h 30m |
| 2026-07-13 | UAE62P | - | Jul 13, 23:25 UTC | Jul 13, 23:45 UTC | 20m |
| 2026-07-13 | UAE41P | - | Jul 13, 01:30 UTC | Jul 13, 16:40 UTC | 15h 10m |
| 2026-07-12 | UAE51N | - | Jul 12, 05:45 UTC | Jul 12, 22:35 UTC | 16h 50m |
| 2026-07-12 | UAE75T | - | Jul 12, 00:35 UTC | Jul 12, 00:55 UTC | 20m |
| 2026-07-11 | UAE75T | - | Jul 11, 11:15 UTC | Jul 11, 23:10 UTC | 11h 55m |
| 2026-07-10 | UAE434 | - | Jul 10, 10:25 UTC | Jul 10, 20:25 UTC | 10h 0m |
| 2026-07-10 | UAE434 | - | Jul 10, 07:20 UTC | Jul 10, 07:45 UTC | 25m |
| 2026-07-09 | UAE5V | - | Jul 9, 15:45 UTC | Jul 10, 04:00 UTC | 12h 15m |
| 2026-07-08 | UAE8ER | DXB → JFK | Jul 8, 23:10 UTC | Jul 9, 12:45 UTC | 13h 35m |
| 2026-07-08 | UAE2VL | - | Jul 8, 02:40 UTC | Jul 8, 17:05 UTC | 14h 25m |
| 2026-07-07 | UAE1Y | - | Jul 7, 06:05 UTC | Jul 7, 22:20 UTC | 16h 15m |
| 2026-07-06 | UAE501 | - | Jul 6, 23:55 UTC | Jul 7, 02:25 UTC | 2h 30m |
| 2026-07-06 | UAE500 | - | Jul 6, 18:40 UTC | Jul 6, 21:25 UTC | 2h 45m |
| 2026-07-05 | UAE67M | - | Jul 5, 19:30 UTC | Jul 6, 09:00 UTC | 13h 30m |
| 2026-07-04 | UAE62P | - | Jul 4, 23:25 UTC | Jul 5, 12:00 UTC | 12h 35m |
| 2026-07-04 | UAE373 | BKK → DXB | Jul 4, 14:45 UTC | Jul 4, 20:20 UTC | 5h 35m |
| 2026-07-04 | UAE372 | - | Jul 4, 10:00 UTC | Jul 4, 12:40 UTC | 2h 40m |
| 2026-07-04 | UAE372 | - | Jul 4, 06:30 UTC | Jul 4, 07:00 UTC | 30m |
| 2026-07-02 | UAE5CL | SYD → DXB | Jul 2, 11:35 UTC | Jul 3, 01:25 UTC | 13h 50m |
| 2026-07-02 | UAE5CL | SYD → DXB | Jul 2, 07:50 UTC | Jul 2, 08:35 UTC | 45m |
| 2026-07-02 | UAE5CL | SYD → DXB | Jul 2, 05:35 UTC | Jul 2, 05:45 UTC | 10m |
| 2026-07-01 | UAE3HJ | DXB → SYD | Jul 1, 22:40 UTC | Jul 2, 01:10 UTC | 2h 30m |
| 2026-07-01 | UAE3HJ | DXB → SYD | Jul 1, 19:30 UTC | Jul 1, 20:20 UTC | 50m |
| 2026-07-01 | UAE3HJ | DXB → SYD | Jul 1, 07:20 UTC | Jul 1, 07:45 UTC | 25m |
| 2026-06-30 | UAE501 | - | Jun 30, 23:45 UTC | Jul 1, 02:05 UTC | 2h 20m |
| 2026-06-30 | UAE500 | DST → BOM | Jun 30, 18:20 UTC | Jun 30, 21:10 UTC | 2h 50m |
| 2026-06-29 | UAE1DP | SYD → DXB | Jun 29, 20:09 UTC | Jun 30, 09:55 UTC | 13h 46m |
| 2026-06-29 | UAE414 | DXB → SYD | Jun 29, 08:14 UTC | Jun 29, 12:05 UTC | 3h 50m |
| 2026-06-28 | UAE414 | DXB → SYD | Jun 28, 22:49 UTC | Jun 28, 23:09 UTC | 20m |
| 2026-06-28 | UAE216 | LAX → DXB | Jun 28, 00:04 UTC | Jun 28, 16:25 UTC | 16h 20m |
| 2026-06-27 | UAE83M | DXB → LAX | Jun 27, 04:54 UTC | Jun 27, 21:10 UTC | 16h 15m |
| 2026-06-26 | UAE216 | LAX → DXB | Jun 26, 00:05 UTC | Jun 26, 16:24 UTC | 16h 20m |
| 2026-06-25 | UAE83M | DXB → LAX | Jun 25, 04:54 UTC | Jun 25, 21:29 UTC | 16h 35m |
| 2026-06-24 | UAE5AM | AKL → DXB | Jun 24, 08:45 UTC | Jun 25, 00:49 UTC | 16h 5m |
| 2026-06-23 | UAE80T | DXB → AKL | Jun 23, 21:29 UTC | Jun 23, 21:49 UTC | 20m |
| 2026-06-23 | UAE80T | DXB → AKL | Jun 23, 08:35 UTC | Jun 23, 19:55 UTC | 11h 20m |
| 2026-06-23 | UAE80T | DXB → AKL | Jun 23, 06:44 UTC | Jun 23, 06:59 UTC | 15m |
| 2026-06-22 | UAE5AM | AKL → DXB | Jun 22, 08:50 UTC | Jun 23, 01:25 UTC | 16h 35m |
| 2026-06-21 | UAE80T | DXB → AKL | Jun 21, 10:04 UTC | Jun 21, 22:10 UTC | 12h 5m |
| 2026-06-21 | UAE80T | DXB → AKL | Jun 21, 06:50 UTC | Jun 21, 07:14 UTC | 25m |
| 2026-06-20 | UAE5AM | AKL → DXB | Jun 20, 11:49 UTC | Jun 21, 01:14 UTC | 13h 25m |
| 2026-06-20 | UAE5AM | AKL → DXB | Jun 20, 08:44 UTC | Jun 20, 09:05 UTC | 20m |
| 2026-06-19 | UAE80T | DXB → AKL | Jun 19, 16:19 UTC | Jun 19, 22:09 UTC | 5h 50m |
| 2026-06-19 | UAE80T | DXB → AKL | Jun 19, 06:49 UTC | Jun 19, 07:14 UTC | 25m |
| 2026-06-18 | UAE39L | MXP → DXB | Jun 18, 20:25 UTC | Jun 19, 02:35 UTC | 6h 9m |
| 2026-06-18 | UAE9LT | DXB → MXP | Jun 18, 11:45 UTC | Jun 18, 17:55 UTC | 6h 10m |
| 2026-06-17 | UAE5V | JFK → DXB | Jun 17, 16:15 UTC | Jun 18, 04:35 UTC | 12h 20m |
| 2026-06-16 | UAE8ER | DXB → JFK | Jun 16, 22:50 UTC | Jun 17, 12:25 UTC | 13h 35m |
| 2026-06-16 | UAE216 | LAX → DXB | Jun 16, 00:05 UTC | Jun 16, 16:25 UTC | 16h 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-EVR page for operator, model, and routing details .