sensors Mode-S transponder
896354
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-ETQ · BOEING 777-300ER
- Hex
- 896354
- Octal
- 42261524
- Decimal
- 9,003,860
- Country
- AE
- Tail
- A6-ETQ
- Type
- B77W
- Flights observed
- 192
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 896354 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 | - | 15 | 2026-07-12 |
| ETD440 | - | 13 | 2026-06-14 |
| ETD447 | - | 12 | 2026-07-12 |
| ETD406 | Etihad Airways | 12 | 2026-05-10 |
| ETD402 | Etihad Airways | 10 | 2026-04-30 |
| ETD403 | Etihad Airways | 9 | 2026-05-09 |
| ETD72W | Etihad Airways | 8 | 2026-05-11 |
| ETD430 | Etihad Airways | 8 | 2026-06-06 |
| ETD407 | Etihad Airways | 8 | 2026-05-04 |
| ETD5FA | Etihad Airways | 7 | 2026-04-28 |
| ETD441 | Etihad Airways | 7 | 2026-06-05 |
| ETD431 | Etihad Airways | 7 | 2026-06-24 |
| ETD49D | Etihad Airways | 6 | 2026-06-27 |
| ETD479 | - | 6 | 2026-07-11 |
| ETD9XU | - | 5 | 2026-06-28 |
| ETD432 | - | 5 | 2026-06-23 |
| ETD26N | - | 5 | 2026-06-13 |
| ETD36V | Etihad Airways | 4 | 2026-06-14 |
| ETD217 | - | 3 | 2026-07-08 |
| ETD216 | - | 3 | 2026-07-08 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-12 | ETD447 | - | Jul 12, 22:40 UTC | Jul 13, 06:25 UTC | 7h 45m |
| 2026-07-12 | ETD446 | - | Jul 12, 07:20 UTC | Jul 12, 14:30 UTC | 7h 10m |
| 2026-07-12 | ETD446 | - | Jul 12, 06:05 UTC | Jul 12, 06:15 UTC | 10m |
| 2026-07-11 | ETD479 | - | Jul 11, 08:20 UTC | Jul 12, 02:05 UTC | 17h 45m |
| 2026-07-11 | ETD479 | - | Jul 11, 06:30 UTC | Jul 12, 02:05 UTC | 19h 35m |
| 2026-07-10 | ETD479 | - | Jul 10, 08:05 UTC | Jul 11, 02:00 UTC | 17h 55m |
| 2026-07-10 | ETD479 | - | Jul 10, 06:35 UTC | Jul 11, 02:00 UTC | 19h 25m |
| 2026-07-09 | ETD205 | BOM → AUH | Jul 9, 17:55 UTC | Jul 9, 20:15 UTC | 2h 20m |
| 2026-07-09 | ETD204 | - | Jul 9, 11:05 UTC | Jul 9, 13:25 UTC | 2h 20m |
| 2026-07-08 | ETD217 | - | Jul 8, 18:25 UTC | Jul 8, 18:50 UTC | 25m |
| 2026-07-08 | ETD217 | - | Jul 8, 16:05 UTC | Jul 8, 16:35 UTC | 30m |
| 2026-07-08 | ETD216 | - | Jul 8, 11:05 UTC | Jul 8, 13:55 UTC | 2h 50m |
| 2026-07-07 | ETD447 | MNL → AUH | Jul 7, 22:35 UTC | Jul 8, 06:25 UTC | 7h 50m |
| 2026-07-07 | ETD446 | - | Jul 7, 05:45 UTC | Jul 7, 14:10 UTC | 8h 25m |
| 2026-07-06 | ETD479 | - | Jul 6, 08:05 UTC | Jul 7, 02:00 UTC | 17h 55m |
| 2026-07-06 | ETD478 | - | Jul 6, 06:25 UTC | Jul 6, 06:35 UTC | 10m |
| 2026-07-06 | ETD4XQ | - | Jul 6, 00:05 UTC | Jul 6, 02:30 UTC | 2h 25m |
| 2026-07-05 | ETD206 | - | Jul 5, 19:40 UTC | Jul 5, 20:30 UTC | 50m |
| 2026-07-04 | ETD447 | MNL → AUH | Jul 4, 22:25 UTC | Jul 5, 06:25 UTC | 8h 0m |
| 2026-07-04 | ETD446 | - | Jul 4, 09:15 UTC | Jul 4, 17:20 UTC | 8h 5m |
| 2026-07-03 | ETD447 | MNL → AUH | Jul 3, 22:00 UTC | Jul 4, 05:55 UTC | 7h 55m |
| 2026-07-03 | ETD446 | - | Jul 3, 05:45 UTC | Jul 3, 11:05 UTC | 5h 20m |
| 2026-07-02 | ETD479 | - | Jul 2, 08:10 UTC | Jul 3, 02:00 UTC | 17h 50m |
| 2026-07-02 | ETD478 | - | Jul 2, 06:35 UTC | Jul 3, 02:00 UTC | 19h 25m |
| 2026-07-01 | ETD217 | - | Jul 1, 16:15 UTC | Jul 1, 19:00 UTC | 2h 45m |
| 2026-07-01 | ETD216 | - | Jul 1, 10:30 UTC | Jul 1, 13:25 UTC | 2h 55m |
| 2026-06-30 | ETD447 | MNL → AUH | Jun 30, 22:40 UTC | Jul 1, 06:30 UTC | 7h 50m |
| 2026-06-30 | ETD446 | - | Jun 30, 05:25 UTC | Jun 30, 14:05 UTC | 8h 40m |
| 2026-06-29 | ETD401 | - | Jun 29, 20:19 UTC | Jun 29, 21:24 UTC | 1h 5m |
| 2026-06-29 | ETD400 | - | Jun 29, 10:59 UTC | Jun 29, 17:14 UTC | 6h 15m |
| 2026-06-29 | ETD4XQ | - | Jun 29, 00:05 UTC | Jun 29, 02:30 UTC | 2h 25m |
| 2026-06-28 | ETD206 | - | Jun 28, 18:29 UTC | Jun 28, 21:10 UTC | 2h 40m |
| 2026-06-28 | ETD9XU | - | Jun 28, 08:59 UTC | Jun 28, 15:55 UTC | 6h 55m |
| 2026-06-27 | ETD49D | AUH → MAN | Jun 27, 22:55 UTC | Jun 28, 05:49 UTC | 6h 55m |
| 2026-06-27 | ETD477 | DPS → AUH | Jun 27, 01:35 UTC | Jun 27, 19:19 UTC | 17h 45m |
| 2026-06-26 | ETD477 | DPS → AUH | Jun 26, 21:20 UTC | Jun 27, 19:19 UTC | 22h 0m |
| 2026-06-26 | ETD476 | - | Jun 26, 19:30 UTC | Jun 27, 19:00 UTC | 23h 30m |
| 2026-06-26 | ETD9XU | - | Jun 26, 09:05 UTC | Jun 26, 15:54 UTC | 6h 50m |
| 2026-06-25 | ETD49D | AUH → MAN | Jun 25, 23:30 UTC | Jun 26, 06:19 UTC | 6h 50m |
| 2026-06-25 | ETD413 | HKT → AUH | Jun 25, 19:39 UTC | Jun 25, 20:09 UTC | 30m |
| 2026-06-25 | ETD412 | - | Jun 25, 04:49 UTC | Jun 25, 18:19 UTC | 13h 30m |
| 2026-06-24 | ETD431 | HAN → AUH | Jun 24, 14:15 UTC | Jun 24, 18:39 UTC | 4h 25m |
| 2026-06-23 | ETD432 | - | Jun 23, 19:19 UTC | Jun 23, 23:14 UTC | 3h 55m |
| 2026-06-23 | ETD432 | - | Jun 23, 17:54 UTC | Jun 23, 18:10 UTC | 15m |
| 2026-06-23 | ETD1QN | - | Jun 23, 10:15 UTC | Jun 23, 15:24 UTC | 5h 10m |
| 2026-06-22 | ETD3BU | AYM → VIE | Jun 22, 22:54 UTC | Jun 23, 04:09 UTC | 5h 15m |
| 2026-06-22 | ETD431 | HAN → AUH | Jun 22, 14:10 UTC | Jun 22, 20:00 UTC | 5h 50m |
| 2026-06-21 | ETD432 | - | Jun 21, 19:20 UTC | Jun 21, 22:29 UTC | 3h 10m |
| 2026-06-21 | ETD1QN | - | Jun 21, 10:04 UTC | Jun 21, 15:15 UTC | 5h 10m |
| 2026-06-21 | ETD3BU | - | Jun 21, 01:05 UTC | Jun 21, 04:14 UTC | 3h 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-ETQ page for operator, model, and routing details .