sensors Mode-S transponder
8965D0
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-FKE · BOEING 737 MAX 8
- Hex
- 8965D0
- Octal
- 42262720
- Decimal
- 9,004,496
- Country
- AE
- Tail
- A6-FKE
- Type
- B38M
- Flights observed
- 52
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 18h ago
Last known position
Country allocation
The ICAO 24-bit address 8965D0 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 |
|---|---|---|---|
| FDB870 | Fly Dubai | 3 | 2026-05-23 |
| FDB864 | Fly Dubai | 2 | 2026-05-29 |
| FDB808 | Fly Dubai | 2 | 2026-05-20 |
| FDB7KL | Fly Dubai | 2 | 2026-05-25 |
| FDB64X | - | 2 | 2026-05-07 |
| FDB5WB | Fly Dubai | 2 | 2026-04-25 |
| FDB5JA | Fly Dubai | 2 | 2026-04-25 |
| FDB4JZ | Fly Dubai | 2 | 2026-04-23 |
| FDB16T | Fly Dubai | 2 | 2026-04-16 |
| FDB9RQ | Fly Dubai | 1 | 2026-05-29 |
| FDB948 | Fly Dubai | 1 | 2026-05-19 |
| FDB919 | Fly Dubai | 1 | 2026-04-13 |
| FDB905 | Fly Dubai | 1 | 2026-04-27 |
| FDB884 | Fly Dubai | 1 | 2026-05-27 |
| FDB882 | Fly Dubai | 1 | 2026-05-25 |
| FDB875 | Fly Dubai | 1 | 2026-05-05 |
| FDB869 | Fly Dubai | 1 | 2026-05-01 |
| FDB863 | Fly Dubai | 1 | 2026-05-04 |
| FDB832 | Fly Dubai | 1 | 2026-05-05 |
| FDB810 | Fly Dubai | 1 | 2026-04-30 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | FDB864 | DMM → DXB | May 29, 12:40 UTC | May 29, 13:35 UTC | 55m |
| 2026-05-29 | FDB9RQ | DOH → DXB | May 29, 07:10 UTC | May 29, 07:55 UTC | 45m |
| 2026-05-27 | FDB646 | ASM → DXB | May 27, 21:50 UTC | May 27, 22:35 UTC | 45m |
| 2026-05-27 | FDB884 | DMM → DXB | May 27, 05:35 UTC | May 27, 06:29 UTC | 55m |
| 2026-05-25 | FDB882 | TUU → DXB | May 25, 22:05 UTC | May 26, 17:39 UTC | 19h 35m |
| 2026-05-25 | FDB7KL | AMM → DXB | May 25, 21:24 UTC | May 26, 17:39 UTC | 20h 15m |
| 2026-05-25 | FDB7KL | AMM → DXB | May 25, 19:50 UTC | May 25, 19:59 UTC | 10m |
| 2026-05-25 | FDB143 | DXB → AMM | May 25, 18:10 UTC | May 25, 18:30 UTC | 20m |
| 2026-05-24 | FDB3CK | AMM → DXB | May 24, 07:20 UTC | May 24, 09:45 UTC | 2h 25m |
| 2026-05-23 | FDB184 | HBE → DXB | May 23, 17:55 UTC | May 23, 21:05 UTC | 3h 10m |
| 2026-05-23 | FDB183 | DXB → HBE | May 23, 15:55 UTC | May 23, 16:50 UTC | 55m |
| 2026-05-23 | FDB870 | DMM → DXB | May 23, 10:15 UTC | May 23, 11:15 UTC | 1h 0m |
| 2026-05-22 | FDB4DT | DXB → SKT | May 22, 23:00 UTC | May 23, 01:30 UTC | 2h 30m |
| 2026-05-20 | FDB808 | JED → DXB | May 20, 21:15 UTC | May 20, 21:45 UTC | 30m |
| 2026-05-19 | FDB948 | AQI → DXB | May 19, 08:10 UTC | May 19, 11:45 UTC | 3h 35m |
| 2026-05-17 | FDB870 | DMM → DXB | May 17, 10:05 UTC | May 17, 11:01 UTC | 55m |
| 2026-05-16 | FDB176 | HBE → DXB | May 16, 21:05 UTC | May 17, 00:05 UTC | 3h 0m |
| 2026-05-16 | FDB175 | DXB → HBE | May 16, 16:31 UTC | May 16, 19:35 UTC | 3h 5m |
| 2026-05-15 | FDB808 | JED → DXB | May 15, 21:20 UTC | May 16, 16:45 UTC | 19h 26m |
| 2026-05-09 | - | - | May 9, 10:05 UTC | May 9, 12:50 UTC | 2h 45m |
| 2026-05-07 | FDB64X | - | May 7, 13:20 UTC | May 7, 14:05 UTC | 45m |
| 2026-05-05 | FDB875 | DXB → TIF | May 5, 12:00 UTC | May 5, 16:20 UTC | 4h 20m |
| 2026-05-05 | FDB832 | JED → DXB | May 5, 05:45 UTC | May 5, 07:00 UTC | 1h 15m |
| 2026-05-04 | FDB864 | DMM → DXB | May 4, 12:35 UTC | May 4, 13:25 UTC | 50m |
| 2026-05-04 | FDB863 | DXB → DMM | May 4, 10:20 UTC | May 4, 11:10 UTC | 50m |
| 2026-05-03 | FDB3JE | MRV → DXB | May 3, 16:40 UTC | May 3, 21:10 UTC | 4h 30m |
| 2026-05-02 | FDB5PG | DXB → MRV | May 2, 17:55 UTC | May 2, 18:15 UTC | 20m |
| 2026-05-01 | FDB606 | ADD → DXB | May 1, 21:35 UTC | May 2, 07:30 UTC | 9h 55m |
| 2026-05-01 | FDB870 | DMM → DXB | May 1, 10:10 UTC | May 1, 11:00 UTC | 50m |
| 2026-05-01 | FDB869 | DXB → DMM | May 1, 07:40 UTC | May 1, 08:30 UTC | 50m |
| 2026-04-30 | FDB810 | HOF → DXB | Apr 30, 13:05 UTC | Apr 30, 14:20 UTC | 1h 15m |
| 2026-04-30 | FDB809 | DXB → HOF | Apr 30, 09:20 UTC | Apr 30, 10:25 UTC | 1h 5m |
| 2026-04-29 | FDB64X | - | Apr 29, 09:30 UTC | Apr 29, 10:30 UTC | 1h 0m |
| 2026-04-29 | FDB1AR | - | Apr 29, 07:15 UTC | Apr 29, 07:59 UTC | 45m |
| 2026-04-27 | FDB905 | DXB → ULH | Apr 27, 15:55 UTC | Apr 27, 22:10 UTC | 6h 15m |
| 2026-04-25 | FDB5WB | BEY → DXB | Apr 25, 12:20 UTC | Apr 25, 15:10 UTC | 2h 50m |
| 2026-04-25 | FDB5JA | DXB → BEY | Apr 25, 07:00 UTC | Apr 25, 10:05 UTC | 3h 5m |
| 2026-04-24 | FDB59K | KHI → DXB | Apr 24, 13:15 UTC | Apr 24, 13:35 UTC | 20m |
| 2026-04-24 | FDB3YX | DXB → KHI | Apr 24, 08:45 UTC | Apr 24, 09:10 UTC | 25m |
| 2026-04-23 | FDB1YT | BAH → DXB | Apr 23, 06:01 UTC | Apr 23, 07:30 UTC | 1h 30m |
| 2026-04-23 | FDB4JZ | DXB → BAH | Apr 23, 04:05 UTC | Apr 23, 04:30 UTC | 25m |
| 2026-04-23 | FDB4JZ | DXB → BAH | Apr 23, 02:15 UTC | Apr 23, 03:25 UTC | 1h 10m |
| 2026-04-21 | FDB7AQ | DXB → ISU | Apr 21, 06:45 UTC | Apr 21, 14:50 UTC | 8h 5m |
| 2026-04-20 | FDB5WB | BEY → DXB | Apr 20, 12:00 UTC | Apr 20, 15:00 UTC | 3h 0m |
| 2026-04-20 | FDB5JA | DXB → BEY | Apr 20, 06:40 UTC | Apr 20, 07:50 UTC | 1h 10m |
| 2026-04-19 | FDB3HP | BSR → DXB | Apr 19, 08:20 UTC | Apr 19, 16:35 UTC | 8h 15m |
| 2026-04-18 | FDB2UB | LYP → DXB | Apr 18, 01:30 UTC | Apr 18, 01:55 UTC | 25m |
| 2026-04-17 | FDB355 | DXB → LYP | Apr 17, 19:05 UTC | Apr 17, 19:20 UTC | 15m |
| 2026-04-16 | FDB16T | BAH → DXB | Apr 16, 13:15 UTC | Apr 16, 15:05 UTC | 1h 50m |
| 2026-04-16 | FDB16T | BAH → DXB | Apr 16, 12:55 UTC | Apr 16, 13:05 UTC | 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-FKE page for operator, model, and routing details .