sensors Mode-S transponder
896533
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-FML · BOEING 737 MAX 8
- Hex
- 896533
- Octal
- 42262463
- Decimal
- 9,004,339
- Country
- AE
- Tail
- A6-FML
- Type
- B38M
- Flights observed
- 103
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 6h ago
Last known position
Country allocation
The ICAO 24-bit address 896533 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 |
|---|---|---|---|
| FDB7ML | Fly Dubai | 4 | 2026-05-10 |
| FDB52X | Fly Dubai | 4 | 2026-04-15 |
| FDB1BM | - | 4 | 2026-04-16 |
| FDB1550 | Fly Dubai | 4 | 2026-05-03 |
| FDB7KL | Fly Dubai | 3 | 2026-04-26 |
| FDB579 | Fly Dubai | 3 | 2026-05-19 |
| FDB443 | Fly Dubai | 3 | 2026-05-06 |
| FDB3PL | Fly Dubai | 3 | 2026-04-18 |
| FDB1549 | Fly Dubai | 3 | 2026-05-03 |
| FDB143 | Fly Dubai | 3 | 2026-04-28 |
| FDB1133 | Fly Dubai | 3 | 2026-05-06 |
| FDB64C | Fly Dubai | 2 | 2026-05-25 |
| FDB580 | Fly Dubai | 2 | 2026-05-20 |
| FDB4CE | Fly Dubai | 2 | 2026-05-08 |
| FDB444 | Fly Dubai | 2 | 2026-05-28 |
| FDB3UM | Fly Dubai | 2 | 2026-05-26 |
| FDB2MF | Fly Dubai | 2 | 2026-05-21 |
| FDB2DC | Fly Dubai | 2 | 2026-04-30 |
| FDB1NU | Fly Dubai | 2 | 2026-04-26 |
| FDB14Q | Fly Dubai | 2 | 2026-05-08 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | FDB47B | OLB → DXB | May 30, 12:10 UTC | May 30, 14:10 UTC | 2h 0m |
| 2026-05-28 | FDB444 | LKO → DXB | May 28, 03:15 UTC | May 28, 04:20 UTC | 1h 5m |
| 2026-05-27 | FDB93Q | NAP → DXB | May 27, 11:30 UTC | May 28, 01:00 UTC | 13h 30m |
| 2026-05-26 | FDB3UM | DXB → NAP | May 26, 15:20 UTC | May 27, 09:15 UTC | 17h 55m |
| 2026-05-26 | FDB3UM | DXB → NAP | May 26, 12:50 UTC | May 27, 09:15 UTC | 20h 25m |
| 2026-05-26 | FDB1574 | BGY → DXB | May 26, 11:39 UTC | May 27, 09:15 UTC | 21h 35m |
| 2026-05-25 | FDB64C | DXB → BGY | May 25, 14:50 UTC | May 26, 09:19 UTC | 18h 30m |
| 2026-05-25 | FDB64C | DXB → BGY | May 25, 13:10 UTC | May 26, 09:19 UTC | 20h 9m |
| 2026-05-24 | FDB719 | DXB → DBV | May 24, 10:45 UTC | May 24, 12:00 UTC | 1h 15m |
| 2026-05-23 | FDB1502 | CTA → DXB | May 23, 05:40 UTC | May 23, 10:25 UTC | 4h 45m |
| 2026-05-21 | FDB2MF | IST → DXB | May 21, 17:00 UTC | May 22, 08:55 UTC | 15h 55m |
| 2026-05-20 | FDB580 | CMB → DXB | May 20, 04:20 UTC | May 20, 21:25 UTC | 17h 6m |
| 2026-05-19 | FDB579 | DXB → CMB | May 19, 23:50 UTC | May 20, 01:50 UTC | 2h 0m |
| 2026-05-19 | FDB1126 | TLV → DXB | May 19, 15:20 UTC | May 19, 15:30 UTC | 10m |
| 2026-05-19 | FDB1125 | DXB → TLV | May 19, 13:40 UTC | May 19, 13:45 UTC | 5m |
| 2026-05-19 | FDB5JD | MCX → DXB | May 19, 01:10 UTC | May 19, 04:35 UTC | 3h 25m |
| 2026-05-18 | FDB4XC | DXB → MCX | May 18, 20:45 UTC | May 18, 22:45 UTC | 2h 0m |
| 2026-05-18 | FDB864 | DMM → DXB | May 18, 12:40 UTC | May 18, 13:30 UTC | 50m |
| 2026-05-18 | FDB863 | DXB → DMM | May 18, 11:05 UTC | May 18, 11:15 UTC | 10m |
| 2026-05-17 | FDB3QB | DXB → NBO | May 17, 15:10 UTC | May 17, 15:25 UTC | 15m |
| 2026-05-16 | FDB580 | CMB → DXB | May 16, 04:20 UTC | May 16, 19:40 UTC | 15h 21m |
| 2026-05-15 | FDB579 | DXB → CMB | May 15, 11:35 UTC | May 16, 01:50 UTC | 14h 14m |
| 2026-05-10 | FDB7ML | RMO → DXB | May 10, 12:15 UTC | May 11, 07:50 UTC | 19h 35m |
| 2026-05-08 | FDB4CE | BEG → DXB | May 8, 22:00 UTC | May 9, 00:35 UTC | 2h 35m |
| 2026-05-08 | FDB14Q | DXB → BEG | May 8, 19:30 UTC | May 8, 20:45 UTC | 1h 15m |
| 2026-05-07 | FDB876 | TIF → DXB | May 7, 16:15 UTC | May 7, 16:50 UTC | 35m |
| 2026-05-06 | FDB443 | DXB → LKO | May 6, 16:10 UTC | May 7, 00:45 UTC | 8h 34m |
| 2026-05-06 | FDB443 | DXB → LKO | May 6, 03:30 UTC | May 7, 00:45 UTC | 21h 14m |
| 2026-05-06 | FDB1133 | DXB → KTM | May 6, 01:25 UTC | May 6, 02:05 UTC | 40m |
| 2026-05-05 | FDB444 | LKO → DXB | May 5, 06:40 UTC | May 5, 07:00 UTC | 20m |
| 2026-05-05 | FDB443 | DXB → LKO | May 5, 01:00 UTC | May 5, 01:50 UTC | 50m |
| 2026-05-03 | FDB4CE | BEG → DXB | May 3, 21:50 UTC | May 4, 03:24 UTC | 5h 35m |
| 2026-05-03 | FDB14Q | DXB → BEG | May 3, 14:35 UTC | May 3, 20:15 UTC | 5h 40m |
| 2026-05-03 | FDB1550 | TLV → DXB | May 3, 09:50 UTC | May 3, 11:15 UTC | 1h 25m |
| 2026-05-03 | FDB1550 | TLV → DXB | May 3, 08:00 UTC | May 3, 08:15 UTC | 15m |
| 2026-05-03 | FDB1549 | DXB → TLV | May 3, 05:55 UTC | May 3, 06:15 UTC | 20m |
| 2026-05-02 | FDB2MF | IST → DXB | May 2, 17:00 UTC | May 3, 03:40 UTC | 10h 39m |
| 2026-05-02 | FDB4GP | DXB → IST | May 2, 10:25 UTC | May 2, 11:25 UTC | 1h 0m |
| 2026-05-02 | FDB1ZA | SPX → DXB | May 2, 01:10 UTC | May 2, 02:20 UTC | 1h 10m |
| 2026-05-01 | FDB4RM | DXB → SPX | May 1, 17:40 UTC | May 1, 21:25 UTC | 3h 45m |
| 2026-05-01 | FDB620 | EBB → DXB | May 1, 13:35 UTC | May 1, 13:45 UTC | 10m |
| 2026-05-01 | FDB619 | DXB → EBB | May 1, 01:35 UTC | May 1, 02:00 UTC | 25m |
| 2026-04-30 | FDB1126 | TLV → DXB | Apr 30, 15:15 UTC | Apr 30, 18:30 UTC | 3h 15m |
| 2026-04-30 | FDB1125 | DXB → TLV | Apr 30, 10:00 UTC | Apr 30, 11:10 UTC | 1h 10m |
| 2026-04-30 | FDB2DC | LHE → DXB | Apr 30, 03:20 UTC | Apr 30, 03:45 UTC | 25m |
| 2026-04-29 | FDB2DC | LHE → DXB | Apr 29, 22:45 UTC | Apr 30, 01:20 UTC | 2h 34m |
| 2026-04-29 | FDB7SK | DXB → LHE | Apr 29, 20:40 UTC | Apr 29, 21:00 UTC | 20m |
| 2026-04-29 | FDB1289 | DXB → MBA | Apr 29, 05:35 UTC | Apr 29, 16:45 UTC | 11h 11m |
| 2026-04-28 | FDB143 | DXB → AMM | Apr 28, 14:30 UTC | Apr 28, 22:45 UTC | 8h 15m |
| 2026-04-28 | FDB884 | DMM → DXB | Apr 28, 05:40 UTC | Apr 28, 06:40 UTC | 1h 0m |
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-FML page for operator, model, and routing details .