sensors Mode-S transponder
8965B4
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-FMX · BOEING 737 MAX 8
- Hex
- 8965B4
- Octal
- 42262664
- Decimal
- 9,004,468
- Country
- AE
- Tail
- A6-FMX
- Type
- B38M
- Flights observed
- 104
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 3h ago
Last known position
Country allocation
The ICAO 24-bit address 8965B4 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 |
|---|---|---|---|
| FDB1082 | Fly Dubai | 8 | 2026-04-28 |
| FDB1133 | Fly Dubai | 7 | 2026-05-01 |
| FDB1134 | Fly Dubai | 6 | 2026-05-01 |
| FDB1081 | Fly Dubai | 6 | 2026-04-28 |
| FDB71T | Fly Dubai | 3 | 2026-04-14 |
| FDB5GE | Fly Dubai | 3 | 2026-05-05 |
| FDB2RG | Fly Dubai | 3 | 2026-05-22 |
| FDB2PJ | Fly Dubai | 3 | 2026-04-15 |
| FDB1NU | Fly Dubai | 3 | 2026-05-05 |
| FDB919 | Fly Dubai | 2 | 2026-04-24 |
| FDB914 | Fly Dubai | 2 | 2026-05-18 |
| FDB842 | Fly Dubai | 2 | 2026-05-16 |
| FDB7UE | - | 2 | 2026-04-13 |
| FDB59G | - | 2 | 2026-04-13 |
| FDB52X | Fly Dubai | 2 | 2026-05-04 |
| FDB4CE | Fly Dubai | 2 | 2026-04-29 |
| FDB3DK | - | 2 | 2026-04-16 |
| FDB2WK | Fly Dubai | 2 | 2026-04-14 |
| FDB1BM | - | 2 | 2026-05-04 |
| FDB1550 | Fly Dubai | 2 | 2026-05-15 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | FDB1078 | CFU → DXB | May 30, 13:35 UTC | May 30, 17:20 UTC | 3h 45m |
| 2026-05-29 | FDB454 | COK → DXB | May 29, 22:05 UTC | May 29, 23:35 UTC | 1h 30m |
| 2026-05-29 | FDB4HX | DBV → DXB | May 29, 06:05 UTC | May 29, 20:35 UTC | 14h 30m |
| 2026-05-27 | FDB750 | TIV → DXB | May 27, 16:10 UTC | May 28, 10:45 UTC | 18h 35m |
| 2026-05-25 | FDB756 | IST → DXB | May 25, 23:30 UTC | May 26, 03:30 UTC | 4h 0m |
| 2026-05-25 | FDB3VG | DXB → IST | May 25, 21:40 UTC | May 25, 21:49 UTC | 10m |
| 2026-05-24 | FDB4TA | ZAG → DXB | May 24, 13:00 UTC | May 25, 06:00 UTC | 17h 0m |
| 2026-05-24 | FDB4MA | DXB → ZAG | May 24, 09:50 UTC | May 24, 11:25 UTC | 1h 35m |
| 2026-05-22 | FDB2RG | OTP → DXB | May 22, 12:25 UTC | May 23, 02:00 UTC | 13h 35m |
| 2026-05-22 | FDB3PL | DXB → OTP | May 22, 09:45 UTC | May 22, 10:35 UTC | 50m |
| 2026-05-19 | FDB7KL | AMM → DXB | May 19, 18:10 UTC | May 20, 12:45 UTC | 18h 36m |
| 2026-05-18 | FDB914 | AJF → DXB | May 18, 10:25 UTC | May 18, 10:55 UTC | 30m |
| 2026-05-17 | FDB3PR | SOF → DXB | May 17, 13:10 UTC | May 17, 17:01 UTC | 3h 50m |
| 2026-05-16 | FDB846 | RUH → DXB | May 16, 21:50 UTC | May 17, 11:35 UTC | 13h 45m |
| 2026-05-16 | FDB842 | RUH → DXB | May 16, 11:05 UTC | May 17, 01:40 UTC | 14h 35m |
| 2026-05-15 | FDB842 | RUH → DXB | May 15, 20:25 UTC | May 16, 11:35 UTC | 15h 11m |
| 2026-05-15 | FDB1550 | TLV → DXB | May 15, 10:05 UTC | May 15, 20:25 UTC | 10h 19m |
| 2026-05-15 | FDB1550 | TLV → DXB | May 15, 08:20 UTC | May 15, 08:35 UTC | 15m |
| 2026-05-15 | FDB1549 | DXB → TLV | May 15, 06:25 UTC | May 15, 06:55 UTC | 30m |
| 2026-05-14 | FDB914 | AJF → DXB | May 14, 10:00 UTC | May 15, 04:25 UTC | 18h 25m |
| 2026-05-13 | FDB746 | TIA → DXB | May 13, 12:50 UTC | May 13, 17:35 UTC | 4h 45m |
| 2026-05-12 | FDB2RG | OTP → DXB | May 12, 15:30 UTC | May 13, 10:00 UTC | 18h 30m |
| 2026-05-12 | FDB2RG | OTP → DXB | May 12, 14:05 UTC | May 13, 10:00 UTC | 19h 55m |
| 2026-05-11 | FDB574 | KTM → DXB | May 11, 17:50 UTC | May 12, 11:05 UTC | 17h 15m |
| 2026-05-11 | FDB573 | DXB → KTM | May 11, 03:35 UTC | May 11, 15:45 UTC | 12h 10m |
| 2026-05-08 | FDB5WB | BEY → DXB | May 8, 12:55 UTC | May 8, 15:10 UTC | 2h 15m |
| 2026-05-07 | FDB932 | NUM → DXB | May 7, 10:20 UTC | May 7, 10:55 UTC | 35m |
| 2026-05-05 | FDB5GE | OTP → DXB | May 5, 07:15 UTC | May 5, 12:35 UTC | 5h 20m |
| 2026-05-05 | FDB1NU | DXB → OTP | May 5, 05:30 UTC | May 5, 05:50 UTC | 20m |
| 2026-05-04 | FDB1BM | - | May 4, 12:20 UTC | May 4, 17:15 UTC | 4h 55m |
| 2026-05-04 | FDB52X | DXB → SJJ | May 4, 04:55 UTC | May 4, 10:50 UTC | 5h 55m |
| 2026-05-03 | FDB5GE | OTP → DXB | May 3, 06:35 UTC | May 3, 11:45 UTC | 5h 10m |
| 2026-05-03 | FDB1NU | DXB → OTP | May 3, 00:30 UTC | May 3, 05:15 UTC | 4h 44m |
| 2026-05-02 | FDB1BM | - | May 2, 13:00 UTC | May 2, 18:40 UTC | 5h 40m |
| 2026-05-02 | FDB52X | DXB → SJJ | May 2, 04:55 UTC | May 2, 10:55 UTC | 6h 0m |
| 2026-05-01 | FDB645 | DXB → ASM | May 1, 15:25 UTC | May 1, 23:30 UTC | 8h 5m |
| 2026-05-01 | FDB1134 | KTM → DXB | May 1, 07:50 UTC | May 1, 08:10 UTC | 20m |
| 2026-05-01 | FDB1134 | KTM → DXB | May 1, 04:30 UTC | May 1, 05:25 UTC | 55m |
| 2026-05-01 | FDB1133 | DXB → KTM | May 1, 00:30 UTC | May 1, 01:25 UTC | 55m |
| 2026-04-30 | FDB1133 | DXB → KTM | Apr 30, 22:25 UTC | Apr 30, 22:50 UTC | 25m |
| 2026-04-30 | FDB841 | DXB → RUH | Apr 30, 07:25 UTC | Apr 30, 12:20 UTC | 4h 55m |
| 2026-04-29 | FDB4CE | BEG → DXB | Apr 29, 22:45 UTC | Apr 30, 04:05 UTC | 5h 19m |
| 2026-04-29 | FDB14Q | DXB → BEG | Apr 29, 13:40 UTC | Apr 29, 19:55 UTC | 6h 15m |
| 2026-04-29 | FDB1134 | KTM → DXB | Apr 29, 03:34 UTC | Apr 29, 07:45 UTC | 4h 10m |
| 2026-04-29 | FDB1133 | DXB → KTM | Apr 29, 00:10 UTC | Apr 29, 01:15 UTC | 1h 5m |
| 2026-04-28 | FDB1133 | DXB → KTM | Apr 28, 22:10 UTC | Apr 28, 22:35 UTC | 25m |
| 2026-04-28 | FDB1082 | TLV → DXB | Apr 28, 13:00 UTC | Apr 28, 16:05 UTC | 3h 5m |
| 2026-04-28 | FDB1081 | DXB → TLV | Apr 28, 07:40 UTC | Apr 28, 08:50 UTC | 1h 10m |
| 2026-04-27 | FDB1126 | TLV → DXB | Apr 27, 15:05 UTC | Apr 27, 18:05 UTC | 3h 0m |
| 2026-04-27 | FDB1125 | DXB → TLV | Apr 27, 13:05 UTC | Apr 27, 13:25 UTC | 20m |
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-FMX page for operator, model, and routing details .