sensors Mode-S transponder
89647A
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-EUP · AIRBUS A-380-800
- Hex
- 89647A
- Octal
- 42262172
- Decimal
- 9,004,154
- Country
- AE
- Tail
- A6-EUP
- Type
- A388
- Flights observed
- 60
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 19d ago
Last known position
Country allocation
The ICAO 24-bit address 89647A 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 |
|---|---|---|---|
| UAE369 | Emirates | 9 | 2026-06-05 |
| UAE398 | - | 7 | 2026-06-18 |
| UAE399 | Emirates | 6 | 2026-06-19 |
| UAE368 | Emirates | 6 | 2026-06-05 |
| UAE98P | Emirates | 4 | 2026-05-13 |
| UAE39 | Emirates | 4 | 2026-05-13 |
| UAE9YT | Emirates | 3 | 2026-06-17 |
| UAE5GU | Emirates | 3 | 2026-05-24 |
| UAE58Q | Emirates | 3 | 2026-05-24 |
| UAE7X | - | 2 | 2026-06-17 |
| UAE7Q | Emirates | 2 | 2026-04-13 |
| UAE367 | Emirates | 2 | 2026-05-18 |
| UAE2503 | Emirates | 2 | 2026-05-26 |
| UAE702 | Emirates | 1 | 2026-04-17 |
| UAE366 | Emirates | 1 | 2026-05-18 |
| UAE2582 | - | 1 | 2026-06-24 |
| UAE2506 | - | 1 | 2026-05-03 |
| UAE2504 | Emirates | 1 | 2026-04-27 |
| UAE20 | Emirates | 1 | 2026-04-26 |
| UAE19 | Emirates | 1 | 2026-04-26 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-24 | UAE2582 | - | Jun 24, 14:00 UTC | Jun 24, 20:40 UTC | 6h 40m |
| 2026-06-19 | UAE399 | DPS → DXB | Jun 19, 00:55 UTC | Jun 19, 01:15 UTC | 20m |
| 2026-06-18 | UAE398 | - | Jun 18, 07:30 UTC | Jun 18, 23:30 UTC | 16h 0m |
| 2026-06-18 | UAE398 | - | Jun 18, 05:45 UTC | Jun 18, 06:10 UTC | 25m |
| 2026-06-17 | UAE9YT | MRU → DXB | Jun 17, 23:35 UTC | Jun 18, 00:00 UTC | 25m |
| 2026-06-17 | UAE7X | - | Jun 17, 06:40 UTC | Jun 17, 07:00 UTC | 20m |
| 2026-06-16 | UAE398 | - | Jun 16, 05:45 UTC | Jun 17, 01:20 UTC | 19h 36m |
| 2026-06-16 | UAE399 | DPS → DXB | Jun 16, 01:19 UTC | Jun 16, 01:40 UTC | 20m |
| 2026-06-15 | UAE398 | - | Jun 15, 08:04 UTC | Jun 15, 23:50 UTC | 15h 45m |
| 2026-06-15 | UAE399 | DPS → DXB | Jun 15, 01:04 UTC | Jun 15, 01:25 UTC | 20m |
| 2026-06-14 | UAE398 | - | Jun 14, 07:35 UTC | Jun 14, 23:35 UTC | 15h 59m |
| 2026-06-13 | UAE399 | DPS → DXB | Jun 13, 01:50 UTC | Jun 13, 02:05 UTC | 15m |
| 2026-06-12 | UAE398 | DXB → DPS | Jun 12, 07:25 UTC | Jun 13, 00:20 UTC | 16h 55m |
| 2026-06-11 | UAE399 | DPS → DXB | Jun 11, 07:25 UTC | Jun 12, 01:20 UTC | 17h 56m |
| 2026-06-10 | UAE399 | DPS → DXB | Jun 10, 07:25 UTC | Jun 11, 01:15 UTC | 17h 50m |
| 2026-06-06 | UAE398 | DXB → DPS | Jun 6, 07:25 UTC | Jun 7, 01:24 UTC | 18h 0m |
| 2026-06-05 | UAE369 | DPS → DXB | Jun 5, 20:35 UTC | Jun 5, 20:55 UTC | 20m |
| 2026-06-05 | UAE368 | DXB → DPS | Jun 5, 02:10 UTC | Jun 5, 19:05 UTC | 16h 55m |
| 2026-06-04 | UAE369 | DPS → DXB | Jun 4, 20:20 UTC | Jun 4, 20:50 UTC | 30m |
| 2026-06-04 | UAE369 | DPS → DXB | Jun 4, 02:40 UTC | Jun 4, 19:00 UTC | 16h 20m |
| 2026-06-03 | UAE369 | DPS → DXB | Jun 3, 20:15 UTC | Jun 3, 20:40 UTC | 25m |
| 2026-06-03 | UAE368 | DXB → DPS | Jun 3, 02:35 UTC | Jun 3, 18:50 UTC | 16h 15m |
| 2026-05-26 | UAE2503 | DXB → LHR | May 26, 14:20 UTC | May 26, 14:35 UTC | 15m |
| 2026-05-24 | UAE5GU | DUS → DXB | May 24, 13:50 UTC | May 24, 20:35 UTC | 6h 45m |
| 2026-05-24 | UAE58Q | DXB → DUS | May 24, 07:10 UTC | May 24, 11:15 UTC | 4h 5m |
| 2026-05-22 | UAE369 | DPS → DXB | May 22, 06:20 UTC | May 22, 20:50 UTC | 14h 30m |
| 2026-05-22 | UAE369 | DPS → DXB | May 22, 02:00 UTC | May 22, 20:50 UTC | 18h 50m |
| 2026-05-20 | UAE5GU | DUS → DXB | May 20, 13:55 UTC | May 20, 20:25 UTC | 6h 30m |
| 2026-05-20 | UAE58Q | DXB → DUS | May 20, 07:25 UTC | May 20, 11:35 UTC | 4h 10m |
| 2026-05-18 | UAE367 | TPE → DXB | May 18, 23:25 UTC | May 18, 23:45 UTC | 20m |
| 2026-05-18 | UAE367 | TPE → DXB | May 18, 15:10 UTC | May 18, 22:20 UTC | 7h 9m |
| 2026-05-18 | UAE366 | DXB → TPE | May 18, 01:50 UTC | May 18, 08:05 UTC | 6h 15m |
| 2026-05-15 | UAE9YT | MRU → DXB | May 15, 23:50 UTC | May 16, 00:20 UTC | 30m |
| 2026-05-14 | UAE369 | DPS → DXB | May 14, 20:15 UTC | May 14, 20:50 UTC | 35m |
| 2026-05-14 | UAE368 | DXB → DPS | May 14, 06:10 UTC | May 14, 14:30 UTC | 8h 20m |
| 2026-05-14 | UAE368 | DXB → DPS | May 14, 00:15 UTC | May 14, 00:40 UTC | 25m |
| 2026-05-13 | UAE98P | BHX → DXB | May 13, 14:00 UTC | May 13, 21:05 UTC | 7h 5m |
| 2026-05-13 | UAE39 | DXB → BHX | May 13, 05:35 UTC | May 13, 10:40 UTC | 5h 5m |
| 2026-05-06 | UAE2503 | DXB → LHR | May 6, 06:35 UTC | May 6, 06:50 UTC | 15m |
| 2026-05-05 | UAE98P | BHX → DXB | May 5, 16:00 UTC | May 5, 23:05 UTC | 7h 5m |
| 2026-05-05 | UAE39 | DXB → BHX | May 5, 05:25 UTC | May 5, 13:25 UTC | 8h 0m |
| 2026-05-04 | UAE5GU | DUS → DXB | May 4, 13:35 UTC | May 4, 20:15 UTC | 6h 41m |
| 2026-05-04 | UAE58Q | DXB → DUS | May 4, 03:54 UTC | May 4, 11:05 UTC | 7h 10m |
| 2026-05-03 | UAE2506 | - | May 3, 13:40 UTC | May 3, 14:00 UTC | 20m |
| 2026-04-27 | UAE2504 | LGW → DXB | Apr 27, 16:55 UTC | Apr 27, 17:10 UTC | 15m |
| 2026-04-26 | UAE20 | MAN → DXB | Apr 26, 20:45 UTC | Apr 27, 03:55 UTC | 7h 10m |
| 2026-04-26 | UAE19 | DXB → MAN | Apr 26, 10:00 UTC | Apr 26, 18:20 UTC | 8h 20m |
| 2026-04-25 | UAE369 | DPS → DXB | Apr 25, 02:45 UTC | Apr 25, 20:45 UTC | 18h 0m |
| 2026-04-25 | UAE368 | DXB → DPS | Apr 25, 00:50 UTC | Apr 25, 01:10 UTC | 20m |
| 2026-04-24 | UAE98P | BHX → DXB | Apr 24, 14:20 UTC | Apr 24, 21:45 UTC | 7h 25m |
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-EUP page for operator, model, and routing details .