sensors Mode-S transponder
89618E
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-EEO · AIRBUS A-380-800
- Hex
- 89618E
- Octal
- 42260616
- Decimal
- 9,003,406
- Country
- AE
- Tail
- A6-EEO
- Type
- A388
- Flights observed
- 143
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 2h ago
Last known position
Country allocation
The ICAO 24-bit address 89618E 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 |
|---|---|---|---|
| UAE242 | Emirates | 18 | 2026-07-23 |
| UAE30Y | Emirates | 17 | 2026-07-23 |
| UAE2LT | - | 11 | 2026-07-18 |
| UAE2K | Emirates | 10 | 2026-07-25 |
| UAE804 | - | 8 | 2026-07-16 |
| UAE353 | Emirates | 5 | 2026-05-09 |
| UAE7Q | Emirates | 4 | 2026-06-07 |
| UAE322 | - | 4 | 2026-07-09 |
| UAE15K | Emirates | 4 | 2026-06-06 |
| UAE93P | Emirates | 3 | 2026-07-24 |
| UAE903 | Emirates | 3 | 2026-06-16 |
| UAE7V | Emirates | 3 | 2026-07-24 |
| UAE78L | Emirates | 3 | 2026-07-22 |
| UAE71J | - | 3 | 2026-07-10 |
| UAE6JL | Emirates | 3 | 2026-07-22 |
| UAE5W | - | 3 | 2026-06-16 |
| UAE363 | Emirates | 3 | 2026-06-16 |
| UAE352 | Emirates | 3 | 2026-05-09 |
| UAE323 | - | 3 | 2026-07-09 |
| UAE1EW | - | 3 | 2026-07-10 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-25 | UAE2K | DXB → CAI | Jul 25, 11:45 UTC | Jul 25, 12:45 UTC | 1h 0m |
| 2026-07-24 | UAE93P | CDG → DXB | Jul 24, 20:30 UTC | Jul 25, 03:30 UTC | 7h 0m |
| 2026-07-24 | UAE7V | DXB → CDG | Jul 24, 10:55 UTC | Jul 24, 18:10 UTC | 7h 15m |
| 2026-07-23 | UAE242 | YYZ → DXB | Jul 23, 19:00 UTC | Jul 24, 07:45 UTC | 12h 45m |
| 2026-07-23 | UAE30Y | DXB → YYZ | Jul 23, 00:15 UTC | Jul 23, 14:05 UTC | 13h 50m |
| 2026-07-22 | UAE78L | FCO → DXB | Jul 22, 14:15 UTC | Jul 22, 20:05 UTC | 5h 50m |
| 2026-07-22 | UAE6JL | DXB → FCO | Jul 22, 10:20 UTC | Jul 22, 11:50 UTC | 1h 30m |
| 2026-07-21 | UAE377 | BKK → DXB | Jul 21, 20:15 UTC | Jul 22, 01:55 UTC | 5h 40m |
| 2026-07-21 | UAE376 | DXB → BKK | Jul 21, 01:40 UTC | Jul 21, 08:05 UTC | 6h 25m |
| 2026-07-20 | UAE6FJ | - | Jul 20, 13:50 UTC | Jul 20, 18:20 UTC | 4h 30m |
| 2026-07-20 | UAE9N | DXB → IST | Jul 20, 07:00 UTC | Jul 20, 11:25 UTC | 4h 25m |
| 2026-07-18 | UAE2LT | - | Jul 18, 17:55 UTC | Jul 18, 21:20 UTC | 3h 25m |
| 2026-07-18 | UAE2K | - | Jul 18, 12:05 UTC | Jul 18, 15:10 UTC | 3h 5m |
| 2026-07-17 | UAE242 | - | Jul 17, 19:15 UTC | Jul 18, 08:35 UTC | 13h 21m |
| 2026-07-16 | UAE30Y | - | Jul 16, 23:55 UTC | Jul 17, 13:45 UTC | 13h 50m |
| 2026-07-16 | UAE804 | - | Jul 16, 13:20 UTC | Jul 16, 20:45 UTC | 7h 25m |
| 2026-07-16 | UAE242 | - | Jul 16, 06:45 UTC | Jul 16, 08:20 UTC | 1h 35m |
| 2026-07-15 | UAE242 | - | Jul 15, 19:25 UTC | Jul 16, 05:40 UTC | 10h 15m |
| 2026-07-15 | UAE30Y | - | Jul 15, 00:40 UTC | Jul 15, 14:20 UTC | 13h 40m |
| 2026-07-13 | UAE5T | - | Jul 13, 14:00 UTC | Jul 13, 19:35 UTC | 5h 35m |
| 2026-07-13 | UAE9CL | - | Jul 13, 05:31 UTC | Jul 13, 11:45 UTC | 6h 15m |
| 2026-07-12 | UAE2LT | - | Jul 12, 18:30 UTC | Jul 12, 21:35 UTC | 3h 5m |
| 2026-07-12 | UAE2K | - | Jul 12, 12:15 UTC | Jul 12, 14:40 UTC | 2h 25m |
| 2026-07-11 | UAE242 | - | Jul 11, 19:25 UTC | Jul 12, 08:01 UTC | 12h 35m |
| 2026-07-11 | UAE30Y | - | Jul 11, 00:00 UTC | Jul 11, 13:30 UTC | 13h 30m |
| 2026-07-10 | UAE71J | - | Jul 10, 10:35 UTC | Jul 10, 14:00 UTC | 3h 25m |
| 2026-07-10 | UAE1EW | - | Jul 10, 05:30 UTC | Jul 10, 08:05 UTC | 2h 35m |
| 2026-07-09 | UAE323 | - | Jul 9, 23:30 UTC | Jul 9, 23:50 UTC | 20m |
| 2026-07-09 | UAE323 | - | Jul 9, 15:15 UTC | Jul 9, 22:25 UTC | 7h 10m |
| 2026-07-09 | UAE322 | - | Jul 9, 08:10 UTC | Jul 9, 08:35 UTC | 25m |
| 2026-07-09 | UAE322 | - | Jul 9, 00:50 UTC | Jul 9, 07:20 UTC | 6h 30m |
| 2026-07-02 | UAE6FJ | IST → DXB | Jul 2, 13:50 UTC | Jul 2, 17:40 UTC | 3h 50m |
| 2026-07-02 | UAE9N | - | Jul 2, 07:30 UTC | Jul 2, 11:45 UTC | 4h 15m |
| 2026-07-01 | UAE323 | ICN → DXB | Jul 1, 15:05 UTC | Jul 2, 00:15 UTC | 9h 10m |
| 2026-07-01 | UAE322 | - | Jul 1, 08:50 UTC | Jul 1, 09:20 UTC | 30m |
| 2026-07-01 | UAE322 | - | Jul 1, 01:15 UTC | Jul 1, 08:00 UTC | 6h 45m |
| 2026-06-29 | UAE93P | - | Jun 29, 21:24 UTC | Jun 30, 03:45 UTC | 6h 21m |
| 2026-06-29 | UAE7V | DXB → CDG | Jun 29, 11:10 UTC | Jun 29, 17:40 UTC | 6h 30m |
| 2026-06-28 | UAE242 | - | Jun 28, 19:14 UTC | Jun 29, 07:34 UTC | 12h 20m |
| 2026-06-27 | UAE30Y | DXB → YYZ | Jun 27, 23:45 UTC | Jun 28, 13:00 UTC | 13h 15m |
| 2026-06-27 | UAE804 | - | Jun 27, 12:04 UTC | Jun 27, 19:59 UTC | 7h 55m |
| 2026-06-26 | UAE2LT | CAI → DXB | Jun 26, 17:19 UTC | Jun 26, 20:20 UTC | 3h 0m |
| 2026-06-26 | UAE2K | - | Jun 26, 11:45 UTC | Jun 26, 14:50 UTC | 3h 5m |
| 2026-06-25 | UAE242 | - | Jun 25, 19:15 UTC | Jun 26, 07:39 UTC | 12h 25m |
| 2026-06-24 | UAE30Y | DXB → YYZ | Jun 24, 23:50 UTC | Jun 25, 13:29 UTC | 13h 40m |
| 2026-06-24 | UAE78L | FCO → DXB | Jun 24, 14:15 UTC | Jun 24, 19:44 UTC | 5h 30m |
| 2026-06-24 | UAE6JL | - | Jun 24, 05:44 UTC | Jun 24, 11:14 UTC | 5h 30m |
| 2026-06-23 | UAE78L | FCO → DXB | Jun 23, 14:04 UTC | Jun 23, 19:44 UTC | 5h 40m |
| 2026-06-23 | UAE6JL | - | Jun 23, 05:24 UTC | Jun 23, 11:04 UTC | 5h 40m |
| 2026-06-22 | UAE367 | TPE → DXB | Jun 22, 23:29 UTC | Jun 22, 23: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-EEO page for operator, model, and routing details .