sensors Mode-S transponder
896327
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-ETJ · BOEING 777-300ER
- Hex
- 896327
- Octal
- 42261447
- Decimal
- 9,003,815
- Country
- AE
- Tail
- A6-ETJ
- Type
- B77W
- Flights observed
- 170
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 6h ago
Last known position
Country allocation
The ICAO 24-bit address 896327 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 |
|---|---|---|---|
| ETD446 | - | 17 | 2026-07-09 |
| ETD479 | - | 11 | 2026-07-14 |
| ETD447 | - | 11 | 2026-07-09 |
| ETD440 | Etihad Airways | 9 | 2026-06-11 |
| ETD441 | Etihad Airways | 8 | 2026-06-12 |
| ETD7QB | Etihad Airways | 6 | 2026-05-31 |
| ETD430 | Etihad Airways | 6 | 2026-05-17 |
| ETD14P | Etihad Airways | 6 | 2026-06-10 |
| ETD843 | - | 5 | 2026-07-11 |
| ETD478 | - | 5 | 2026-07-14 |
| ETD432 | - | 5 | 2026-06-30 |
| ETD400 | - | 5 | 2026-06-22 |
| ETD871 | Etihad Airways | 4 | 2026-04-25 |
| ETD870 | Etihad Airways | 4 | 2026-04-25 |
| ETD597 | Etihad Airways | 4 | 2026-05-31 |
| ETD477 | Etihad Airways | 4 | 2026-07-19 |
| ETD433 | Etihad Airways | 4 | 2026-06-06 |
| ETD431 | Etihad Airways | 4 | 2026-07-01 |
| ETD72W | Etihad Airways | 3 | 2026-05-07 |
| ETD49D | - | 3 | 2026-07-19 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-20 | ETD9XU | MAN → AUH | Jul 20, 08:25 UTC | Jul 20, 16:00 UTC | 7h 35m |
| 2026-07-19 | ETD49D | - | Jul 19, 22:35 UTC | Jul 20, 06:00 UTC | 7h 25m |
| 2026-07-19 | ETD49D | AUH → AUH | Jul 19, 22:25 UTC | Jul 19, 22:30 UTC | 5m |
| 2026-07-19 | ETD477 | DPS → AUH | Jul 19, 01:50 UTC | Jul 19, 19:15 UTC | 17h 25m |
| 2026-07-18 | ETD477 | DPS → AUH | Jul 18, 21:50 UTC | Jul 19, 19:15 UTC | 21h 25m |
| 2026-07-18 | ETD476 | - | Jul 18, 19:50 UTC | Jul 19, 19:15 UTC | 23h 25m |
| 2026-07-18 | ETD476 | - | Jul 18, 19:25 UTC | Jul 19, 17:30 UTC | 22h 5m |
| 2026-07-17 | ETD841 | AUH → SVO | Jul 17, 23:39 UTC | Jul 18, 15:35 UTC | 15h 56m |
| 2026-07-17 | ETD477 | DPS → AUH | Jul 17, 01:15 UTC | Jul 17, 17:30 UTC | 16h 15m |
| 2026-07-16 | ETD477 | DPS → AUH | Jul 16, 20:55 UTC | Jul 17, 17:30 UTC | 20h 35m |
| 2026-07-16 | ETD476 | - | Jul 16, 19:05 UTC | Jul 17, 17:30 UTC | 22h 25m |
| 2026-07-16 | ETD841 | - | Jul 16, 00:05 UTC | Jul 16, 15:25 UTC | 15h 20m |
| 2026-07-15 | ETD217 | - | Jul 15, 16:10 UTC | Jul 15, 19:00 UTC | 2h 50m |
| 2026-07-15 | ETD216 | - | Jul 15, 11:10 UTC | Jul 15, 14:15 UTC | 3h 5m |
| 2026-07-14 | ETD479 | - | Jul 14, 08:05 UTC | Jul 15, 01:55 UTC | 17h 49m |
| 2026-07-14 | ETD478 | - | Jul 14, 06:20 UTC | Jul 14, 06:40 UTC | 20m |
| 2026-07-14 | ETD479 | - | Jul 14, 01:40 UTC | Jul 14, 01:50 UTC | 10m |
| 2026-07-13 | ETD478 | - | Jul 13, 06:20 UTC | Jul 14, 00:05 UTC | 17h 45m |
| 2026-07-12 | ETD479 | - | Jul 12, 08:05 UTC | Jul 13, 02:05 UTC | 18h 0m |
| 2026-07-12 | ETD479 | - | Jul 12, 06:25 UTC | Jul 13, 02:05 UTC | 19h 40m |
| 2026-07-11 | ETD844 | - | Jul 11, 20:00 UTC | Jul 11, 21:25 UTC | 1h 25m |
| 2026-07-11 | ETD843 | - | Jul 11, 10:30 UTC | Jul 11, 12:30 UTC | 2h 0m |
| 2026-07-10 | ETD843 | - | Jul 10, 13:15 UTC | Jul 11, 10:55 UTC | 21h 40m |
| 2026-07-10 | ETD843 | - | Jul 10, 11:10 UTC | Jul 10, 13:50 UTC | 2h 40m |
| 2026-07-09 | ETD447 | - | Jul 9, 22:30 UTC | Jul 10, 06:20 UTC | 7h 50m |
| 2026-07-09 | ETD446 | - | Jul 9, 05:40 UTC | Jul 9, 13:50 UTC | 8h 10m |
| 2026-07-07 | ETD479 | - | Jul 7, 19:50 UTC | Jul 8, 14:15 UTC | 18h 25m |
| 2026-07-07 | ETD479 | - | Jul 7, 19:25 UTC | Jul 8, 14:15 UTC | 18h 50m |
| 2026-07-07 | ETD479 | - | Jul 7, 12:15 UTC | Jul 8, 11:45 UTC | 23h 30m |
| 2026-07-07 | ETD478 | - | Jul 7, 06:35 UTC | Jul 8, 00:00 UTC | 17h 25m |
| 2026-07-06 | ETD843 | AUH → SVO | Jul 6, 10:45 UTC | Jul 6, 11:15 UTC | 30m |
| 2026-07-05 | ETD479 | - | Jul 5, 08:10 UTC | Jul 6, 02:05 UTC | 17h 55m |
| 2026-07-05 | ETD479 | - | Jul 5, 06:30 UTC | Jul 6, 02:05 UTC | 19h 35m |
| 2026-07-04 | ETD843 | AUH → SVO | Jul 4, 10:35 UTC | Jul 4, 13:35 UTC | 3h 0m |
| 2026-07-03 | ETD844 | - | Jul 3, 11:30 UTC | Jul 4, 03:05 UTC | 15h 35m |
| 2026-07-02 | ETD410 | AUH → HKT | Jul 2, 18:15 UTC | Jul 3, 07:45 UTC | 13h 30m |
| 2026-07-02 | ETD405 | - | Jul 2, 09:20 UTC | Jul 2, 15:00 UTC | 5h 40m |
| 2026-07-01 | ETD404 | AUH → BKK | Jul 1, 23:25 UTC | Jul 2, 05:25 UTC | 6h 0m |
| 2026-07-01 | ETD431 | HAN → AUH | Jul 1, 14:30 UTC | Jul 1, 20:35 UTC | 6h 5m |
| 2026-06-30 | ETD432 | - | Jun 30, 19:05 UTC | Jul 1, 01:20 UTC | 6h 15m |
| 2026-06-30 | ETD9XU | MAN → AUH | Jun 30, 08:40 UTC | Jun 30, 15:35 UTC | 6h 55m |
| 2026-06-29 | ETD49D | AUH → MAN | Jun 29, 22:24 UTC | Jun 30, 05:10 UTC | 6h 45m |
| 2026-06-29 | ETD217 | - | Jun 29, 16:15 UTC | Jun 29, 19:05 UTC | 2h 50m |
| 2026-06-29 | ETD216 | - | Jun 29, 10:44 UTC | Jun 29, 13:49 UTC | 3h 5m |
| 2026-06-28 | ETD447 | MNL → AUH | Jun 28, 22:15 UTC | Jun 29, 06:09 UTC | 7h 55m |
| 2026-06-28 | ETD446 | - | Jun 28, 05:49 UTC | Jun 28, 14:25 UTC | 8h 35m |
| 2026-06-27 | ETD431 | HAN → AUH | Jun 27, 14:14 UTC | Jun 27, 20:04 UTC | 5h 50m |
| 2026-06-26 | ETD432 | - | Jun 26, 18:49 UTC | Jun 27, 00:14 UTC | 5h 25m |
| 2026-06-26 | ETD1QN | - | Jun 26, 10:10 UTC | Jun 26, 12:44 UTC | 2h 35m |
| 2026-06-25 | ETD3BU | - | Jun 25, 23:05 UTC | Jun 26, 04:24 UTC | 5h 20m |
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-ETJ page for operator, model, and routing details .