sensors Mode-S transponder
896555
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-FMO · BOEING 737 MAX 8
- Hex
- 896555
- Octal
- 42262525
- Decimal
- 9,004,373
- Country
- AE
- Tail
- A6-FMO
- Type
- B38M
- Flights observed
- 124
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 6h ago
Last known position
Country allocation
The ICAO 24-bit address 896555 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 |
|---|---|---|---|
| FDB1134 | Fly Dubai | 8 | 2026-05-28 |
| FDB1133 | Fly Dubai | 6 | 2026-05-28 |
| FDB5GE | Fly Dubai | 5 | 2026-05-30 |
| FDB4TA | Fly Dubai | 5 | 2026-05-01 |
| FDB4MA | Fly Dubai | 5 | 2026-05-01 |
| FDB5CH | Fly Dubai | 4 | 2026-05-05 |
| FDB15L | - | 4 | 2026-04-13 |
| FDB75L | - | 3 | 2026-04-13 |
| FDB3DK | Fly Dubai | 3 | 2026-05-16 |
| FDB1NU | Fly Dubai | 3 | 2026-05-25 |
| FDB9UR | Fly Dubai | 2 | 2026-04-18 |
| FDB812 | Fly Dubai | 2 | 2026-04-16 |
| FDB7AF | Fly Dubai | 2 | 2026-05-10 |
| FDB71T | Fly Dubai | 2 | 2026-04-25 |
| FDB539 | Fly Dubai | 2 | 2026-04-24 |
| FDB461 | Fly Dubai | 2 | 2026-04-17 |
| FDB441 | Fly Dubai | 2 | 2026-05-10 |
| FDB436 | Fly Dubai | 2 | 2026-04-29 |
| FDB435 | Fly Dubai | 2 | 2026-04-28 |
| FDB2YF | Fly Dubai | 2 | 2026-05-03 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | FDB5GE | OTP → DXB | May 30, 06:45 UTC | May 30, 10:55 UTC | 4h 10m |
| 2026-05-29 | FDB750 | TIV → DXB | May 29, 16:20 UTC | May 30, 00:45 UTC | 8h 25m |
| 2026-05-28 | FDB4TB | DXB → VKO | May 28, 14:50 UTC | May 29, 03:35 UTC | 12h 45m |
| 2026-05-28 | FDB1134 | KTM → DXB | May 28, 05:20 UTC | May 29, 03:35 UTC | 22h 15m |
| 2026-05-28 | FDB1134 | KTM → DXB | May 28, 03:45 UTC | May 28, 18:15 UTC | 14h 30m |
| 2026-05-28 | FDB1133 | DXB → KTM | May 28, 00:30 UTC | May 28, 02:00 UTC | 1h 30m |
| 2026-05-27 | FDB707 | DXB → GYD | May 27, 03:09 UTC | May 27, 11:45 UTC | 8h 36m |
| 2026-05-26 | FDB1NB | VKO → DXB | May 26, 05:34 UTC | May 27, 03:14 UTC | 21h 40m |
| 2026-05-25 | FDB1NB | VKO → DXB | May 25, 11:20 UTC | May 26, 05:40 UTC | 18h 19m |
| 2026-05-25 | FDB5GE | OTP → DXB | May 25, 10:45 UTC | May 26, 05:40 UTC | 18h 54m |
| 2026-05-25 | FDB5GE | OTP → DXB | May 25, 07:20 UTC | May 26, 05:40 UTC | 22h 19m |
| 2026-05-25 | FDB5GE | OTP → DXB | May 25, 06:55 UTC | May 25, 11:20 UTC | 4h 25m |
| 2026-05-25 | FDB1NU | DXB → OTP | May 25, 02:40 UTC | May 25, 05:05 UTC | 2h 25m |
| 2026-05-23 | FDB1574 | BGY → DXB | May 23, 12:00 UTC | May 23, 17:55 UTC | 5h 55m |
| 2026-05-21 | FDB64C | DXB → BGY | May 21, 16:05 UTC | May 22, 09:20 UTC | 17h 15m |
| 2026-05-20 | FDB830 | JED → DXB | May 20, 18:30 UTC | May 21, 16:40 UTC | 22h 10m |
| 2026-05-19 | FDB620 | EBB → DXB | May 19, 13:00 UTC | May 20, 07:10 UTC | 18h 11m |
| 2026-05-17 | FDB1ZA | SPX → DXB | May 17, 23:10 UTC | May 18, 01:45 UTC | 2h 35m |
| 2026-05-17 | FDB4RM | DXB → SPX | May 17, 21:01 UTC | May 17, 21:25 UTC | 25m |
| 2026-05-16 | FDB3DK | EBL → DXB | May 16, 13:35 UTC | May 16, 14:20 UTC | 45m |
| 2026-05-15 | FDB3DK | EBL → DXB | May 15, 16:10 UTC | May 16, 14:20 UTC | 22h 11m |
| 2026-05-15 | FDB2RG | OTP → DXB | May 15, 12:50 UTC | May 15, 16:55 UTC | 4h 4m |
| 2026-05-14 | FDB3PL | DXB → OTP | May 14, 21:05 UTC | May 15, 10:40 UTC | 13h 35m |
| 2026-05-14 | FDB9RF | DXB → COK | May 14, 18:50 UTC | May 14, 19:20 UTC | 30m |
| 2026-05-13 | FDB1QV | EVN → DXB | May 13, 11:25 UTC | May 13, 14:25 UTC | 3h 0m |
| 2026-05-13 | FDB2PJ | DXB → EVN | May 13, 09:10 UTC | May 13, 09:35 UTC | 25m |
| 2026-05-10 | FDB7AF | DEL → DXB | May 10, 23:00 UTC | May 11, 14:00 UTC | 15h 0m |
| 2026-05-10 | FDB441 | DXB → DEL | May 10, 13:05 UTC | May 10, 21:10 UTC | 8h 5m |
| 2026-05-09 | FDB580 | CMB → DXB | May 9, 04:10 UTC | May 9, 05:10 UTC | 1h 0m |
| 2026-05-08 | FDB579 | DXB → CMB | May 8, 15:20 UTC | May 9, 01:55 UTC | 10h 35m |
| 2026-05-08 | FDB3HP | BSR → DXB | May 8, 01:19 UTC | May 9, 01:15 UTC | 23h 55m |
| 2026-05-05 | FDB5CH | DXB → SVX | May 5, 16:55 UTC | May 6, 01:40 UTC | 8h 45m |
| 2026-05-05 | FDB430 | CCJ → DXB | May 5, 06:40 UTC | May 5, 06:50 UTC | 10m |
| 2026-05-05 | FDB2JQ | DXB → CCJ | May 5, 00:40 UTC | May 5, 00:55 UTC | 15m |
| 2026-05-04 | FDB7UE | EVN → DXB | May 4, 10:30 UTC | May 4, 14:30 UTC | 4h 0m |
| 2026-05-04 | FDB59G | DXB → EVN | May 4, 04:34 UTC | May 4, 08:30 UTC | 3h 55m |
| 2026-05-03 | FDB2YF | SVX → DXB | May 3, 12:55 UTC | May 3, 17:54 UTC | 5h 0m |
| 2026-05-02 | FDB2YF | SVX → DXB | May 2, 19:20 UTC | May 3, 17:54 UTC | 22h 34m |
| 2026-05-02 | FDB5CH | DXB → SVX | May 2, 19:10 UTC | May 3, 12:55 UTC | 17h 44m |
| 2026-05-02 | FDB5CH | DXB → SVX | May 2, 16:25 UTC | May 3, 12:55 UTC | 20h 29m |
| 2026-05-02 | FDB5CH | DXB → SVX | May 2, 14:30 UTC | May 3, 12:55 UTC | 22h 24m |
| 2026-05-02 | FDB1134 | KTM → DXB | May 2, 03:25 UTC | May 2, 07:40 UTC | 4h 15m |
| 2026-05-02 | FDB1133 | DXB → KTM | May 2, 00:25 UTC | May 2, 01:55 UTC | 1h 30m |
| 2026-05-01 | FDB1133 | DXB → KTM | May 1, 22:20 UTC | May 1, 22:45 UTC | 25m |
| 2026-05-01 | FDB4TA | ZAG → DXB | May 1, 12:35 UTC | May 1, 18:05 UTC | 5h 30m |
| 2026-05-01 | FDB4MA | DXB → ZAG | May 1, 04:30 UTC | May 1, 10:45 UTC | 6h 15m |
| 2026-04-30 | FDB9JZ | GYD → DXB | Apr 30, 22:40 UTC | Apr 30, 23:10 UTC | 30m |
| 2026-04-30 | FDB733 | DXB → GYD | Apr 30, 11:55 UTC | Apr 30, 12:20 UTC | 25m |
| 2026-04-30 | FDB312 | KBL → DXB | Apr 30, 02:30 UTC | Apr 30, 07:30 UTC | 5h 0m |
| 2026-04-30 | FDB311 | DXB → KBL | Apr 30, 00:25 UTC | Apr 30, 00:50 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-FMO page for operator, model, and routing details .