sensors Mode-S transponder
8965F4
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-BNF · BOEING 787-9 Dreamliner
- Hex
- 8965F4
- Octal
- 42262764
- Decimal
- 9,004,532
- Country
- AE
- Tail
- A6-BNF
- Type
- B789
- Flights observed
- 172
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 52m ago
Last known position
Country allocation
The ICAO 24-bit address 8965F4 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 | 15 | 2026-06-09 |
| ETD9SM | - | 8 | 2026-06-13 |
| ETD91N | - | 8 | 2026-07-13 |
| ETD801 | Etihad Airways | 8 | 2026-05-01 |
| ETD800 | Etihad Airways | 8 | 2026-04-30 |
| ETD6PX | Etihad Airways | 8 | 2026-06-09 |
| ETD47B | - | 8 | 2026-07-10 |
| ETD93C | - | 7 | 2026-07-12 |
| ETD871 | Etihad Airways | 6 | 2026-05-19 |
| ETD76T | - | 6 | 2026-07-12 |
| ETD2NL | - | 6 | 2026-07-03 |
| ETD16 | - | 6 | 2026-07-10 |
| ETD13 | - | 6 | 2026-06-12 |
| ETD125 | Etihad Airways | 6 | 2026-06-04 |
| ETD99P | Etihad Airways | 5 | 2026-06-04 |
| ETD44 | Etihad Airways | 5 | 2026-06-14 |
| ETD36V | Etihad Airways | 5 | 2026-04-30 |
| ETD26N | Etihad Airways | 5 | 2026-04-29 |
| ETD870 | Etihad Airways | 4 | 2026-06-04 |
| ETD67B | - | 4 | 2026-06-24 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | ETD91N | AUH → MEL | Jul 13, 17:40 UTC | Jul 14, 06:15 UTC | 12h 35m |
| 2026-07-12 | ETD76T | - | Jul 12, 19:40 UTC | Jul 13, 09:05 UTC | 13h 25m |
| 2026-07-12 | ETD93C | - | Jul 12, 01:05 UTC | Jul 12, 14:35 UTC | 13h 30m |
| 2026-07-10 | ETD16 | - | Jul 10, 21:05 UTC | Jul 11, 09:55 UTC | 12h 50m |
| 2026-07-10 | ETD47B | - | Jul 10, 01:15 UTC | Jul 10, 15:35 UTC | 14h 20m |
| 2026-07-09 | ETD7EE | - | Jul 9, 02:10 UTC | Jul 9, 14:50 UTC | 12h 40m |
| 2026-07-08 | ETD4RL | - | Jul 8, 06:25 UTC | Jul 8, 20:25 UTC | 14h 0m |
| 2026-07-08 | ETD11Y | - | Jul 8, 00:20 UTC | Jul 8, 02:30 UTC | 2h 10m |
| 2026-07-07 | ETD11Y | - | Jul 7, 21:20 UTC | Jul 8, 00:15 UTC | 2h 55m |
| 2026-07-07 | ETD6XY | - | Jul 7, 11:45 UTC | Jul 7, 16:55 UTC | 5h 10m |
| 2026-07-06 | ETD76T | - | Jul 6, 20:40 UTC | Jul 7, 09:30 UTC | 12h 50m |
| 2026-07-05 | ETD93C | - | Jul 5, 23:55 UTC | Jul 6, 13:50 UTC | 13h 55m |
| 2026-07-05 | ETD358 | - | Jul 5, 11:40 UTC | Jul 5, 19:35 UTC | 7h 55m |
| 2026-07-04 | ETD76T | - | Jul 4, 20:40 UTC | Jul 5, 09:05 UTC | 12h 25m |
| 2026-07-04 | ETD93C | - | Jul 4, 00:00 UTC | Jul 4, 13:45 UTC | 13h 45m |
| 2026-07-03 | ETD2NL | - | Jul 3, 08:00 UTC | Jul 3, 21:10 UTC | 13h 10m |
| 2026-07-02 | ETD91N | - | Jul 2, 17:30 UTC | Jul 3, 05:55 UTC | 12h 25m |
| 2026-07-01 | ETD76T | - | Jul 1, 19:30 UTC | Jul 2, 08:15 UTC | 12h 45m |
| 2026-07-01 | ETD93C | - | Jul 1, 01:40 UTC | Jul 1, 13:30 UTC | 11h 50m |
| 2026-06-30 | ETD93C | - | Jun 30, 23:35 UTC | Jul 1, 01:35 UTC | 2h 0m |
| 2026-06-30 | ETD2NL | MEL → AUH | Jun 30, 07:40 UTC | Jun 30, 21:00 UTC | 13h 20m |
| 2026-06-29 | ETD91N | - | Jun 29, 17:10 UTC | Jun 30, 05:40 UTC | 12h 31m |
| 2026-06-28 | ETD16 | - | Jun 28, 20:50 UTC | Jun 29, 08:54 UTC | 12h 5m |
| 2026-06-28 | ETD16 | - | Jun 28, 20:04 UTC | Jun 28, 20:45 UTC | 40m |
| 2026-06-28 | ETD47B | - | Jun 28, 00:00 UTC | Jun 28, 14:09 UTC | 14h 10m |
| 2026-06-27 | ETD359 | HYD → AUH | Jun 27, 10:34 UTC | Jun 27, 19:15 UTC | 8h 40m |
| 2026-06-26 | ETD16 | - | Jun 26, 19:24 UTC | Jun 27, 08:14 UTC | 12h 50m |
| 2026-06-25 | ETD47B | - | Jun 25, 23:59 UTC | Jun 26, 14:15 UTC | 14h 15m |
| 2026-06-25 | ETD4EH | - | Jun 25, 20:14 UTC | Jun 25, 20:49 UTC | 35m |
| 2026-06-25 | ETD8PF | - | Jun 25, 17:25 UTC | Jun 25, 17:49 UTC | 25m |
| 2026-06-24 | ETD128 | - | Jun 24, 20:44 UTC | Jun 25, 02:05 UTC | 5h 20m |
| 2026-06-24 | ETD67B | - | Jun 24, 11:05 UTC | Jun 24, 16:59 UTC | 5h 55m |
| 2026-06-23 | ETD16 | - | Jun 23, 19:50 UTC | Jun 24, 08:30 UTC | 12h 40m |
| 2026-06-22 | ETD47B | - | Jun 22, 23:50 UTC | Jun 23, 14:29 UTC | 14h 40m |
| 2026-06-22 | ETD4EH | - | Jun 22, 20:19 UTC | Jun 22, 20:39 UTC | 20m |
| 2026-06-22 | ETD8PF | - | Jun 22, 17:25 UTC | Jun 22, 17:44 UTC | 20m |
| 2026-06-22 | ETD7BR | FRA → AUH | Jun 22, 09:19 UTC | Jun 22, 15:14 UTC | 5h 55m |
| 2026-06-21 | ETD4AJ | - | Jun 21, 22:34 UTC | Jun 22, 04:24 UTC | 5h 50m |
| 2026-06-21 | ETD2MJ | - | Jun 21, 16:49 UTC | Jun 21, 19:50 UTC | 3h 0m |
| 2026-06-21 | ETD238 | - | Jun 21, 10:34 UTC | Jun 21, 13:59 UTC | 3h 25m |
| 2026-06-20 | ETD76T | - | Jun 20, 19:34 UTC | Jun 21, 08:40 UTC | 13h 5m |
| 2026-06-19 | ETD93C | - | Jun 19, 23:25 UTC | Jun 20, 13:09 UTC | 13h 45m |
| 2026-06-18 | ETD76T | - | Jun 18, 19:40 UTC | Jun 19, 08:29 UTC | 12h 49m |
| 2026-06-18 | ETD93C | - | Jun 18, 01:25 UTC | Jun 18, 13:30 UTC | 12h 5m |
| 2026-06-17 | ETD012 | - | Jun 17, 01:50 UTC | Jun 17, 14:30 UTC | 12h 40m |
| 2026-06-16 | ETD011 | - | Jun 16, 07:15 UTC | Jun 16, 20:50 UTC | 13h 36m |
| 2026-06-15 | ETD88C | - | Jun 15, 20:04 UTC | Jun 16, 02:00 UTC | 5h 55m |
| 2026-06-15 | ETD69W | AUH → LHR | Jun 15, 00:29 UTC | Jun 15, 14:00 UTC | 13h 30m |
| 2026-06-14 | ETD44 | AMS → AUH | Jun 14, 09:05 UTC | Jun 14, 14:45 UTC | 5h 40m |
| 2026-06-13 | ETD43 | - | Jun 13, 23:35 UTC | Jun 14, 05:45 UTC | 6h 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-BNF page for operator, model, and routing details .