sensors Mode-S transponder
896531
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-FMK · BOEING 737 MAX 8
- Hex
- 896531
- Octal
- 42262461
- Decimal
- 9,004,337
- Country
- AE
- Tail
- A6-FMK
- Type
- B38M
- Flights observed
- 105
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 42m ago
Last known position
Country allocation
The ICAO 24-bit address 896531 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 |
|---|---|---|---|
| FDB1081 | Fly Dubai | 7 | 2026-05-13 |
| FDB1082 | Fly Dubai | 6 | 2026-05-13 |
| FDB1134 | Fly Dubai | 5 | 2026-05-25 |
| FDB4MA | Fly Dubai | 4 | 2026-05-20 |
| FDB4CE | Fly Dubai | 4 | 2026-04-16 |
| FDB2WK | Fly Dubai | 4 | 2026-05-11 |
| FDB7KL | Fly Dubai | 3 | 2026-05-28 |
| FDB793 | Fly Dubai | 3 | 2026-05-02 |
| FDB14Q | Fly Dubai | 3 | 2026-04-15 |
| FDB846 | Fly Dubai | 2 | 2026-05-14 |
| FDB71T | Fly Dubai | 2 | 2026-05-11 |
| FDB573 | Fly Dubai | 2 | 2026-04-21 |
| FDB540 | Fly Dubai | 2 | 2026-04-27 |
| FDB539 | Fly Dubai | 2 | 2026-04-27 |
| FDB52X | Fly Dubai | 2 | 2026-05-22 |
| FDB4TA | Fly Dubai | 2 | 2026-05-20 |
| FDB445 | Fly Dubai | 2 | 2026-04-30 |
| FDB430 | Fly Dubai | 2 | 2026-05-02 |
| FDB2RK | Fly Dubai | 2 | 2026-05-27 |
| FDB2MF | Fly Dubai | 2 | 2026-05-05 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-31 | FDB8762 | SJJ → DXB | May 31, 12:45 UTC | May 31, 14:15 UTC | 1h 30m |
| 2026-05-31 | FDB8761 | DXB → SJJ | May 31, 09:20 UTC | May 31, 11:00 UTC | 1h 40m |
| 2026-05-28 | FDB7KL | AMM → DXB | May 28, 21:35 UTC | May 29, 13:25 UTC | 15h 50m |
| 2026-05-28 | FDB7KL | AMM → DXB | May 28, 19:55 UTC | May 28, 20:05 UTC | 10m |
| 2026-05-28 | FDB143 | DXB → AMM | May 28, 18:10 UTC | May 28, 18:20 UTC | 10m |
| 2026-05-27 | FDB436 | HYD → DXB | May 27, 22:25 UTC | May 28, 16:25 UTC | 18h 0m |
| 2026-05-27 | FDB435 | DXB → HYD | May 27, 18:35 UTC | May 28, 16:15 UTC | 21h 40m |
| 2026-05-27 | FDB2RK | GYD → DXB | May 27, 08:20 UTC | May 27, 23:00 UTC | 14h 40m |
| 2026-05-26 | FDB2RK | GYD → DXB | May 26, 14:24 UTC | May 27, 12:05 UTC | 21h 41m |
| 2026-05-26 | FDB2PJ | DXB → EVN | May 26, 09:25 UTC | May 26, 09:35 UTC | 10m |
| 2026-05-25 | FDB1134 | KTM → DXB | May 25, 04:00 UTC | May 25, 06:40 UTC | 2h 40m |
| 2026-05-24 | FDB1574 | BGY → DXB | May 24, 11:50 UTC | May 24, 17:35 UTC | 5h 45m |
| 2026-05-23 | FDB64C | DXB → BGY | May 23, 14:20 UTC | May 24, 09:15 UTC | 18h 55m |
| 2026-05-23 | FDB1BM | - | May 23, 12:20 UTC | May 24, 09:15 UTC | 20h 55m |
| 2026-05-22 | FDB52X | DXB → SJJ | May 22, 21:05 UTC | May 23, 10:10 UTC | 13h 4m |
| 2026-05-20 | FDB4TA | ZAG → DXB | May 20, 13:45 UTC | May 20, 18:35 UTC | 4h 50m |
| 2026-05-20 | FDB4MA | DXB → ZAG | May 20, 10:25 UTC | May 20, 11:55 UTC | 1h 30m |
| 2026-05-19 | FDB4MA | DXB → ZAG | May 19, 12:35 UTC | May 20, 11:55 UTC | 23h 21m |
| 2026-05-18 | FDB1550 | TLV → DXB | May 18, 10:00 UTC | May 18, 10:35 UTC | 35m |
| 2026-05-18 | FDB1550 | TLV → DXB | May 18, 08:05 UTC | May 18, 08:20 UTC | 15m |
| 2026-05-18 | FDB1549 | DXB → TLV | May 18, 05:50 UTC | May 18, 06:35 UTC | 45m |
| 2026-05-14 | FDB846 | RUH → DXB | May 14, 00:00 UTC | May 14, 00:25 UTC | 25m |
| 2026-05-13 | FDB1082 | TLV → DXB | May 13, 14:51 UTC | May 13, 16:10 UTC | 1h 20m |
| 2026-05-13 | FDB1082 | TLV → DXB | May 13, 13:00 UTC | May 13, 13:20 UTC | 20m |
| 2026-05-13 | FDB1081 | DXB → TLV | May 13, 01:35 UTC | May 13, 11:00 UTC | 9h 25m |
| 2026-05-12 | FDB5CH | DXB → SVX | May 12, 19:45 UTC | May 12, 19:55 UTC | 10m |
| 2026-05-11 | FDB71T | TBS → DXB | May 11, 12:45 UTC | May 11, 16:20 UTC | 3h 35m |
| 2026-05-11 | FDB2WK | DXB → TBS | May 11, 10:10 UTC | May 11, 10:35 UTC | 25m |
| 2026-05-10 | FDB842 | RUH → DXB | May 10, 11:30 UTC | May 11, 10:15 UTC | 22h 45m |
| 2026-05-09 | FDB731 | DXB → ASB | May 9, 18:50 UTC | May 9, 19:14 UTC | 25m |
| 2026-05-09 | FDB1134 | KTM → DXB | May 9, 04:00 UTC | May 9, 05:20 UTC | 1h 20m |
| 2026-05-08 | FDB4TA | ZAG → DXB | May 8, 13:15 UTC | May 9, 02:00 UTC | 12h 45m |
| 2026-05-07 | FDB4MA | DXB → ZAG | May 7, 16:55 UTC | May 8, 11:30 UTC | 18h 35m |
| 2026-05-07 | FDB4MA | DXB → ZAG | May 7, 13:40 UTC | May 8, 11:30 UTC | 21h 50m |
| 2026-05-07 | FDB2WK | DXB → TBS | May 7, 11:45 UTC | May 7, 12:20 UTC | 35m |
| 2026-05-06 | FDB2WK | DXB → TBS | May 6, 12:20 UTC | May 7, 12:15 UTC | 23h 55m |
| 2026-05-06 | FDB7UE | EVN → DXB | May 6, 02:30 UTC | May 6, 12:35 UTC | 10h 5m |
| 2026-05-05 | FDB2MF | IST → DXB | May 5, 18:30 UTC | May 5, 20:35 UTC | 2h 5m |
| 2026-05-04 | FDB833 | DXB → JED | May 4, 07:10 UTC | May 4, 13:20 UTC | 6h 10m |
| 2026-05-03 | FDB871 | - | May 3, 19:10 UTC | May 4, 00:10 UTC | 5h 0m |
| 2026-05-03 | FDB1082 | TLV → DXB | May 3, 13:10 UTC | May 3, 16:20 UTC | 3h 10m |
| 2026-05-03 | FDB1081 | DXB → TLV | May 3, 11:25 UTC | May 3, 11:30 UTC | 5m |
| 2026-05-03 | FDB1081 | DXB → TLV | May 3, 07:50 UTC | May 3, 10:45 UTC | 2h 55m |
| 2026-05-02 | FDB793 | DXB → DYU | May 2, 20:10 UTC | May 3, 01:30 UTC | 5h 20m |
| 2026-05-02 | FDB793 | DXB → DYU | May 2, 18:15 UTC | May 2, 18:35 UTC | 20m |
| 2026-05-02 | FDB430 | CCJ → DXB | May 2, 06:35 UTC | May 2, 06:55 UTC | 20m |
| 2026-05-02 | FDB430 | CCJ → DXB | May 2, 03:35 UTC | May 2, 04:50 UTC | 1h 15m |
| 2026-05-01 | FDB2JQ | DXB → CCJ | May 1, 22:40 UTC | May 2, 00:50 UTC | 2h 10m |
| 2026-05-01 | FDB1ND | GYD → DXB | May 1, 18:30 UTC | May 1, 18:55 UTC | 25m |
| 2026-05-01 | FDB707 | DXB → GYD | May 1, 07:50 UTC | May 1, 08:15 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-FMK page for operator, model, and routing details .