sensors Mode-S transponder
8964D1
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-FMB · BOEING 737 MAX 8
- Hex
- 8964D1
- Octal
- 42262321
- Decimal
- 9,004,241
- Country
- AE
- Tail
- A6-FMB
- Type
- B38M
- Flights observed
- 89
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address 8964D1 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 |
|---|---|---|---|
| FDB1NU | Fly Dubai | 8 | 2026-05-19 |
| FDB5GE | Fly Dubai | 7 | 2026-05-24 |
| FDB9UR | Fly Dubai | 4 | 2026-04-16 |
| FDB539 | Fly Dubai | 4 | 2026-05-15 |
| FDB1626 | Fly Dubai | 4 | 2026-05-25 |
| FDB794 | Fly Dubai | 3 | 2026-04-17 |
| FDB793 | Fly Dubai | 3 | 2026-05-19 |
| FDB71T | Fly Dubai | 2 | 2026-04-30 |
| FDB65E | Fly Dubai | 2 | 2026-05-03 |
| FDB5WH | Fly Dubai | 2 | 2026-05-29 |
| FDB540 | Fly Dubai | 2 | 2026-05-15 |
| FDB461 | Fly Dubai | 2 | 2026-04-15 |
| FDB430 | Fly Dubai | 2 | 2026-05-03 |
| FDB3PR | Fly Dubai | 2 | 2026-05-29 |
| FDB2WK | Fly Dubai | 2 | 2026-04-30 |
| FDB2RG | Fly Dubai | 2 | 2026-04-13 |
| FDB2EX | Fly Dubai | 2 | 2026-05-09 |
| FDB14Q | Fly Dubai | 2 | 2026-05-16 |
| FDB1134 | Fly Dubai | 2 | 2026-05-27 |
| FDB1133 | Fly Dubai | 2 | 2026-05-26 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | FDB5PS | TBS → DXB | May 30, 02:35 UTC | May 30, 03:05 UTC | 30m |
| 2026-05-30 | FDB7WG | DXB → TBS | May 30, 00:15 UTC | May 30, 00:35 UTC | 20m |
| 2026-05-29 | FDB3PR | SOF → DXB | May 29, 13:20 UTC | May 29, 17:30 UTC | 4h 10m |
| 2026-05-29 | FDB5WH | DXB → SOF | May 29, 01:00 UTC | May 29, 11:30 UTC | 10h 30m |
| 2026-05-28 | FDB5WH | DXB → SOF | May 28, 13:30 UTC | May 29, 11:30 UTC | 22h 0m |
| 2026-05-27 | FDB1QS | PRG → DXB | May 27, 19:25 UTC | May 28, 08:55 UTC | 13h 30m |
| 2026-05-27 | FDB1134 | KTM → DXB | May 27, 04:30 UTC | May 27, 17:35 UTC | 13h 5m |
| 2026-05-26 | FDB1133 | DXB → KTM | May 26, 15:00 UTC | May 27, 01:49 UTC | 10h 50m |
| 2026-05-25 | FDB1626 | TLV → DXB | May 25, 18:40 UTC | May 26, 15:39 UTC | 20h 59m |
| 2026-05-25 | FDB1626 | TLV → DXB | May 25, 16:50 UTC | May 26, 15:39 UTC | 22h 49m |
| 2026-05-25 | FDB1625 | DXB → TLV | May 25, 14:40 UTC | May 25, 15:10 UTC | 30m |
| 2026-05-24 | FDB5GE | OTP → DXB | May 24, 06:40 UTC | May 24, 11:15 UTC | 4h 35m |
| 2026-05-23 | FDB1626 | TLV → DXB | May 23, 18:20 UTC | May 23, 19:05 UTC | 45m |
| 2026-05-23 | FDB1626 | TLV → DXB | May 23, 16:35 UTC | May 23, 16:50 UTC | 15m |
| 2026-05-21 | FDB906 | ULH → DXB | May 21, 17:10 UTC | May 21, 17:35 UTC | 25m |
| 2026-05-19 | FDB793 | DXB → DYU | May 19, 20:00 UTC | May 20, 16:25 UTC | 20h 26m |
| 2026-05-19 | FDB5GE | OTP → DXB | May 19, 07:00 UTC | May 19, 20:05 UTC | 13h 5m |
| 2026-05-19 | FDB1NU | DXB → OTP | May 19, 04:25 UTC | May 19, 05:10 UTC | 45m |
| 2026-05-18 | FDB868 | DMM → DXB | May 18, 17:05 UTC | May 18, 17:40 UTC | 35m |
| 2026-05-18 | FDB1134 | KTM → DXB | May 18, 03:40 UTC | May 18, 06:20 UTC | 2h 40m |
| 2026-05-17 | FDB1133 | DXB → KTM | May 17, 15:10 UTC | May 18, 01:15 UTC | 10h 5m |
| 2026-05-16 | FDB4CE | BEG → DXB | May 16, 22:50 UTC | May 17, 15:50 UTC | 17h 0m |
| 2026-05-16 | FDB14Q | DXB → BEG | May 16, 15:50 UTC | May 16, 21:15 UTC | 5h 25m |
| 2026-05-15 | FDB14Q | DXB → BEG | May 15, 22:55 UTC | May 16, 21:15 UTC | 22h 20m |
| 2026-05-15 | FDB540 | KTM → DXB | May 15, 10:25 UTC | May 15, 23:35 UTC | 13h 9m |
| 2026-05-15 | FDB539 | DXB → KTM | May 15, 07:00 UTC | May 15, 08:40 UTC | 1h 40m |
| 2026-05-14 | FDB539 | DXB → KTM | May 14, 09:45 UTC | May 15, 08:15 UTC | 22h 30m |
| 2026-05-11 | FDB3PR | SOF → DXB | May 11, 12:50 UTC | May 11, 16:55 UTC | 4h 5m |
| 2026-05-10 | FDB2MF | IST → DXB | May 10, 18:35 UTC | May 11, 11:00 UTC | 16h 25m |
| 2026-05-09 | FDB2EX | DXB → KZN | May 9, 20:40 UTC | May 10, 12:49 UTC | 16h 10m |
| 2026-05-09 | FDB2EX | DXB → KZN | May 9, 08:20 UTC | May 10, 02:30 UTC | 18h 10m |
| 2026-05-09 | FDB848 | RUH → DXB | May 9, 08:00 UTC | May 10, 02:30 UTC | 18h 30m |
| 2026-05-06 | FDB5YA | VKO → DXB | May 6, 20:20 UTC | May 6, 20:35 UTC | 15m |
| 2026-05-06 | FDB9CA | DXB → VKO | May 6, 05:10 UTC | May 6, 05:30 UTC | 20m |
| 2026-05-05 | FDB828 | MED → DXB | May 5, 23:15 UTC | May 5, 23:45 UTC | 30m |
| 2026-05-03 | FDB65E | EBB → DXB | May 3, 10:25 UTC | May 3, 21:44 UTC | 11h 20m |
| 2026-05-03 | FDB430 | CCJ → DXB | May 3, 06:45 UTC | May 3, 07:10 UTC | 25m |
| 2026-05-03 | FDB430 | CCJ → DXB | May 3, 03:45 UTC | May 3, 04:55 UTC | 1h 10m |
| 2026-05-03 | FDB2JQ | DXB → CCJ | May 3, 00:40 UTC | May 3, 01:50 UTC | 1h 10m |
| 2026-05-02 | FDB5GE | OTP → DXB | May 2, 06:55 UTC | May 2, 11:45 UTC | 4h 50m |
| 2026-05-02 | FDB1NU | DXB → OTP | May 2, 00:05 UTC | May 2, 05:40 UTC | 5h 35m |
| 2026-05-01 | FDB3KJ | MBA → DXB | May 1, 10:20 UTC | May 1, 21:20 UTC | 11h 0m |
| 2026-04-30 | FDB919 | DXB → JED | Apr 30, 21:55 UTC | Apr 30, 23:05 UTC | 1h 10m |
| 2026-04-30 | FDB71T | TBS → DXB | Apr 30, 13:10 UTC | Apr 30, 17:15 UTC | 4h 5m |
| 2026-04-30 | FDB2WK | DXB → TBS | Apr 30, 07:05 UTC | Apr 30, 11:25 UTC | 4h 20m |
| 2026-04-29 | FDB65E | EBB → DXB | Apr 29, 09:45 UTC | Apr 29, 21:20 UTC | 11h 35m |
| 2026-04-28 | FDB920 | JED → DXB | Apr 28, 22:00 UTC | Apr 29, 04:25 UTC | 6h 25m |
| 2026-04-28 | FDB7UE | EVN → DXB | Apr 28, 11:20 UTC | Apr 28, 12:30 UTC | 1h 10m |
| 2026-04-28 | FDB59G | DXB → EVN | Apr 28, 02:25 UTC | Apr 28, 06:35 UTC | 4h 10m |
| 2026-04-27 | FDB746 | TIA → DXB | Apr 27, 12:10 UTC | Apr 27, 17:05 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-FMB page for operator, model, and routing details .