sensors Mode-S transponder
896741
ICAO 24-bit transponder address · allocated to United Arab Emirates
- Hex
- 896741
- Octal
- 42263501
- Decimal
- 9,004,865
- Country
- AE
- Flights observed
- 102
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 21m ago
Current position
Country allocation
The ICAO 24-bit address 896741 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 |
|---|---|---|---|
| ABY687 | Air Arabia | 8 | 2026-06-21 |
| ABY823 | - | 6 | 2026-06-17 |
| ABY819 | - | 5 | 2026-06-30 |
| ABY696 | Air Arabia | 5 | 2026-06-23 |
| ABY695 | Air Arabia | 5 | 2026-06-23 |
| ABY824 | - | 4 | 2026-06-18 |
| ABY298 | Air Arabia | 4 | 2026-06-19 |
| ABY297 | Air Arabia | 4 | 2026-06-21 |
| ABY818 | - | 3 | 2026-06-30 |
| ABY794 | Air Arabia | 3 | 2026-07-03 |
| ABY793 | Air Arabia | 3 | 2026-07-03 |
| ABY685 | - | 3 | 2026-06-27 |
| ABY502 | - | 3 | 2026-06-24 |
| ABY299 | Air Arabia | 3 | 2026-06-19 |
| ABY296 | Air Arabia | 3 | 2026-06-21 |
| ABY816 | Air Arabia | 2 | 2026-06-16 |
| ABY688 | - | 2 | 2026-06-21 |
| ABY503 | - | 2 | 2026-06-25 |
| ABY388 | Air Arabia | 2 | 2026-06-03 |
| ABY998 | Air Arabia | 1 | 2026-05-08 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-04 | ABY241 | - | Jul 4, 21:25 UTC | Jul 5, 00:15 UTC | 2h 50m |
| 2026-07-04 | ABY240 | - | Jul 4, 13:45 UTC | Jul 4, 20:05 UTC | 6h 20m |
| 2026-07-03 | ABY464 | DEL → SHJ | Jul 3, 23:30 UTC | Jul 4, 02:40 UTC | 3h 10m |
| 2026-07-03 | ABY463 | SHJ → DEL | Jul 3, 19:25 UTC | Jul 3, 22:20 UTC | 2h 55m |
| 2026-07-03 | ABY794 | BGY → SHJ | Jul 3, 12:10 UTC | Jul 3, 17:50 UTC | 5h 40m |
| 2026-07-03 | ABY793 | SHJ → BGY | Jul 3, 04:30 UTC | Jul 3, 10:50 UTC | 6h 20m |
| 2026-07-02 | ABY714 | - | Jul 2, 04:20 UTC | Jul 2, 18:00 UTC | 13h 40m |
| 2026-07-01 | ABY794 | BGY → SHJ | Jul 1, 12:10 UTC | Jul 1, 18:05 UTC | 5h 55m |
| 2026-07-01 | ABY793 | SHJ → BGY | Jul 1, 04:35 UTC | Jul 1, 10:45 UTC | 6h 10m |
| 2026-06-30 | ABY819 | ATH → SHJ | Jun 30, 20:55 UTC | Jul 1, 01:10 UTC | 4h 15m |
| 2026-06-30 | ABY818 | SHJ → ATH | Jun 30, 15:00 UTC | Jun 30, 19:35 UTC | 4h 35m |
| 2026-06-30 | ABY091 | - | Jun 30, 04:10 UTC | Jun 30, 13:30 UTC | 9h 20m |
| 2026-06-29 | ABY708 | SHJ → SHJ | Jun 29, 14:04 UTC | Jun 30, 00:45 UTC | 10h 40m |
| 2026-06-28 | ABY956 | SHJ → SHJ | Jun 28, 10:50 UTC | Jun 29, 03:49 UTC | 17h 0m |
| 2026-06-27 | ABY685 | ATH → SHJ | Jun 27, 11:39 UTC | Jun 27, 16:04 UTC | 4h 25m |
| 2026-06-27 | ABY684 | SHJ → ATH | Jun 27, 05:25 UTC | Jun 27, 10:14 UTC | 4h 50m |
| 2026-06-27 | ABY436 | - | Jun 27, 00:25 UTC | Jun 27, 02:35 UTC | 2h 10m |
| 2026-06-26 | ABY435 | - | Jun 26, 19:35 UTC | Jun 26, 22:29 UTC | 2h 55m |
| 2026-06-26 | ABY794 | BGY → SHJ | Jun 26, 12:00 UTC | Jun 26, 17:54 UTC | 5h 55m |
| 2026-06-26 | ABY793 | SHJ → BGY | Jun 26, 04:24 UTC | Jun 26, 10:35 UTC | 6h 10m |
| 2026-06-25 | ABY546 | SHJ → SHJ | Jun 25, 09:29 UTC | Jun 25, 14:04 UTC | 4h 35m |
| 2026-06-25 | ABY503 | - | Jun 25, 00:35 UTC | Jun 25, 04:20 UTC | 3h 45m |
| 2026-06-24 | ABY502 | - | Jun 24, 22:14 UTC | Jun 24, 23:00 UTC | 45m |
| 2026-06-24 | ABY493 | - | Jun 24, 06:59 UTC | Jun 24, 12:04 UTC | 5h 5m |
| 2026-06-24 | ABY492 | - | Jun 24, 05:09 UTC | Jun 24, 05:40 UTC | 30m |
| 2026-06-23 | ABY696 | BGY → SHJ | Jun 23, 21:10 UTC | Jun 24, 03:40 UTC | 6h 30m |
| 2026-06-23 | ABY695 | SHJ → BGY | Jun 23, 13:09 UTC | Jun 23, 19:29 UTC | 6h 20m |
| 2026-06-23 | ABY513 | - | Jun 23, 03:15 UTC | Jun 23, 06:15 UTC | 3h 0m |
| 2026-06-22 | ABY512 | - | Jun 22, 21:40 UTC | Jun 23, 01:59 UTC | 4h 20m |
| 2026-06-21 | ABY688 | - | Jun 21, 22:15 UTC | Jun 22, 10:19 UTC | 12h 5m |
| 2026-06-21 | ABY687 | SHJ → HKT | Jun 21, 20:09 UTC | Jun 21, 20:34 UTC | 25m |
| 2026-06-21 | ABY297 | TBS → SHJ | Jun 21, 11:15 UTC | Jun 21, 15:49 UTC | 4h 35m |
| 2026-06-21 | ABY296 | DOK → SHJ | Jun 21, 05:54 UTC | Jun 21, 09:40 UTC | 3h 45m |
| 2026-06-20 | ABY696 | BGY → SHJ | Jun 20, 21:25 UTC | Jun 21, 04:20 UTC | 6h 55m |
| 2026-06-20 | ABY695 | SHJ → BGY | Jun 20, 13:09 UTC | Jun 20, 19:19 UTC | 6h 10m |
| 2026-06-19 | ABY687 | SHJ → HKT | Jun 19, 21:34 UTC | Jun 20, 08:19 UTC | 10h 45m |
| 2026-06-19 | ABY687 | SHJ → HKT | Jun 19, 20:09 UTC | Jun 19, 20:29 UTC | 20m |
| 2026-06-19 | ABY299 | SHJ → HRK | Jun 19, 11:45 UTC | Jun 19, 16:19 UTC | 4h 35m |
| 2026-06-19 | ABY298 | SHJ → TBS | Jun 19, 06:20 UTC | Jun 19, 10:09 UTC | 3h 50m |
| 2026-06-18 | ABY696 | BGY → SHJ | Jun 18, 21:10 UTC | Jun 19, 04:10 UTC | 6h 59m |
| 2026-06-18 | ABY695 | SHJ → BGY | Jun 18, 13:10 UTC | Jun 18, 19:15 UTC | 6h 5m |
| 2026-06-18 | ABY824 | - | Jun 18, 04:40 UTC | Jun 18, 09:05 UTC | 4h 25m |
| 2026-06-17 | ABY823 | - | Jun 17, 22:35 UTC | Jun 18, 03:20 UTC | 4h 45m |
| 2026-06-17 | ABY823 | - | Jun 17, 21:05 UTC | Jun 17, 21:30 UTC | 25m |
| 2026-06-17 | ABY824 | - | Jun 17, 04:30 UTC | Jun 17, 07:00 UTC | 2h 30m |
| 2026-06-16 | ABY823 | - | Jun 16, 22:25 UTC | Jun 17, 03:15 UTC | 4h 50m |
| 2026-06-16 | ABY823 | SHJ → SHJ | Jun 16, 21:00 UTC | Jun 16, 21:25 UTC | 25m |
| 2026-06-16 | ABY817 | BKK → SHJ | Jun 16, 12:35 UTC | Jun 16, 17:05 UTC | 4h 30m |
| 2026-06-16 | ABY816 | SHJ → BKK | Jun 16, 06:20 UTC | Jun 16, 11:25 UTC | 5h 5m |
| 2026-06-16 | ABY816 | SHJ → BKK | Jun 16, 04:55 UTC | Jun 16, 05:25 UTC | 30m |
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.