sensors Mode-S transponder
8965B3
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-FMW · BOEING 737 MAX 8
- Hex
- 8965B3
- Octal
- 42262663
- Decimal
- 9,004,467
- Country
- AE
- Tail
- A6-FMW
- Type
- B38M
- Flights observed
- 92
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 8965B3 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 |
|---|---|---|---|
| FDB746 | Fly Dubai | 6 | 2026-05-08 |
| FDB2MF | Fly Dubai | 4 | 2026-05-17 |
| FDB870 | Fly Dubai | 3 | 2026-04-26 |
| FDB869 | Fly Dubai | 3 | 2026-04-26 |
| FDB7ML | - | 3 | 2026-04-16 |
| FDB579 | Fly Dubai | 3 | 2026-05-14 |
| FDB43F | Fly Dubai | 3 | 2026-04-28 |
| FDB37M | Fly Dubai | 3 | 2026-04-15 |
| FDB1ZA | Fly Dubai | 3 | 2026-05-02 |
| FDB9QG | Fly Dubai | 2 | 2026-04-28 |
| FDB882 | Fly Dubai | 2 | 2026-04-17 |
| FDB881 | Fly Dubai | 2 | 2026-04-17 |
| FDB868 | Fly Dubai | 2 | 2026-05-19 |
| FDB846 | Fly Dubai | 2 | 2026-04-25 |
| FDB7KL | Fly Dubai | 2 | 2026-05-18 |
| FDB750 | Fly Dubai | 2 | 2026-05-25 |
| FDB539 | Fly Dubai | 2 | 2026-05-02 |
| FDB4RM | Fly Dubai | 2 | 2026-05-02 |
| FDB34Q | Fly Dubai | 2 | 2026-05-08 |
| FDB2GT | Fly Dubai | 2 | 2026-04-30 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-27 | FDB1406 | BUD → DXB | May 27, 20:50 UTC | May 28, 15:55 UTC | 19h 5m |
| 2026-05-27 | FDB1405 | DXB → BUD | May 27, 07:20 UTC | May 27, 18:40 UTC | 11h 20m |
| 2026-05-26 | FDB1405 | DXB → BUD | May 26, 21:09 UTC | May 27, 18:40 UTC | 21h 30m |
| 2026-05-26 | FDB848 | RUH → DXB | May 26, 16:50 UTC | May 27, 15:30 UTC | 22h 40m |
| 2026-05-26 | FDB760 | AYT → DXB | May 26, 13:45 UTC | May 27, 08:05 UTC | 18h 21m |
| 2026-05-25 | FDB750 | TIV → DXB | May 25, 16:50 UTC | May 26, 12:14 UTC | 19h 24m |
| 2026-05-25 | FDB750 | TIV → DXB | May 25, 16:15 UTC | May 26, 12:14 UTC | 19h 59m |
| 2026-05-24 | FDB749 | DXB → TIV | May 24, 19:35 UTC | May 25, 14:20 UTC | 18h 45m |
| 2026-05-22 | FDB4TA | ZAG → DXB | May 22, 12:40 UTC | May 22, 15:15 UTC | 2h 35m |
| 2026-05-22 | FDB4MA | DXB → ZAG | May 22, 09:35 UTC | May 22, 11:15 UTC | 1h 40m |
| 2026-05-19 | FDB868 | DMM → DXB | May 19, 17:00 UTC | May 19, 18:00 UTC | 1h 0m |
| 2026-05-19 | FDB867 | DXB → DMM | May 19, 15:00 UTC | May 19, 15:10 UTC | 10m |
| 2026-05-18 | FDB7KL | AMM → DXB | May 18, 16:20 UTC | May 18, 22:15 UTC | 5h 54m |
| 2026-05-17 | FDB2MF | IST → DXB | May 17, 20:50 UTC | May 18, 18:10 UTC | 21h 20m |
| 2026-05-17 | FDB2MF | IST → DXB | May 17, 18:50 UTC | May 18, 18:10 UTC | 23h 20m |
| 2026-05-17 | FDB2MF | IST → DXB | May 17, 17:30 UTC | May 18, 16:25 UTC | 22h 55m |
| 2026-05-17 | FDB4GP | DXB → IST | May 17, 15:25 UTC | May 17, 15:40 UTC | 15m |
| 2026-05-15 | FDB868 | DMM → DXB | May 15, 17:05 UTC | May 15, 18:20 UTC | 1h 15m |
| 2026-05-14 | FDB579 | DXB → CMB | May 14, 01:30 UTC | May 14, 05:05 UTC | 3h 35m |
| 2026-05-13 | FDB1BM | - | May 13, 12:10 UTC | May 13, 17:30 UTC | 5h 20m |
| 2026-05-12 | FDB52X | DXB → SJJ | May 12, 18:20 UTC | May 13, 10:30 UTC | 16h 10m |
| 2026-05-10 | FDB4CE | BEG → DXB | May 10, 22:05 UTC | May 11, 16:05 UTC | 18h 0m |
| 2026-05-10 | FDB14Q | DXB → BEG | May 10, 04:25 UTC | May 10, 20:09 UTC | 15h 45m |
| 2026-05-09 | FDB579 | DXB → CMB | May 9, 06:50 UTC | May 10, 02:10 UTC | 19h 20m |
| 2026-05-09 | FDB579 | DXB → CMB | May 9, 04:25 UTC | May 10, 02:10 UTC | 21h 45m |
| 2026-05-08 | FDB746 | TIA → DXB | May 8, 12:49 UTC | May 9, 06:55 UTC | 18h 5m |
| 2026-05-08 | FDB746 | TIA → DXB | May 8, 12:44 UTC | May 9, 06:55 UTC | 18h 10m |
| 2026-05-08 | FDB34Q | DXB → TIA | May 8, 08:24 UTC | May 8, 10:44 UTC | 2h 20m |
| 2026-05-07 | FDB34Q | DXB → TIA | May 7, 11:55 UTC | May 8, 10:44 UTC | 22h 50m |
| 2026-05-06 | FDB2MF | IST → DXB | May 6, 17:45 UTC | May 7, 12:05 UTC | 18h 20m |
| 2026-05-06 | FDB5JD | MCX → DXB | May 6, 01:40 UTC | May 6, 05:30 UTC | 3h 50m |
| 2026-05-05 | FDB4XC | DXB → MCX | May 5, 19:15 UTC | May 5, 23:15 UTC | 4h 0m |
| 2026-05-04 | FDB1126 | TLV → DXB | May 4, 17:20 UTC | May 5, 12:10 UTC | 18h 51m |
| 2026-05-04 | FDB1126 | TLV → DXB | May 4, 15:15 UTC | May 5, 12:10 UTC | 20h 56m |
| 2026-05-04 | FDB1125 | DXB → TLV | May 4, 13:00 UTC | May 4, 13:15 UTC | 15m |
| 2026-05-04 | FDB1125 | DXB → TLV | May 4, 09:40 UTC | May 4, 10:35 UTC | 55m |
| 2026-05-02 | FDB1ZA | SPX → DXB | May 2, 23:05 UTC | May 3, 01:50 UTC | 2h 45m |
| 2026-05-02 | FDB4RM | DXB → SPX | May 2, 17:25 UTC | May 2, 21:20 UTC | 3h 55m |
| 2026-05-02 | FDB540 | KTM → DXB | May 2, 10:20 UTC | May 2, 14:35 UTC | 4h 15m |
| 2026-05-02 | FDB539 | DXB → KTM | May 2, 07:00 UTC | May 2, 07:55 UTC | 55m |
| 2026-05-02 | FDB539 | DXB → KTM | May 2, 04:55 UTC | May 2, 05:20 UTC | 25m |
| 2026-04-30 | FDB811 | DXB → AHB | Apr 30, 13:00 UTC | Apr 30, 18:55 UTC | 5h 55m |
| 2026-04-30 | FDB2GT | KHI → DXB | Apr 30, 08:00 UTC | Apr 30, 08:35 UTC | 35m |
| 2026-04-30 | FDB1KF | DXB → KHI | Apr 30, 03:35 UTC | Apr 30, 03:50 UTC | 15m |
| 2026-04-29 | FDB59G | DXB → EVN | Apr 29, 02:24 UTC | Apr 29, 12:15 UTC | 9h 51m |
| 2026-04-28 | FDB9QG | KHI → DXB | Apr 28, 20:10 UTC | Apr 28, 20:35 UTC | 25m |
| 2026-04-28 | FDB43F | DXB → KHI | Apr 28, 15:35 UTC | Apr 28, 15:55 UTC | 20m |
| 2026-04-28 | FDB2GT | KHI → DXB | Apr 28, 08:10 UTC | Apr 28, 08:30 UTC | 20m |
| 2026-04-28 | FDB1KF | DXB → KHI | Apr 28, 03:40 UTC | Apr 28, 04:00 UTC | 20m |
| 2026-04-27 | FDB43F | DXB → KHI | Apr 27, 15:40 UTC | Apr 27, 20:35 UTC | 4h 55m |
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-FMW page for operator, model, and routing details .