sensors Mode-S transponder
89638D
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-ANT · AIRBUS A-320
- Hex
- 89638D
- Octal
- 42261615
- Decimal
- 9,003,917
- Country
- AE
- Tail
- A6-ANT
- Type
- A320
- Flights observed
- 114
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 14h ago
Last known position
Country allocation
The ICAO 24-bit address 89638D 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 |
|---|---|---|---|
| ABY338 | Air Arabia | 6 | 2026-06-03 |
| ABY530 | Air Arabia | 5 | 2026-06-11 |
| ABY442 | Air Arabia | 5 | 2026-06-06 |
| ABY531 | Air Arabia | 4 | 2026-06-11 |
| ABY443 | Air Arabia | 4 | 2026-06-01 |
| ABY337 | Air Arabia | 4 | 2026-06-03 |
| ABY520 | Air Arabia | 3 | 2026-05-30 |
| ABY492 | Air Arabia | 3 | 2026-05-21 |
| ABY463 | Air Arabia | 3 | 2026-05-01 |
| ABY435 | Air Arabia | 3 | 2026-06-06 |
| ABY426 | Air Arabia | 3 | 2026-06-04 |
| ABY410 | Air Arabia | 3 | 2026-05-27 |
| ABY104 | Air Arabia | 3 | 2026-06-03 |
| ABY102 | Air Arabia | 3 | 2026-06-11 |
| ABY834 | Air Arabia | 2 | 2026-05-10 |
| ABY833 | Air Arabia | 2 | 2026-05-19 |
| ABY588 | Air Arabia | 2 | 2026-06-02 |
| ABY587 | Air Arabia | 2 | 2026-06-02 |
| ABY521 | Air Arabia | 2 | 2026-05-31 |
| ABY496 | Air Arabia | 2 | 2026-05-09 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-14 | ABY455 | SHJ → HYD | Jun 14, 00:00 UTC | Jun 14, 00:10 UTC | 10m |
| 2026-06-13 | ABY419 | - | Jun 13, 00:25 UTC | Jun 13, 01:15 UTC | 50m |
| 2026-06-12 | ABY418 | SHJ → AMD | Jun 12, 22:10 UTC | Jun 12, 22:55 UTC | 45m |
| 2026-06-11 | ABY531 | KTM → SHJ | Jun 11, 17:45 UTC | Jun 11, 20:25 UTC | 2h 40m |
| 2026-06-11 | ABY530 | SHJ → KTM | Jun 11, 14:30 UTC | Jun 11, 16:05 UTC | 1h 35m |
| 2026-06-11 | ABY530 | SHJ → KTM | Jun 11, 12:20 UTC | Jun 11, 12:40 UTC | 20m |
| 2026-06-11 | ABY102 | BAH → SHJ | Jun 11, 07:40 UTC | Jun 11, 08:35 UTC | 55m |
| 2026-06-11 | ABY101 | SHJ → BAH | Jun 11, 04:50 UTC | Jun 11, 06:30 UTC | 1h 40m |
| 2026-06-10 | ABY531 | KTM → SHJ | Jun 10, 17:50 UTC | Jun 10, 20:30 UTC | 2h 40m |
| 2026-06-10 | ABY530 | SHJ → KTM | Jun 10, 04:00 UTC | Jun 10, 16:10 UTC | 12h 10m |
| 2026-06-09 | ABY546 | KHI → SHJ | Jun 9, 09:35 UTC | Jun 9, 09:55 UTC | 20m |
| 2026-06-09 | ABY152 | RUH → SHJ | Jun 9, 06:35 UTC | Jun 9, 07:00 UTC | 25m |
| 2026-06-07 | ABY286 | SAW → SHJ | Jun 7, 23:00 UTC | Jun 8, 03:00 UTC | 4h 0m |
| 2026-06-07 | ABY285 | SHJ → SAW | Jun 7, 07:40 UTC | Jun 7, 20:50 UTC | 13h 10m |
| 2026-06-06 | ABY435 | SHJ → JAI | Jun 6, 22:10 UTC | Jun 6, 22:25 UTC | 15m |
| 2026-06-06 | ABY442 | TRV → SHJ | Jun 6, 12:35 UTC | Jun 6, 12:54 UTC | 20m |
| 2026-06-06 | ABY442 | TRV → SHJ | Jun 6, 09:04 UTC | Jun 6, 09:30 UTC | 25m |
| 2026-06-05 | ABY322 | IST → SHJ | Jun 5, 11:35 UTC | Jun 6, 01:05 UTC | 13h 30m |
| 2026-06-05 | ABY321 | SHJ → IST | Jun 5, 09:30 UTC | Jun 5, 09:55 UTC | 25m |
| 2026-06-05 | ABY419 | SHJ → NAG | Jun 5, 00:35 UTC | Jun 5, 06:30 UTC | 5h 55m |
| 2026-06-04 | ABY418 | SHJ → AMD | Jun 4, 22:20 UTC | Jun 4, 23:15 UTC | 55m |
| 2026-06-04 | ABY427 | SHJ → COK | Jun 4, 14:15 UTC | Jun 4, 14:30 UTC | 15m |
| 2026-06-04 | ABY426 | COK → SHJ | Jun 4, 12:45 UTC | Jun 4, 13:10 UTC | 25m |
| 2026-06-03 | ABY616 | ATZ → SHJ | Jun 3, 23:00 UTC | Jun 4, 02:45 UTC | 3h 45m |
| 2026-06-03 | ABY615 | SHJ → ATZ | Jun 3, 18:10 UTC | Jun 3, 21:35 UTC | 3h 25m |
| 2026-06-03 | ABY104 | BAH → SHJ | Jun 3, 15:00 UTC | Jun 3, 15:50 UTC | 50m |
| 2026-06-03 | ABY338 | AMM → SHJ | Jun 3, 10:15 UTC | Jun 3, 10:50 UTC | 35m |
| 2026-06-03 | ABY338 | AMM → SHJ | Jun 3, 08:25 UTC | Jun 3, 08:35 UTC | 10m |
| 2026-06-03 | ABY337 | SHJ → AMM | Jun 3, 07:00 UTC | Jun 3, 07:15 UTC | 15m |
| 2026-06-03 | ABY337 | SHJ → AMM | Jun 3, 04:30 UTC | Jun 3, 05:15 UTC | 45m |
| 2026-06-02 | ABY588 | CMB → SHJ | Jun 2, 21:55 UTC | Jun 2, 22:30 UTC | 35m |
| 2026-06-02 | ABY587 | SHJ → CMB | Jun 2, 09:35 UTC | Jun 2, 20:10 UTC | 10h 35m |
| 2026-06-01 | ABY436 | JAI → SHJ | Jun 1, 23:45 UTC | Jun 2, 20:10 UTC | 20h 25m |
| 2026-06-01 | ABY435 | SHJ → JAI | Jun 1, 21:55 UTC | Jun 1, 22:15 UTC | 20m |
| 2026-06-01 | ABY435 | SHJ → JAI | Jun 1, 19:50 UTC | Jun 1, 20:15 UTC | 25m |
| 2026-06-01 | ABY443 | TRV → SHJ | Jun 1, 14:00 UTC | Jun 1, 14:25 UTC | 25m |
| 2026-05-31 | ABY521 | SHJ → CGP | May 31, 15:35 UTC | May 31, 18:50 UTC | 3h 15m |
| 2026-05-30 | ABY520 | SHJ → CGP | May 30, 21:30 UTC | May 31, 14:00 UTC | 16h 30m |
| 2026-05-30 | ABY443 | TRV → SHJ | May 30, 14:15 UTC | May 30, 14:25 UTC | 10m |
| 2026-05-30 | ABY442 | TRV → SHJ | May 30, 12:20 UTC | May 30, 12:55 UTC | 35m |
| 2026-05-29 | ABY442 | TRV → SHJ | May 29, 13:20 UTC | May 30, 12:55 UTC | 23h 35m |
| 2026-05-29 | ABY247 | EVN → SHJ | May 29, 12:50 UTC | May 29, 13:35 UTC | 45m |
| 2026-05-28 | ABY338 | AMM → SHJ | May 28, 11:20 UTC | May 29, 07:45 UTC | 20h 25m |
| 2026-05-28 | ABY338 | AMM → SHJ | May 28, 11:10 UTC | May 29, 07:45 UTC | 20h 35m |
| 2026-05-28 | ABY338 | AMM → SHJ | May 28, 09:30 UTC | May 28, 09:40 UTC | 10m |
| 2026-05-28 | ABY337 | SHJ → AMM | May 28, 07:10 UTC | May 28, 07:20 UTC | 10m |
| 2026-05-27 | ABY411 | CJB → SHJ | May 27, 23:05 UTC | May 27, 23:25 UTC | 20m |
| 2026-05-27 | ABY410 | NAG → SHJ | May 27, 11:05 UTC | May 27, 21:50 UTC | 10h 45m |
| 2026-05-26 | ABY245 | EVN → SHJ | May 26, 17:50 UTC | May 27, 11:10 UTC | 17h 21m |
| 2026-05-25 | ABY423 | COK → SHJ | May 25, 23:14 UTC | May 25, 23:24 UTC | 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-ANT page for operator, model, and routing details .