sensors Mode-S transponder
89656F
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-BMJ · BOEING 787-10 Dreamliner
- Hex
- 89656F
- Octal
- 42262557
- Decimal
- 9,004,399
- Country
- AE
- Tail
- A6-BMJ
- Type
- B78X
- Flights observed
- 254
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- Jul 26, 15:05 UTC
Last known position
Country allocation
The ICAO 24-bit address 89656F 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 |
|---|---|---|---|
| ETD477 | Etihad Airways | 13 | 2026-06-02 |
| ETD476 | Etihad Airways | 13 | 2026-06-02 |
| ETD843 | Etihad Airways | 12 | 2026-06-23 |
| ETD79H | Etihad Airways | 10 | 2026-06-04 |
| ETD7LE | - | 9 | 2026-07-10 |
| ETD72W | Etihad Airways | 9 | 2026-07-22 |
| ETD49D | Etihad Airways | 9 | 2026-07-25 |
| ETD475 | - | 8 | 2026-07-14 |
| ETD14P | Etihad Airways | 8 | 2026-06-03 |
| ETD844 | - | 7 | 2026-06-24 |
| ETD474 | - | 7 | 2026-07-14 |
| ETD9XU | Etihad Airways | 6 | 2026-07-25 |
| ETD7BR | Etihad Airways | 6 | 2026-06-05 |
| ETD3JC | - | 6 | 2026-07-10 |
| ETD4AJ | Etihad Airways | 5 | 2026-06-05 |
| ETD36V | - | 5 | 2026-07-13 |
| ETD26N | - | 5 | 2026-07-12 |
| ETD98V | Etihad Airways | 4 | 2026-04-19 |
| ETD889 | Etihad Airways | 4 | 2026-07-24 |
| ETD888 | Etihad Airways | 4 | 2026-07-24 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | ETD26W | MAD → AUH | Jul 26, 08:10 UTC | Jul 26, 15:05 UTC | 6h 55m |
| 2026-07-25 | ETD5H3 | - | Jul 25, 23:20 UTC | Jul 26, 05:55 UTC | 6h 35m |
| 2026-07-25 | ETD9XU | MAN → AUH | Jul 25, 08:25 UTC | Jul 25, 15:40 UTC | 7h 15m |
| 2026-07-25 | ETD49D | AUH → MAN | Jul 25, 06:05 UTC | Jul 25, 06:10 UTC | 5m |
| 2026-07-24 | ETD49D | AUH → MAN | Jul 24, 22:25 UTC | Jul 25, 06:00 UTC | 7h 35m |
| 2026-07-24 | ETD889 | PKX → AUH | Jul 24, 19:10 UTC | Jul 24, 19:35 UTC | 25m |
| 2026-07-24 | ETD889 | PKX → AUH | Jul 24, 12:00 UTC | Jul 24, 12:10 UTC | 10m |
| 2026-07-24 | ETD888 | AUH → PKX | Jul 24, 00:05 UTC | Jul 24, 00:20 UTC | 15m |
| 2026-07-23 | ETD888 | - | Jul 23, 17:35 UTC | Jul 23, 18:05 UTC | 30m |
| 2026-07-23 | ETD411 | KUL → AUH | Jul 23, 07:50 UTC | Jul 23, 08:15 UTC | 25m |
| 2026-07-22 | ETD410 | - | Jul 22, 17:40 UTC | Jul 23, 06:25 UTC | 12h 45m |
| 2026-07-22 | ETD72W | AUH → DUB | Jul 22, 01:20 UTC | Jul 22, 15:05 UTC | 13h 45m |
| 2026-07-21 | ETD72W | AUH → DUB | Jul 21, 15:50 UTC | Jul 22, 15:05 UTC | 23h 15m |
| 2026-07-21 | ETD72W | AUH → DUB | Jul 21, 14:35 UTC | Jul 22, 13:00 UTC | 22h 25m |
| 2026-07-21 | ETD431 | - | Jul 21, 03:50 UTC | Jul 22, 03:45 UTC | 23h 55m |
| 2026-07-21 | ETD431 | - | Jul 21, 02:10 UTC | Jul 22, 01:45 UTC | 23h 35m |
| 2026-07-21 | ETD432 | AUH → HAN | Jul 21, 00:05 UTC | Jul 21, 18:25 UTC | 18h 20m |
| 2026-07-20 | ETD432 | AUH → HAN | Jul 20, 22:35 UTC | Jul 21, 18:25 UTC | 19h 49m |
| 2026-07-20 | ETD35Q | BCN → AUH | Jul 20, 11:05 UTC | Jul 20, 17:35 UTC | 6h 30m |
| 2026-07-20 | ETD3P1 | AUH → BCN | Jul 20, 03:05 UTC | Jul 20, 06:55 UTC | 3h 50m |
| 2026-07-19 | ETD358 | - | Jul 19, 02:55 UTC | Jul 19, 21:10 UTC | 18h 15m |
| 2026-07-18 | ETD73G | - | Jul 18, 18:20 UTC | Jul 19, 00:55 UTC | 6h 35m |
| 2026-07-18 | ETD9XU | MAN → AUH | Jul 18, 08:50 UTC | Jul 18, 15:25 UTC | 6h 35m |
| 2026-07-17 | ETD49D | - | Jul 17, 14:30 UTC | Jul 18, 06:20 UTC | 15h 51m |
| 2026-07-16 | ETD431 | - | Jul 16, 21:50 UTC | Jul 17, 18:15 UTC | 20h 25m |
| 2026-07-16 | ETD431 | - | Jul 16, 19:50 UTC | Jul 17, 18:15 UTC | 22h 25m |
| 2026-07-16 | ETD432 | - | Jul 16, 17:49 UTC | Jul 17, 16:24 UTC | 22h 35m |
| 2026-07-16 | ETD432 | - | Jul 16, 17:40 UTC | Jul 17, 15:44 UTC | 22h 5m |
| 2026-07-15 | ETD410 | - | Jul 15, 18:45 UTC | Jul 16, 08:20 UTC | 13h 35m |
| 2026-07-15 | ETD9XU | - | Jul 15, 09:00 UTC | Jul 15, 16:20 UTC | 7h 20m |
| 2026-07-14 | ETD49D | - | Jul 14, 22:35 UTC | Jul 15, 06:00 UTC | 7h 24m |
| 2026-07-14 | ETD475 | - | Jul 14, 12:20 UTC | Jul 14, 18:50 UTC | 6h 30m |
| 2026-07-14 | ETD475 | - | Jul 14, 11:35 UTC | Jul 14, 11:50 UTC | 15m |
| 2026-07-14 | ETD474 | - | Jul 14, 02:10 UTC | Jul 14, 02:30 UTC | 20m |
| 2026-07-13 | ETD474 | - | Jul 13, 18:40 UTC | Jul 14, 01:40 UTC | 7h 0m |
| 2026-07-13 | ETD36V | - | Jul 13, 10:15 UTC | Jul 13, 15:55 UTC | 5h 40m |
| 2026-07-12 | ETD26N | - | Jul 12, 22:40 UTC | Jul 13, 04:30 UTC | 5h 50m |
| 2026-07-11 | ETD1QN | - | Jul 11, 10:10 UTC | Jul 11, 15:10 UTC | 5h 0m |
| 2026-07-10 | ETD3BU | AYM → VIE | Jul 10, 23:05 UTC | Jul 11, 04:15 UTC | 5h 10m |
| 2026-07-10 | ETD3JC | - | Jul 10, 14:10 UTC | Jul 10, 20:20 UTC | 6h 10m |
| 2026-07-10 | ETD7LE | - | Jul 10, 05:00 UTC | Jul 10, 11:45 UTC | 6h 45m |
| 2026-07-09 | ETD80 | - | Jul 9, 21:10 UTC | Jul 10, 02:40 UTC | 5h 30m |
| 2026-07-09 | ETD79 | AUH → MXP | Jul 9, 10:55 UTC | Jul 9, 16:50 UTC | 5h 55m |
| 2026-07-08 | ETD410 | AUH → HKT | Jul 8, 18:30 UTC | Jul 9, 08:05 UTC | 13h 35m |
| 2026-07-08 | ETD36V | - | Jul 8, 10:25 UTC | Jul 8, 15:50 UTC | 5h 25m |
| 2026-07-07 | ETD26N | - | Jul 7, 23:05 UTC | Jul 8, 04:40 UTC | 5h 35m |
| 2026-07-07 | ETD475 | - | Jul 7, 15:20 UTC | Jul 7, 18:30 UTC | 3h 10m |
| 2026-07-07 | ETD475 | - | Jul 7, 11:25 UTC | Jul 7, 11:35 UTC | 10m |
| 2026-07-06 | ETD474 | AUH → CGK | Jul 6, 18:20 UTC | Jul 7, 01:15 UTC | 6h 55m |
| 2026-07-06 | ETD1QN | - | Jul 6, 10:10 UTC | Jul 6, 15:15 UTC | 5h 5m |
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-BMJ page for operator, model, and routing details .