sensors Mode-S transponder
89659D
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-ATF · AIRBUS A-321neo
- Hex
- 89659D
- Octal
- 42262635
- Decimal
- 9,004,445
- Country
- AE
- Tail
- A6-ATF
- Type
- A21N
- Flights observed
- 165
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 6h ago
Last known position
Country allocation
The ICAO 24-bit address 89659D 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 |
|---|---|---|---|
| ABY527 | Air Arabia | 12 | 2026-05-20 |
| ABY519 | Air Arabia | 12 | 2026-05-19 |
| ABY518 | Air Arabia | 12 | 2026-05-18 |
| ABY513 | Air Arabia | 11 | 2026-05-17 |
| ABY526 | Air Arabia | 10 | 2026-05-19 |
| ABY512 | Air Arabia | 9 | 2026-05-16 |
| ABY823 | Air Arabia | 6 | 2026-05-25 |
| ABY511 | Air Arabia | 6 | 2026-05-11 |
| ABY822 | Air Arabia | 5 | 2026-05-30 |
| ABY801 | Air Arabia | 5 | 2026-05-27 |
| ABY684 | Air Arabia | 5 | 2026-04-25 |
| ABY824 | Air Arabia | 4 | 2026-05-26 |
| ABY800 | Air Arabia | 4 | 2026-05-27 |
| ABY685 | Air Arabia | 4 | 2026-04-25 |
| ABY515 | Air Arabia | 4 | 2026-05-18 |
| ABY148 | Air Arabia | 4 | 2026-04-17 |
| ABY147 | Air Arabia | 4 | 2026-04-29 |
| ABY559 | Air Arabia | 3 | 2026-05-16 |
| ABY558 | Air Arabia | 3 | 2026-05-16 |
| ABY514 | Air Arabia | 3 | 2026-05-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | ABY822 | BKK → SHJ | May 30, 03:00 UTC | May 30, 07:30 UTC | 4h 30m |
| 2026-05-29 | ABY821 | SHJ → BKK | May 29, 11:20 UTC | May 30, 01:25 UTC | 14h 6m |
| 2026-05-29 | ABY296 | DOK → SHJ | May 29, 09:20 UTC | May 29, 09:40 UTC | 20m |
| 2026-05-28 | ABY322 | IST → SHJ | May 28, 12:00 UTC | May 28, 16:25 UTC | 4h 25m |
| 2026-05-28 | ABY321 | SHJ → IST | May 28, 06:15 UTC | May 28, 10:00 UTC | 3h 45m |
| 2026-05-27 | ABY321 | SHJ → IST | May 27, 14:40 UTC | May 28, 10:00 UTC | 19h 20m |
| 2026-05-27 | ABY155 | RUH → SHJ | May 27, 07:40 UTC | May 28, 06:30 UTC | 22h 50m |
| 2026-05-27 | ABY801 | KUL → SHJ | May 27, 03:14 UTC | May 27, 15:15 UTC | 12h 1m |
| 2026-05-27 | ABY800 | SHJ → KUL | May 27, 01:09 UTC | May 27, 01:19 UTC | 10m |
| 2026-05-26 | ABY824 | BKK → SHJ | May 26, 05:05 UTC | May 26, 21:44 UTC | 16h 40m |
| 2026-05-25 | ABY823 | SHJ → BKK | May 25, 23:04 UTC | May 26, 03:40 UTC | 4h 35m |
| 2026-05-25 | ABY823 | SHJ → BKK | May 25, 07:20 UTC | May 26, 03:40 UTC | 20h 19m |
| 2026-05-25 | ABY823 | SHJ → BKK | May 25, 06:20 UTC | May 26, 03:40 UTC | 21h 19m |
| 2026-05-25 | ABY822 | BKK → SHJ | May 25, 03:20 UTC | May 26, 03:15 UTC | 23h 55m |
| 2026-05-25 | ABY822 | BKK → SHJ | May 25, 02:40 UTC | May 25, 23:45 UTC | 21h 5m |
| 2026-05-24 | ABY822 | BKK → SHJ | May 24, 07:50 UTC | May 24, 23:46 UTC | 15h 56m |
| 2026-05-24 | ABY822 | BKK → SHJ | May 24, 04:10 UTC | May 24, 23:46 UTC | 19h 36m |
| 2026-05-23 | ABY821 | SHJ → BKK | May 23, 22:15 UTC | May 24, 02:45 UTC | 4h 30m |
| 2026-05-23 | ABY801 | KUL → SHJ | May 23, 07:15 UTC | May 23, 07:40 UTC | 25m |
| 2026-05-23 | ABY801 | KUL → SHJ | May 23, 03:05 UTC | May 23, 03:20 UTC | 15m |
| 2026-05-23 | ABY800 | SHJ → KUL | May 23, 01:00 UTC | May 23, 01:30 UTC | 30m |
| 2026-05-22 | ABY801 | KUL → SHJ | May 22, 07:00 UTC | May 22, 20:45 UTC | 13h 45m |
| 2026-05-22 | ABY801 | KUL → SHJ | May 22, 02:40 UTC | May 22, 02:55 UTC | 15m |
| 2026-05-21 | ABY800 | SHJ → KUL | May 21, 19:45 UTC | May 22, 00:45 UTC | 5h 0m |
| 2026-05-21 | ABY800 | SHJ → KUL | May 21, 17:50 UTC | May 21, 18:15 UTC | 25m |
| 2026-05-21 | ABY509 | CMB → SHJ | May 21, 10:00 UTC | May 21, 10:25 UTC | 25m |
| 2026-05-21 | ABY508 | SHJ → CMB | May 21, 07:30 UTC | May 21, 08:15 UTC | 45m |
| 2026-05-21 | ABY803 | KUL → SHJ | May 21, 00:15 UTC | May 21, 01:00 UTC | 45m |
| 2026-05-20 | ABY803 | KUL → SHJ | May 20, 20:00 UTC | May 20, 20:15 UTC | 15m |
| 2026-05-20 | ABY802 | SHJ → KUL | May 20, 17:30 UTC | May 20, 17:55 UTC | 25m |
| 2026-05-20 | ABY527 | SHJ → CGP | May 20, 02:15 UTC | May 20, 13:10 UTC | 10h 56m |
| 2026-05-19 | ABY526 | SHJ → CGP | May 19, 09:50 UTC | May 20, 00:50 UTC | 15h 0m |
| 2026-05-19 | ABY519 | DAC → SHJ | May 19, 00:20 UTC | May 19, 03:30 UTC | 3h 10m |
| 2026-05-18 | ABY518 | DAC → SHJ | May 18, 20:20 UTC | May 18, 23:05 UTC | 2h 45m |
| 2026-05-18 | ABY518 | DAC → SHJ | May 18, 19:00 UTC | May 18, 19:20 UTC | 20m |
| 2026-05-18 | ABY515 | SHJ → DAC | May 18, 11:05 UTC | May 18, 14:20 UTC | 3h 15m |
| 2026-05-17 | ABY514 | SHJ → DAC | May 17, 17:01 UTC | May 18, 09:55 UTC | 16h 55m |
| 2026-05-17 | ABY513 | DAC → SHJ | May 17, 03:35 UTC | May 17, 15:35 UTC | 12h 0m |
| 2026-05-16 | ABY512 | SHJ → DAC | May 16, 23:10 UTC | May 17, 02:20 UTC | 3h 10m |
| 2026-05-16 | ABY512 | SHJ → DAC | May 16, 21:50 UTC | May 16, 22:10 UTC | 20m |
| 2026-05-16 | ABY572 | DAC → SHJ | May 16, 14:35 UTC | May 16, 17:30 UTC | 2h 55m |
| 2026-05-16 | ABY571 | SHJ → DAC | May 16, 10:50 UTC | May 16, 13:31 UTC | 2h 40m |
| 2026-05-16 | ABY559 | MUX → SHJ | May 16, 04:05 UTC | May 16, 04:10 UTC | 5m |
| 2026-05-16 | ABY558 | SHJ → MUX | May 16, 02:45 UTC | May 16, 02:55 UTC | 10m |
| 2026-05-15 | ABY519 | DAC → SHJ | May 15, 00:10 UTC | May 15, 03:30 UTC | 3h 20m |
| 2026-05-14 | ABY518 | DAC → SHJ | May 14, 21:55 UTC | May 14, 23:00 UTC | 1h 5m |
| 2026-05-14 | ABY518 | DAC → SHJ | May 14, 19:00 UTC | May 14, 19:25 UTC | 25m |
| 2026-05-13 | ABY625 | CAI → SHJ | May 13, 13:55 UTC | May 13, 17:10 UTC | 3h 15m |
| 2026-05-13 | ABY624 | SHJ → CAI | May 13, 09:00 UTC | May 13, 10:00 UTC | 1h 0m |
| 2026-05-13 | ABY527 | SHJ → CGP | May 13, 02:05 UTC | May 13, 05:30 UTC | 3h 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-ATF page for operator, model, and routing details .