sensors Mode-S transponder
8965B2
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-FMV · BOEING 737 MAX 8
- Hex
- 8965B2
- Octal
- 42262662
- Decimal
- 9,004,466
- Country
- AE
- Tail
- A6-FMV
- Type
- B38M
- Flights observed
- 100
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 16h ago
Last known position
Country allocation
The ICAO 24-bit address 8965B2 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 |
|---|---|---|---|
| FDB540 | Fly Dubai | 7 | 2026-04-22 |
| FDB7ML | Fly Dubai | 6 | 2026-05-17 |
| FDB1549 | Fly Dubai | 6 | 2026-05-27 |
| FDB539 | Fly Dubai | 5 | 2026-04-22 |
| FDB1550 | Fly Dubai | 4 | 2026-05-11 |
| FDB884 | Fly Dubai | 3 | 2026-05-05 |
| FDB5WH | Fly Dubai | 3 | 2026-05-08 |
| FDB1025 | Fly Dubai | 3 | 2026-05-24 |
| FDB883 | Fly Dubai | 2 | 2026-04-16 |
| FDB848 | Fly Dubai | 2 | 2026-05-29 |
| FDB811 | Fly Dubai | 2 | 2026-04-21 |
| FDB3PR | Fly Dubai | 2 | 2026-05-08 |
| FDB37M | Fly Dubai | 2 | 2026-05-06 |
| FDB2WK | Fly Dubai | 2 | 2026-05-18 |
| FDB2GT | - | 2 | 2026-04-13 |
| FDB1KS | Fly Dubai | 2 | 2026-05-23 |
| FDB1126 | Fly Dubai | 2 | 2026-05-21 |
| FDB9YD | Fly Dubai | 1 | 2026-05-22 |
| FDB9QG | Fly Dubai | 1 | 2026-04-18 |
| FDB9JZ | Fly Dubai | 1 | 2026-04-16 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | FDB1QS | PRG → DXB | May 29, 20:20 UTC | May 30, 01:55 UTC | 5h 35m |
| 2026-05-29 | FDB848 | RUH → DXB | May 29, 07:45 UTC | May 29, 13:20 UTC | 5h 35m |
| 2026-05-27 | FDB1549 | DXB → TLV | May 27, 04:09 UTC | May 27, 16:05 UTC | 11h 56m |
| 2026-05-24 | FDB756 | IST → DXB | May 24, 23:30 UTC | May 25, 03:30 UTC | 4h 0m |
| 2026-05-24 | FDB3VG | DXB → IST | May 24, 21:25 UTC | May 24, 21:35 UTC | 10m |
| 2026-05-24 | FDB1025 | DXB → MLE | May 24, 04:10 UTC | May 24, 19:45 UTC | 15h 35m |
| 2026-05-23 | FDB1KS | BEG → DXB | May 23, 12:35 UTC | May 24, 06:45 UTC | 18h 10m |
| 2026-05-23 | FDB1KS | BEG → DXB | May 23, 12:05 UTC | May 24, 06:45 UTC | 18h 40m |
| 2026-05-22 | FDB9YD | DXB → BEG | May 22, 14:45 UTC | May 23, 10:15 UTC | 19h 29m |
| 2026-05-22 | FDB7LW | - | May 22, 09:40 UTC | May 23, 08:10 UTC | 22h 29m |
| 2026-05-21 | FDB1126 | TLV → DXB | May 21, 17:15 UTC | May 22, 14:50 UTC | 21h 35m |
| 2026-05-21 | FDB1126 | TLV → DXB | May 21, 15:20 UTC | May 21, 15:35 UTC | 15m |
| 2026-05-21 | FDB444 | LKO → DXB | May 21, 03:25 UTC | May 21, 04:30 UTC | 1h 5m |
| 2026-05-20 | FDB443 | DXB → LKO | May 20, 12:45 UTC | May 21, 00:55 UTC | 12h 10m |
| 2026-05-20 | FDB446 | BOM → DXB | May 20, 00:15 UTC | May 20, 10:45 UTC | 10h 31m |
| 2026-05-19 | FDB71T | TBS → DXB | May 19, 13:00 UTC | May 19, 22:45 UTC | 9h 45m |
| 2026-05-18 | FDB2WK | DXB → TBS | May 18, 21:45 UTC | May 19, 11:10 UTC | 13h 25m |
| 2026-05-18 | FDB2WK | DXB → TBS | May 18, 15:45 UTC | May 19, 11:10 UTC | 19h 24m |
| 2026-05-18 | FDB580 | CMB → DXB | May 18, 04:15 UTC | May 18, 22:20 UTC | 18h 4m |
| 2026-05-17 | FDB7ML | RMO → DXB | May 17, 13:01 UTC | May 18, 02:00 UTC | 13h 0m |
| 2026-05-16 | FDB7ML | RMO → DXB | May 16, 21:40 UTC | May 17, 15:05 UTC | 17h 25m |
| 2026-05-14 | FDB1134 | KTM → DXB | May 14, 03:40 UTC | May 14, 16:25 UTC | 12h 45m |
| 2026-05-14 | FDB1133 | DXB → KTM | May 14, 00:20 UTC | May 14, 01:45 UTC | 1h 25m |
| 2026-05-13 | FDB3HP | BSR → DXB | May 13, 15:20 UTC | May 13, 16:40 UTC | 1h 20m |
| 2026-05-12 | FDB5WB | BEY → DXB | May 12, 12:15 UTC | May 12, 12:45 UTC | 30m |
| 2026-05-11 | FDB570 | CMB → DXB | May 11, 21:20 UTC | May 11, 22:15 UTC | 55m |
| 2026-05-11 | FDB569 | DXB → CMB | May 11, 10:05 UTC | May 11, 18:55 UTC | 8h 50m |
| 2026-05-11 | FDB1550 | TLV → DXB | May 11, 08:05 UTC | May 11, 08:25 UTC | 20m |
| 2026-05-11 | FDB1549 | DXB → TLV | May 11, 05:25 UTC | May 11, 05:50 UTC | 25m |
| 2026-05-10 | FDB707 | DXB → GYD | May 10, 08:35 UTC | May 11, 03:40 UTC | 19h 5m |
| 2026-05-09 | FDB1941 | DXB → TAS | May 9, 18:10 UTC | May 9, 18:30 UTC | 20m |
| 2026-05-08 | FDB3PR | SOF → DXB | May 8, 12:49 UTC | May 8, 16:55 UTC | 4h 5m |
| 2026-05-08 | FDB5WH | DXB → SOF | May 8, 08:49 UTC | May 8, 11:09 UTC | 2h 20m |
| 2026-05-07 | FDB5WH | DXB → SOF | May 7, 13:40 UTC | May 8, 11:09 UTC | 21h 29m |
| 2026-05-06 | FDB7ML | RMO → DXB | May 6, 17:05 UTC | May 7, 14:05 UTC | 21h 0m |
| 2026-05-06 | FDB7ML | RMO → DXB | May 6, 15:25 UTC | May 7, 14:05 UTC | 22h 40m |
| 2026-05-06 | FDB7ML | RMO → DXB | May 6, 13:20 UTC | May 6, 17:45 UTC | 4h 24m |
| 2026-05-06 | FDB37M | DXB → RMO | May 6, 07:10 UTC | May 6, 11:35 UTC | 4h 25m |
| 2026-05-05 | FDB884 | DMM → DXB | May 5, 07:05 UTC | May 5, 09:00 UTC | 1h 55m |
| 2026-05-04 | FDB9DV | DXB → EBL | May 4, 07:10 UTC | May 4, 15:40 UTC | 8h 30m |
| 2026-05-04 | FDB436 | HYD → DXB | May 4, 01:00 UTC | May 4, 01:40 UTC | 40m |
| 2026-05-03 | FDB435 | DXB → HYD | May 3, 17:24 UTC | May 3, 23:10 UTC | 5h 45m |
| 2026-05-02 | FDB856 | RUH → DXB | May 2, 19:00 UTC | May 3, 13:20 UTC | 18h 19m |
| 2026-05-02 | FDB855 | DXB → RUH | May 2, 15:00 UTC | May 3, 13:20 UTC | 22h 19m |
| 2026-05-02 | FDB848 | RUH → DXB | May 2, 03:55 UTC | May 2, 08:35 UTC | 4h 40m |
| 2026-05-01 | FDB5GE | OTP → DXB | May 1, 06:50 UTC | May 1, 11:45 UTC | 4h 55m |
| 2026-04-30 | FDB1NU | DXB → OTP | Apr 30, 23:05 UTC | May 1, 04:40 UTC | 5h 35m |
| 2026-04-30 | FDB7ML | RMO → DXB | Apr 30, 12:20 UTC | Apr 30, 17:20 UTC | 5h 0m |
| 2026-04-29 | FDB37M | DXB → RMO | Apr 29, 03:55 UTC | Apr 29, 09:25 UTC | 5h 31m |
| 2026-04-28 | FDB1688 | ZNZ → DXB | Apr 28, 06:10 UTC | Apr 28, 23:00 UTC | 16h 50m |
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-FMV page for operator, model, and routing details .