sensors Mode-S transponder
8965F5
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-BNG · BOEING 787-9 Dreamliner
- Hex
- 8965F5
- Octal
- 42262765
- Decimal
- 9,004,533
- Country
- AE
- Tail
- A6-BNG
- Type
- B789
- Flights observed
- 200
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- Jul 25, 03:00 UTC
Last known position
Country allocation
The ICAO 24-bit address 8965F5 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 |
|---|---|---|---|
| ETD3MB | Etihad Airways | 17 | 2026-06-13 |
| ETD47B | Etihad Airways | 13 | 2026-07-23 |
| ETD6PX | - | 10 | 2026-06-13 |
| ETD53M | Etihad Airways | 10 | 2026-05-01 |
| ETD2NL | Etihad Airways | 10 | 2026-07-22 |
| ETD13 | Etihad Airways | 10 | 2026-06-03 |
| ETD16 | Etihad Airways | 9 | 2026-07-23 |
| ETD91N | Etihad Airways | 8 | 2026-07-21 |
| ETD99P | Etihad Airways | 7 | 2026-06-06 |
| ETD67B | - | 7 | 2026-07-24 |
| ETD93C | Etihad Airways | 6 | 2026-07-20 |
| ETD6HZ | Etihad Airways | 6 | 2026-05-01 |
| ETD128 | Etihad Airways | 6 | 2026-07-24 |
| ETD125 | Etihad Airways | 6 | 2026-06-05 |
| ETD76T | Etihad Airways | 5 | 2026-07-21 |
| ETD123 | Etihad Airways | 5 | 2026-07-01 |
| ETD9SM | Etihad Airways | 4 | 2026-06-04 |
| ETD870 | Etihad Airways | 4 | 2026-06-02 |
| ETD79 | Etihad Airways | 4 | 2026-05-07 |
| ETD18MA | - | 4 | 2026-04-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-24 | ETD128 | MUC → AUH | Jul 24, 20:40 UTC | Jul 25, 03:00 UTC | 6h 20m |
| 2026-07-24 | ETD67B | - | Jul 24, 10:45 UTC | Jul 24, 16:55 UTC | 6h 10m |
| 2026-07-23 | ETD16 | MAN → AUH | Jul 23, 19:25 UTC | Jul 24, 07:50 UTC | 12h 25m |
| 2026-07-23 | ETD47B | AUH → CLT | Jul 23, 00:20 UTC | Jul 23, 14:45 UTC | 14h 25m |
| 2026-07-22 | ETD2NL | MEL → AUH | Jul 22, 11:10 UTC | Jul 22, 21:05 UTC | 9h 55m |
| 2026-07-21 | ETD91N | AUH → MEL | Jul 21, 17:10 UTC | Jul 22, 05:25 UTC | 12h 15m |
| 2026-07-21 | ETD76T | ORD → AUH | Jul 21, 07:25 UTC | Jul 21, 08:20 UTC | 55m |
| 2026-07-20 | ETD76T | ORD → AUH | Jul 20, 19:20 UTC | Jul 21, 06:15 UTC | 10h 54m |
| 2026-07-20 | ETD93C | AUH → ORD | Jul 20, 00:55 UTC | Jul 20, 14:50 UTC | 13h 55m |
| 2026-07-19 | ETD562 | DAM → AUH | Jul 19, 16:05 UTC | Jul 19, 18:40 UTC | 2h 35m |
| 2026-07-18 | ETD76T | ORD → AUH | Jul 18, 19:25 UTC | Jul 19, 12:55 UTC | 17h 30m |
| 2026-07-18 | ETD93C | AUH → ORD | Jul 18, 02:29 UTC | Jul 18, 14:25 UTC | 11h 56m |
| 2026-07-17 | ETD93C | AUH → ORD | Jul 17, 17:35 UTC | Jul 18, 14:25 UTC | 20h 51m |
| 2026-07-17 | ETD93C | AUH → ORD | Jul 17, 08:00 UTC | Jul 18, 07:15 UTC | 23h 16m |
| 2026-07-16 | ETD91N | - | Jul 16, 17:25 UTC | Jul 17, 06:00 UTC | 12h 35m |
| 2026-07-16 | ETD7EE | - | Jul 16, 02:00 UTC | Jul 16, 15:14 UTC | 13h 15m |
| 2026-07-15 | ETD4RL | - | Jul 15, 06:35 UTC | Jul 15, 20:40 UTC | 14h 5m |
| 2026-07-14 | ETD11Y | - | Jul 14, 23:10 UTC | Jul 15, 03:15 UTC | 4h 5m |
| 2026-07-14 | ETD11Y | - | Jul 14, 21:30 UTC | Jul 14, 23:05 UTC | 1h 34m |
| 2026-07-14 | ETD6XY | - | Jul 14, 11:00 UTC | Jul 14, 16:40 UTC | 5h 40m |
| 2026-07-13 | ETD16 | - | Jul 13, 19:40 UTC | Jul 14, 08:55 UTC | 13h 15m |
| 2026-07-13 | ETD47B | - | Jul 13, 00:35 UTC | Jul 13, 14:20 UTC | 13h 45m |
| 2026-07-11 | ETD16 | - | Jul 11, 19:30 UTC | Jul 12, 08:35 UTC | 13h 5m |
| 2026-07-11 | ETD47B | - | Jul 11, 00:00 UTC | Jul 11, 14:15 UTC | 14h 15m |
| 2026-07-10 | ETD2NL | - | Jul 10, 08:30 UTC | Jul 10, 21:20 UTC | 12h 50m |
| 2026-07-09 | ETD91N | - | Jul 9, 17:45 UTC | Jul 10, 06:20 UTC | 12h 35m |
| 2026-07-09 | ETD1QN | - | Jul 9, 10:10 UTC | Jul 9, 15:25 UTC | 5h 15m |
| 2026-07-08 | ETD3BU | AUH → VIE | Jul 8, 23:20 UTC | Jul 9, 04:35 UTC | 5h 15m |
| 2026-07-07 | ETD16 | - | Jul 7, 19:50 UTC | Jul 8, 08:40 UTC | 12h 50m |
| 2026-07-07 | ETD47B | - | Jul 7, 00:20 UTC | Jul 7, 14:30 UTC | 14h 10m |
| 2026-07-06 | ETD2NL | - | Jul 6, 20:35 UTC | Jul 6, 20:55 UTC | 20m |
| 2026-07-06 | ETD2NL | - | Jul 6, 08:05 UTC | Jul 6, 17:50 UTC | 9h 45m |
| 2026-07-05 | ETD91N | - | Jul 5, 17:35 UTC | Jul 6, 06:00 UTC | 12h 25m |
| 2026-07-04 | ETD16 | - | Jul 4, 19:55 UTC | Jul 5, 08:30 UTC | 12h 35m |
| 2026-07-04 | ETD47B | - | Jul 4, 00:05 UTC | Jul 4, 14:10 UTC | 14h 5m |
| 2026-07-03 | ETD012 | - | Jul 3, 03:05 UTC | Jul 3, 15:40 UTC | 12h 35m |
| 2026-07-02 | ETD011 | - | Jul 2, 06:35 UTC | Jul 2, 20:25 UTC | 13h 50m |
| 2026-07-01 | ETD18M | - | Jul 1, 20:15 UTC | Jul 2, 02:05 UTC | 5h 50m |
| 2026-07-01 | ETD123 | AUH → FRA | Jul 1, 10:40 UTC | Jul 1, 16:45 UTC | 6h 5m |
| 2026-06-30 | ETD76T | - | Jun 30, 19:20 UTC | Jul 1, 08:25 UTC | 13h 5m |
| 2026-06-29 | ETD93C | AUH → ORD | Jun 29, 23:54 UTC | Jun 30, 13:50 UTC | 13h 56m |
| 2026-06-29 | ETD012 | ORD → AUH | Jun 29, 01:50 UTC | Jun 29, 14:50 UTC | 13h 0m |
| 2026-06-28 | ETD011 | - | Jun 28, 06:24 UTC | Jun 28, 20:04 UTC | 13h 40m |
| 2026-06-27 | ETD11Y | - | Jun 27, 21:40 UTC | Jun 28, 02:54 UTC | 5h 15m |
| 2026-06-27 | ETD6XY | - | Jun 27, 10:34 UTC | Jun 27, 16:00 UTC | 5h 25m |
| 2026-06-26 | ETD76T | - | Jun 26, 19:30 UTC | Jun 27, 08:20 UTC | 12h 50m |
| 2026-06-25 | ETD93C | - | Jun 25, 23:24 UTC | Jun 26, 13:30 UTC | 14h 5m |
| 2026-06-25 | ETD35Q | - | Jun 25, 09:10 UTC | Jun 25, 15:20 UTC | 6h 10m |
| 2026-06-24 | ETD3P1 | - | Jun 24, 23:10 UTC | Jun 25, 05:20 UTC | 6h 10m |
| 2026-06-24 | ETD412 | - | Jun 24, 05:15 UTC | Jun 24, 18:34 UTC | 13h 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-BNG page for operator, model, and routing details .