sensors Mode-S transponder
896532
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-FMM · BOEING 737 MAX 8
- Hex
- 896532
- Octal
- 42262462
- Decimal
- 9,004,338
- Country
- AE
- Tail
- A6-FMM
- Type
- B38M
- Flights observed
- 81
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 896532 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 |
|---|---|---|---|
| FDB646 | Fly Dubai | 4 | 2026-05-21 |
| FDB2RG | Fly Dubai | 4 | 2026-04-17 |
| FDB1082 | Fly Dubai | 4 | 2026-05-16 |
| FDB1081 | Fly Dubai | 4 | 2026-05-17 |
| FDB884 | Fly Dubai | 3 | 2026-04-23 |
| FDB883 | Fly Dubai | 3 | 2026-04-23 |
| FDB830 | Fly Dubai | 3 | 2026-05-10 |
| FDB52X | Fly Dubai | 3 | 2026-05-25 |
| FDB3PL | Fly Dubai | 3 | 2026-04-17 |
| FDB1BM | - | 3 | 2026-05-25 |
| FDB9RF | Fly Dubai | 2 | 2026-05-05 |
| FDB868 | Fly Dubai | 2 | 2026-05-11 |
| FDB829 | - | 2 | 2026-04-13 |
| FDB5WB | Fly Dubai | 2 | 2026-05-13 |
| FDB580 | Fly Dubai | 2 | 2026-04-24 |
| FDB454 | Fly Dubai | 2 | 2026-05-05 |
| FDB444 | Fly Dubai | 2 | 2026-04-18 |
| FDB443 | Fly Dubai | 2 | 2026-04-18 |
| FDB1212 | Fly Dubai | 2 | 2026-05-07 |
| FDB870 | Fly Dubai | 1 | 2026-04-22 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-28 | FDB5GE | OTP → DXB | May 28, 06:45 UTC | May 28, 11:05 UTC | 4h 20m |
| 2026-05-28 | FDB1NU | DXB → OTP | May 28, 02:20 UTC | May 28, 04:50 UTC | 2h 30m |
| 2026-05-26 | FDB5JD | MCX → DXB | May 26, 10:54 UTC | May 27, 05:35 UTC | 18h 40m |
| 2026-05-25 | FDB1BM | - | May 25, 14:35 UTC | May 26, 08:39 UTC | 18h 4m |
| 2026-05-25 | FDB1BM | - | May 25, 13:30 UTC | May 26, 08:39 UTC | 19h 10m |
| 2026-05-25 | FDB52X | DXB → SJJ | May 25, 10:45 UTC | May 25, 12:05 UTC | 1h 20m |
| 2026-05-23 | FDB1078 | CFU → DXB | May 23, 13:40 UTC | May 24, 06:15 UTC | 16h 35m |
| 2026-05-23 | FDB1077 | DXB → CFU | May 23, 06:50 UTC | May 23, 11:40 UTC | 4h 50m |
| 2026-05-22 | FDB756 | IST → DXB | May 22, 23:45 UTC | May 23, 03:50 UTC | 4h 4m |
| 2026-05-22 | FDB3VG | DXB → IST | May 22, 05:20 UTC | May 22, 21:45 UTC | 16h 25m |
| 2026-05-21 | FDB646 | ASM → DXB | May 21, 21:50 UTC | May 22, 20:30 UTC | 22h 40m |
| 2026-05-21 | FDB646 | ASM → DXB | May 21, 09:45 UTC | May 22, 05:55 UTC | 20h 10m |
| 2026-05-21 | FDB646 | ASM → DXB | May 21, 08:20 UTC | May 22, 05:55 UTC | 21h 35m |
| 2026-05-21 | FDB646 | ASM → DXB | May 21, 04:40 UTC | May 21, 22:25 UTC | 17h 45m |
| 2026-05-18 | FDB1BM | - | May 18, 13:00 UTC | May 18, 17:20 UTC | 4h 20m |
| 2026-05-17 | FDB52X | DXB → SJJ | May 17, 23:00 UTC | May 18, 11:20 UTC | 12h 20m |
| 2026-05-17 | FDB52X | DXB → SJJ | May 17, 14:45 UTC | May 18, 11:20 UTC | 20h 35m |
| 2026-05-17 | FDB1081 | DXB → TLV | May 17, 11:05 UTC | May 17, 11:35 UTC | 30m |
| 2026-05-16 | FDB1082 | TLV → DXB | May 16, 14:35 UTC | May 16, 15:16 UTC | 40m |
| 2026-05-16 | FDB1082 | TLV → DXB | May 16, 12:55 UTC | May 16, 13:11 UTC | 15m |
| 2026-05-16 | FDB1081 | DXB → TLV | May 16, 11:16 UTC | May 16, 11:35 UTC | 20m |
| 2026-05-13 | FDB7AF | DEL → DXB | May 13, 22:55 UTC | May 13, 23:30 UTC | 35m |
| 2026-05-13 | FDB441 | DXB → DEL | May 13, 20:30 UTC | May 13, 21:15 UTC | 45m |
| 2026-05-13 | FDB5WB | BEY → DXB | May 13, 12:20 UTC | May 13, 15:35 UTC | 3h 15m |
| 2026-05-12 | FDB3DK | EBL → DXB | May 12, 13:45 UTC | May 13, 01:15 UTC | 11h 30m |
| 2026-05-11 | FDB868 | DMM → DXB | May 11, 17:10 UTC | May 11, 18:05 UTC | 55m |
| 2026-05-10 | FDB830 | JED → DXB | May 10, 01:50 UTC | May 10, 16:25 UTC | 14h 35m |
| 2026-05-09 | FDB830 | JED → DXB | May 9, 19:35 UTC | May 10, 16:25 UTC | 20h 50m |
| 2026-05-08 | FDB3QB | DXB → NBO | May 8, 17:45 UTC | May 8, 17:55 UTC | 10m |
| 2026-05-07 | FDB1212 | TLV → DXB | May 7, 14:00 UTC | May 8, 01:40 UTC | 11h 39m |
| 2026-05-07 | FDB1212 | TLV → DXB | May 7, 12:05 UTC | May 7, 12:25 UTC | 20m |
| 2026-05-07 | FDB1211 | DXB → TLV | May 7, 10:10 UTC | May 7, 10:15 UTC | 5m |
| 2026-05-05 | FDB454 | COK → DXB | May 5, 22:01 UTC | May 5, 22:25 UTC | 25m |
| 2026-05-05 | FDB9RF | DXB → COK | May 5, 19:40 UTC | May 5, 20:10 UTC | 30m |
| 2026-05-04 | FDB5WB | BEY → DXB | May 4, 12:10 UTC | May 4, 15:45 UTC | 3h 35m |
| 2026-05-04 | FDB5JA | DXB → BEY | May 4, 07:00 UTC | May 4, 07:55 UTC | 55m |
| 2026-05-03 | FDB846 | RUH → DXB | May 3, 20:25 UTC | May 4, 00:50 UTC | 4h 25m |
| 2026-05-03 | FDB746 | TIA → DXB | May 3, 11:40 UTC | May 3, 16:50 UTC | 5h 10m |
| 2026-05-03 | FDB34Q | DXB → TIA | May 3, 05:05 UTC | May 3, 09:40 UTC | 4h 35m |
| 2026-05-02 | FDB71T | TBS → DXB | May 2, 12:55 UTC | May 2, 17:05 UTC | 4h 10m |
| 2026-05-02 | FDB2WK | DXB → TBS | May 2, 07:00 UTC | May 2, 11:35 UTC | 4h 35m |
| 2026-05-01 | FDB454 | COK → DXB | May 1, 22:05 UTC | May 2, 01:40 UTC | 3h 35m |
| 2026-05-01 | FDB9RF | DXB → COK | May 1, 17:00 UTC | May 1, 20:25 UTC | 3h 25m |
| 2026-05-01 | FDB841 | DXB → RUH | May 1, 07:35 UTC | May 1, 12:15 UTC | 4h 40m |
| 2026-04-29 | FDB1082 | TLV → DXB | Apr 29, 14:40 UTC | Apr 29, 15:55 UTC | 1h 15m |
| 2026-04-29 | FDB1082 | TLV → DXB | Apr 29, 12:50 UTC | Apr 29, 13:10 UTC | 20m |
| 2026-04-29 | FDB1081 | DXB → TLV | Apr 29, 11:05 UTC | Apr 29, 11:15 UTC | 10m |
| 2026-04-29 | FDB1081 | DXB → TLV | Apr 29, 07:45 UTC | Apr 29, 09:00 UTC | 1h 16m |
| 2026-04-29 | FDB732 | ASB → DXB | Apr 29, 03:30 UTC | Apr 29, 03:55 UTC | 25m |
| 2026-04-28 | FDB731 | DXB → ASB | Apr 28, 18:05 UTC | Apr 28, 18:30 UTC | 25m |
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-FMM page for operator, model, and routing details .