sensors Mode-S transponder
8965B1
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-FMU · BOEING 737 MAX 8
- Hex
- 8965B1
- Octal
- 42262661
- Decimal
- 9,004,465
- Country
- AE
- Tail
- A6-FMU
- Type
- B38M
- Flights observed
- 104
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 3h ago
Last known position
Country allocation
The ICAO 24-bit address 8965B1 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 |
|---|---|---|---|
| FDB5EX | Fly Dubai | 4 | 2026-04-20 |
| FDB435 | Fly Dubai | 4 | 2026-05-13 |
| FDB2RG | Fly Dubai | 4 | 2026-05-21 |
| FDB14Q | Fly Dubai | 4 | 2026-05-29 |
| FDB7UE | Fly Dubai | 3 | 2026-05-12 |
| FDB71T | Fly Dubai | 3 | 2026-05-04 |
| FDB3PL | Fly Dubai | 3 | 2026-05-21 |
| FDB2WK | Fly Dubai | 3 | 2026-05-04 |
| FDB1NU | Fly Dubai | 3 | 2026-04-28 |
| FDB15L | Fly Dubai | 3 | 2026-04-16 |
| FDB1463 | Fly Dubai | 3 | 2026-05-28 |
| FDB1114 | Fly Dubai | 3 | 2026-05-09 |
| FDB1025 | Fly Dubai | 3 | 2026-05-02 |
| FDB9DV | Fly Dubai | 2 | 2026-04-15 |
| FDB884 | Fly Dubai | 2 | 2026-04-24 |
| FDB75L | Fly Dubai | 2 | 2026-04-16 |
| FDB5GE | Fly Dubai | 2 | 2026-04-29 |
| FDB59G | Fly Dubai | 2 | 2026-05-17 |
| FDB574 | Fly Dubai | 2 | 2026-05-18 |
| FDB4CE | Fly Dubai | 2 | 2026-05-29 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | FDB4CE | BEG → DXB | May 29, 21:55 UTC | May 30, 02:40 UTC | 4h 45m |
| 2026-05-29 | FDB14Q | DXB → BEG | May 29, 08:40 UTC | May 29, 20:25 UTC | 11h 45m |
| 2026-05-29 | FDB14Q | DXB → BEG | May 29, 01:40 UTC | May 29, 20:25 UTC | 18h 45m |
| 2026-05-28 | FDB14Q | DXB → BEG | May 28, 23:15 UTC | May 29, 20:25 UTC | 21h 10m |
| 2026-05-28 | FDB1463 | DXB → KBV | May 28, 04:40 UTC | May 29, 01:40 UTC | 21h 0m |
| 2026-05-26 | FDB1482 | KBV → DXB | May 26, 08:10 UTC | May 26, 20:50 UTC | 12h 40m |
| 2026-05-25 | FDB1481 | DXB → KBV | May 25, 14:45 UTC | May 26, 08:59 UTC | 18h 15m |
| 2026-05-25 | FDB3HP | BSR → DXB | May 25, 02:10 UTC | May 25, 15:25 UTC | 13h 15m |
| 2026-05-24 | FDB1464 | KBV → DXB | May 24, 08:50 UTC | May 25, 02:10 UTC | 17h 20m |
| 2026-05-23 | FDB1463 | DXB → KBV | May 23, 16:25 UTC | May 24, 10:20 UTC | 17h 55m |
| 2026-05-23 | FDB1463 | DXB → KBV | May 23, 15:40 UTC | May 24, 10:20 UTC | 18h 40m |
| 2026-05-23 | FDB1636 | TLV → DXB | May 23, 13:50 UTC | May 23, 14:10 UTC | 20m |
| 2026-05-23 | FDB1635 | DXB → TLV | May 23, 12:10 UTC | May 23, 12:20 UTC | 10m |
| 2026-05-23 | FDB1464 | KBV → DXB | May 23, 03:55 UTC | May 23, 04:25 UTC | 30m |
| 2026-05-21 | FDB2RG | OTP → DXB | May 21, 12:20 UTC | May 22, 01:40 UTC | 13h 20m |
| 2026-05-21 | FDB3PL | DXB → OTP | May 21, 09:50 UTC | May 21, 10:40 UTC | 50m |
| 2026-05-20 | FDB2RG | OTP → DXB | May 20, 14:25 UTC | May 21, 10:40 UTC | 20h 15m |
| 2026-05-20 | FDB2RG | OTP → DXB | May 20, 13:20 UTC | May 21, 10:40 UTC | 21h 20m |
| 2026-05-19 | FDB570 | CMB → DXB | May 19, 21:05 UTC | May 20, 11:15 UTC | 14h 11m |
| 2026-05-19 | FDB569 | DXB → CMB | May 19, 16:55 UTC | May 19, 18:40 UTC | 1h 45m |
| 2026-05-18 | FDB574 | KTM → DXB | May 18, 19:05 UTC | May 19, 18:15 UTC | 23h 10m |
| 2026-05-18 | FDB574 | KTM → DXB | May 18, 17:25 UTC | May 18, 20:05 UTC | 2h 39m |
| 2026-05-18 | FDB573 | DXB → KTM | May 18, 14:10 UTC | May 18, 15:35 UTC | 1h 25m |
| 2026-05-17 | FDB59G | DXB → EVN | May 17, 06:55 UTC | May 17, 07:05 UTC | 10m |
| 2026-05-16 | FDB868 | DMM → DXB | May 16, 17:01 UTC | May 16, 17:35 UTC | 35m |
| 2026-05-16 | FDB867 | DXB → DMM | May 16, 15:16 UTC | May 16, 15:25 UTC | 10m |
| 2026-05-16 | FDB1134 | KTM → DXB | May 16, 03:25 UTC | May 16, 06:16 UTC | 2h 51m |
| 2026-05-15 | FDB1133 | DXB → KTM | May 15, 12:00 UTC | May 16, 01:45 UTC | 13h 44m |
| 2026-05-13 | FDB435 | DXB → HYD | May 13, 18:40 UTC | May 13, 23:40 UTC | 5h 0m |
| 2026-05-12 | FDB7UE | EVN → DXB | May 12, 20:25 UTC | May 13, 12:30 UTC | 16h 5m |
| 2026-05-12 | FDB7UE | EVN → DXB | May 12, 17:10 UTC | May 13, 12:30 UTC | 19h 20m |
| 2026-05-10 | FDB435 | DXB → HYD | May 10, 04:19 UTC | May 10, 23:39 UTC | 19h 20m |
| 2026-05-10 | FDB435 | DXB → HYD | May 10, 04:09 UTC | May 10, 23:39 UTC | 19h 30m |
| 2026-05-09 | FDB1114 | DAM → DXB | May 9, 14:15 UTC | May 10, 06:50 UTC | 16h 35m |
| 2026-05-08 | FDB1114 | DAM → DXB | May 8, 22:20 UTC | May 9, 16:30 UTC | 18h 10m |
| 2026-05-08 | FDB1114 | DAM → DXB | May 8, 22:00 UTC | May 9, 16:30 UTC | 18h 30m |
| 2026-05-08 | FDB1550 | TLV → DXB | May 8, 08:05 UTC | May 8, 20:10 UTC | 12h 5m |
| 2026-05-07 | FDB1549 | DXB → TLV | May 7, 16:25 UTC | May 8, 06:20 UTC | 13h 55m |
| 2026-05-07 | FDB1082 | TLV → DXB | May 7, 14:10 UTC | May 7, 14:30 UTC | 20m |
| 2026-05-07 | FDB1081 | DXB → TLV | May 7, 12:05 UTC | May 7, 12:30 UTC | 25m |
| 2026-05-06 | FDB4TA | ZAG → DXB | May 6, 14:20 UTC | May 6, 19:15 UTC | 4h 55m |
| 2026-05-06 | FDB4MA | DXB → ZAG | May 6, 11:00 UTC | May 6, 12:40 UTC | 1h 40m |
| 2026-05-04 | FDB71T | TBS → DXB | May 4, 13:10 UTC | May 4, 20:05 UTC | 6h 56m |
| 2026-05-04 | FDB2WK | DXB → TBS | May 4, 06:35 UTC | May 4, 10:45 UTC | 4h 10m |
| 2026-05-03 | FDB454 | COK → DXB | May 3, 22:20 UTC | May 4, 02:00 UTC | 3h 40m |
| 2026-05-03 | FDB9RF | DXB → COK | May 3, 17:35 UTC | May 3, 20:55 UTC | 3h 20m |
| 2026-05-03 | FDB1026 | MLE → DXB | May 3, 12:10 UTC | May 3, 12:35 UTC | 25m |
| 2026-05-02 | FDB1025 | DXB → MLE | May 2, 23:00 UTC | May 3, 06:35 UTC | 7h 34m |
| 2026-05-01 | FDB1025 | DXB → MLE | May 1, 22:30 UTC | May 2, 12:55 UTC | 14h 25m |
| 2026-05-01 | FDB71T | TBS → DXB | May 1, 13:50 UTC | May 1, 17:55 UTC | 4h 5m |
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-FMU page for operator, model, and routing details .