sensors Mode-S transponder
89653B
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-BND · BOEING 787-9 Dreamliner
- Hex
- 89653B
- Octal
- 42262473
- Decimal
- 9,004,347
- Country
- AE
- Tail
- A6-BND
- Type
- B789
- Flights observed
- 105
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 12h ago
Last known position
Country allocation
The ICAO 24-bit address 89653B 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 |
|---|---|---|---|
| ETD844 | Etihad Airways | 9 | 2026-05-13 |
| ETD843 | Etihad Airways | 9 | 2026-05-12 |
| ETD3P1 | Etihad Airways | 6 | 2026-05-16 |
| ETD79 | Etihad Airways | 5 | 2026-04-17 |
| ETD35Q | Etihad Airways | 4 | 2026-05-17 |
| ETD889 | Etihad Airways | 3 | 2026-05-07 |
| ETD842 | Etihad Airways | 3 | 2026-05-29 |
| ETD80 | Etihad Airways | 3 | 2026-04-18 |
| ETD9D2 | - | 2 | 2026-05-19 |
| ETD888 | Etihad Airways | 2 | 2026-05-10 |
| ETD7QB | Etihad Airways | 2 | 2026-04-23 |
| ETD7NW | Etihad Airways | 2 | 2026-05-09 |
| ETD73G | Etihad Airways | 2 | 2026-05-08 |
| ETD67B | - | 2 | 2026-05-24 |
| ETD5FA | Etihad Airways | 2 | 2026-05-27 |
| ETD475 | Etihad Airways | 2 | 2026-04-27 |
| ETD474 | Etihad Airways | 2 | 2026-04-27 |
| ETD47 | Etihad Airways | 2 | 2026-05-27 |
| ETD407 | Etihad Airways | 2 | 2026-05-28 |
| ETD378 | Etihad Airways | 2 | 2026-05-01 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | ETD842 | SVO → AUH | May 29, 09:25 UTC | May 29, 12:45 UTC | 3h 20m |
| 2026-05-29 | ETD842 | SVO → AUH | May 29, 08:25 UTC | May 29, 08:50 UTC | 25m |
| 2026-05-28 | ETD407 | BKK → AUH | May 28, 14:10 UTC | May 29, 03:00 UTC | 12h 50m |
| 2026-05-28 | ETD406 | AUH → BKK | May 28, 06:10 UTC | May 28, 10:35 UTC | 4h 25m |
| 2026-05-27 | ETD5FA | DUB → AUH | May 27, 19:55 UTC | May 28, 02:35 UTC | 6h 40m |
| 2026-05-27 | ETD47 | AUH → AGP | May 27, 12:40 UTC | May 27, 18:10 UTC | 5h 30m |
| 2026-05-25 | ETD407 | BKK → AUH | May 25, 14:10 UTC | May 25, 18:30 UTC | 4h 20m |
| 2026-05-24 | ETD128 | MUC → AUH | May 24, 20:30 UTC | May 25, 10:35 UTC | 14h 5m |
| 2026-05-24 | ETD67B | - | May 24, 13:05 UTC | May 24, 16:35 UTC | 3h 30m |
| 2026-05-23 | ETD67B | - | May 23, 16:50 UTC | May 24, 16:35 UTC | 23h 45m |
| 2026-05-23 | ETD359 | HYD → AUH | May 23, 12:35 UTC | May 23, 17:30 UTC | 4h 55m |
| 2026-05-22 | ETD8JZ | PRG → AUH | May 22, 09:25 UTC | May 22, 14:35 UTC | 5h 10m |
| 2026-05-22 | ETD9RT | - | May 22, 01:45 UTC | May 22, 05:10 UTC | 3h 25m |
| 2026-05-21 | ETD5HJ | GVA → AUH | May 21, 09:00 UTC | May 21, 14:30 UTC | 5h 30m |
| 2026-05-21 | ETD99E | AUH → GVA | May 21, 01:25 UTC | May 21, 05:30 UTC | 4h 5m |
| 2026-05-19 | ETD104A | MAD → AUH | May 19, 20:05 UTC | May 20, 01:55 UTC | 5h 50m |
| 2026-05-19 | ETD9D2 | - | May 19, 13:10 UTC | May 19, 18:10 UTC | 5h 0m |
| 2026-05-17 | ETD35Q | BCN → AUH | May 17, 09:00 UTC | May 17, 14:35 UTC | 5h 35m |
| 2026-05-16 | ETD3P1 | AUH → BCN | May 16, 23:50 UTC | May 17, 06:55 UTC | 7h 5m |
| 2026-05-16 | ETD437 | - | May 16, 13:55 UTC | May 16, 18:30 UTC | 4h 35m |
| 2026-05-16 | ETD436 | - | May 16, 06:20 UTC | May 16, 10:46 UTC | 4h 25m |
| 2026-05-15 | ETD5FA | DUB → AUH | May 15, 20:05 UTC | May 16, 02:15 UTC | 6h 10m |
| 2026-05-15 | ETD47 | AUH → AGP | May 15, 12:45 UTC | May 15, 18:15 UTC | 5h 29m |
| 2026-05-14 | ETD2NP | MAN → AUH | May 14, 20:00 UTC | May 15, 02:20 UTC | 6h 20m |
| 2026-05-14 | ETD2KQ | AUH → MAN | May 14, 13:15 UTC | May 14, 17:50 UTC | 4h 35m |
| 2026-05-13 | ETD844 | SVO → AUH | May 13, 20:30 UTC | May 14, 03:05 UTC | 6h 35m |
| 2026-05-12 | ETD843 | AUH → SVO | May 12, 21:10 UTC | May 13, 15:45 UTC | 18h 35m |
| 2026-05-12 | ETD844 | SVO → AUH | May 12, 20:20 UTC | May 12, 20:40 UTC | 20m |
| 2026-05-11 | ETD843 | AUH → SVO | May 11, 21:30 UTC | May 12, 15:30 UTC | 18h 0m |
| 2026-05-10 | ETD888 | AUH → PKX | May 10, 00:15 UTC | May 10, 00:30 UTC | 15m |
| 2026-05-09 | ETD7NW | KUL → AUH | May 9, 05:10 UTC | May 9, 19:35 UTC | 14h 25m |
| 2026-05-09 | ETD7NW | KUL → AUH | May 9, 02:15 UTC | May 9, 02:30 UTC | 15m |
| 2026-05-08 | ETD73G | AUH → KUL | May 8, 05:14 UTC | May 9, 00:10 UTC | 18h 55m |
| 2026-05-08 | ETD73G | AUH → KUL | May 8, 01:45 UTC | May 9, 00:10 UTC | 22h 25m |
| 2026-05-07 | ETD889 | PKX → AUH | May 7, 19:35 UTC | May 7, 19:45 UTC | 10m |
| 2026-05-07 | ETD889 | PKX → AUH | May 7, 12:10 UTC | May 7, 17:35 UTC | 5h 25m |
| 2026-05-06 | ETD35Q | BCN → AUH | May 6, 09:10 UTC | May 7, 00:10 UTC | 14h 59m |
| 2026-05-05 | ETD3P1 | AUH → BCN | May 5, 10:50 UTC | May 6, 06:30 UTC | 19h 40m |
| 2026-05-05 | ETD4EA | CPH → AUH | May 5, 09:25 UTC | May 6, 06:30 UTC | 21h 5m |
| 2026-05-05 | ETD1UH | AUH → CPH | May 5, 02:20 UTC | May 5, 06:05 UTC | 3h 45m |
| 2026-05-04 | ETD2MJ | - | May 4, 20:20 UTC | May 4, 20:30 UTC | 10m |
| 2026-05-04 | ETD2MJ | - | May 4, 17:10 UTC | May 4, 18:30 UTC | 1h 20m |
| 2026-05-04 | ETD238 | AUH → BLR | May 4, 11:30 UTC | May 4, 14:40 UTC | 3h 10m |
| 2026-05-03 | ETD9XU | MAN → AUH | May 3, 09:00 UTC | May 3, 16:00 UTC | 7h 0m |
| 2026-05-02 | ETD49D | AUH → MAN | May 2, 11:10 UTC | May 3, 05:55 UTC | 18h 44m |
| 2026-05-01 | ETD378 | BAH → AUH | May 1, 20:20 UTC | May 2, 08:35 UTC | 12h 15m |
| 2026-04-30 | ETD842 | SVO → AUH | Apr 30, 23:35 UTC | May 1, 14:55 UTC | 15h 20m |
| 2026-04-30 | ETD899 | TPE → AUH | Apr 30, 11:50 UTC | Apr 30, 20:45 UTC | 8h 55m |
| 2026-04-29 | ETD898 | AUH → TPE | Apr 29, 18:05 UTC | Apr 30, 01:40 UTC | 7h 34m |
| 2026-04-29 | ETD26W | MAD → AUH | Apr 29, 08:20 UTC | Apr 29, 14:40 UTC | 6h 21m |
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-BND page for operator, model, and routing details .