sensors Mode-S transponder
896530
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-FMJ · BOEING 737 MAX 8
- Hex
- 896530
- Octal
- 42262460
- Decimal
- 9,004,336
- Country
- AE
- Tail
- A6-FMJ
- Type
- B38M
- Flights observed
- 159
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- Jul 26, 21:35 UTC
Last known position
Country allocation
The ICAO 24-bit address 896530 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 |
|---|---|---|---|
| FDB444 | Fly Dubai | 5 | 2026-07-21 |
| FDB34Q | - | 5 | 2026-07-17 |
| FDB2WK | - | 5 | 2026-06-18 |
| FDB9UR | Fly Dubai | 4 | 2026-05-17 |
| FDB746 | - | 4 | 2026-07-17 |
| FDB4CE | Fly Dubai | 4 | 2026-07-22 |
| FDB14Q | Fly Dubai | 4 | 2026-07-22 |
| FDB1212 | Fly Dubai | 4 | 2026-05-09 |
| FDB1134 | - | 4 | 2026-06-21 |
| FDB71T | - | 3 | 2026-06-18 |
| FDB443 | Fly Dubai | 3 | 2026-07-20 |
| FDB2PJ | - | 3 | 2026-06-17 |
| FDB1QV | Fly Dubai | 3 | 2026-06-17 |
| FDB1211 | Fly Dubai | 3 | 2026-05-09 |
| FDB1133 | Fly Dubai | 3 | 2026-06-21 |
| FDB8762 | - | 2 | 2026-07-19 |
| FDB8761 | - | 2 | 2026-07-19 |
| FDB870 | Fly Dubai | 2 | 2026-04-15 |
| FDB868 | Fly Dubai | 2 | 2026-06-16 |
| FDB864 | Fly Dubai | 2 | 2026-05-26 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | FDB1334 | DMK → DXB | Jul 26, 17:10 UTC | Jul 26, 21:35 UTC | 4h 25m |
| 2026-07-26 | FDB1333 | DXB → DMK | Jul 26, 00:30 UTC | Jul 26, 06:35 UTC | 6h 6m |
| 2026-07-25 | FDB1574 | BGY → DXB | Jul 25, 11:55 UTC | Jul 25, 18:40 UTC | 6h 45m |
| 2026-07-25 | FDB64C | DXB → BGY | Jul 25, 03:00 UTC | Jul 25, 09:30 UTC | 6h 30m |
| 2026-07-24 | FDB9JQ | KRK → DXB | Jul 24, 17:40 UTC | Jul 24, 23:40 UTC | 6h 0m |
| 2026-07-24 | FDB5ZL | DXB → KRK | Jul 24, 10:35 UTC | Jul 24, 16:05 UTC | 5h 30m |
| 2026-07-23 | FDB1687 | ZNZ → DAR | Jul 23, 07:10 UTC | Jul 23, 23:40 UTC | 16h 30m |
| 2026-07-22 | FDB4CE | BEG → DXB | Jul 22, 21:50 UTC | Jul 23, 03:35 UTC | 5h 45m |
| 2026-07-22 | FDB14Q | DXB → BEG | Jul 22, 15:15 UTC | Jul 22, 20:20 UTC | 5h 5m |
| 2026-07-22 | FDB7UE | EVN → DXB | Jul 22, 03:45 UTC | Jul 22, 12:05 UTC | 8h 20m |
| 2026-07-21 | FDB209 | - | Jul 21, 10:35 UTC | Jul 21, 11:30 UTC | 55m |
| 2026-07-21 | FDB444 | LKO → DXB | Jul 21, 07:40 UTC | Jul 21, 08:05 UTC | 25m |
| 2026-07-21 | FDB444 | LKO → DXB | Jul 21, 05:45 UTC | Jul 21, 06:35 UTC | 50m |
| 2026-07-20 | FDB443 | DXB → LKO | Jul 20, 23:35 UTC | Jul 21, 02:45 UTC | 3h 10m |
| 2026-07-20 | FDB3PR | - | Jul 20, 13:15 UTC | Jul 20, 18:35 UTC | 5h 20m |
| 2026-07-20 | FDB5WH | DXB → SOF | Jul 20, 07:50 UTC | Jul 20, 12:05 UTC | 4h 15m |
| 2026-07-19 | FDB8762 | - | Jul 19, 17:05 UTC | Jul 19, 22:40 UTC | 5h 35m |
| 2026-07-19 | FDB8761 | - | Jul 19, 12:25 UTC | Jul 19, 15:25 UTC | 3h 0m |
| 2026-07-18 | FDB8762 | - | Jul 18, 18:30 UTC | Jul 19, 00:15 UTC | 5h 45m |
| 2026-07-17 | FDB8761 | - | Jul 17, 21:55 UTC | Jul 18, 15:10 UTC | 17h 16m |
| 2026-07-17 | FDB746 | - | Jul 17, 12:45 UTC | Jul 17, 17:20 UTC | 4h 35m |
| 2026-07-17 | FDB34Q | - | Jul 17, 05:39 UTC | Jul 17, 10:35 UTC | 4h 55m |
| 2026-06-25 | FDB617 | - | Jun 25, 07:00 UTC | Jun 25, 15:34 UTC | 8h 35m |
| 2026-06-24 | FDB1074 | - | Jun 24, 10:10 UTC | Jun 24, 11:09 UTC | 1h 0m |
| 2026-06-24 | FDB1074 | - | Jun 24, 08:14 UTC | Jun 24, 08:35 UTC | 20m |
| 2026-06-24 | FDB1073 | - | Jun 24, 03:15 UTC | Jun 24, 06:15 UTC | 3h 0m |
| 2026-06-23 | FDB23L | - | Jun 23, 02:24 UTC | Jun 23, 12:35 UTC | 10h 10m |
| 2026-06-22 | FDB1114 | - | Jun 22, 09:19 UTC | Jun 22, 16:29 UTC | 7h 10m |
| 2026-06-21 | FDB4CE | - | Jun 21, 21:44 UTC | Jun 22, 03:14 UTC | 5h 30m |
| 2026-06-21 | FDB14Q | - | Jun 21, 15:15 UTC | Jun 21, 20:24 UTC | 5h 10m |
| 2026-06-21 | FDB1134 | - | Jun 21, 07:25 UTC | Jun 21, 07:34 UTC | 10m |
| 2026-06-21 | FDB1134 | - | Jun 21, 03:34 UTC | Jun 21, 05:10 UTC | 1h 35m |
| 2026-06-21 | FDB1133 | DXB → KTM | Jun 21, 00:19 UTC | Jun 21, 01:59 UTC | 1h 40m |
| 2026-06-20 | FDB1133 | DXB → KTM | Jun 20, 22:20 UTC | Jun 20, 22:39 UTC | 20m |
| 2026-06-20 | FDB2RG | OTP → DXB | Jun 20, 12:34 UTC | Jun 20, 17:44 UTC | 5h 10m |
| 2026-06-20 | FDB3PL | - | Jun 20, 06:29 UTC | Jun 20, 10:55 UTC | 4h 25m |
| 2026-06-19 | FDB1KS | BEG → DXB | Jun 19, 12:19 UTC | Jun 19, 14:29 UTC | 2h 10m |
| 2026-06-19 | FDB9YD | DXB → BEG | Jun 19, 05:40 UTC | Jun 19, 10:54 UTC | 5h 15m |
| 2026-06-18 | FDB71T | - | Jun 18, 12:55 UTC | Jun 18, 13:20 UTC | 25m |
| 2026-06-18 | FDB2WK | - | Jun 18, 07:45 UTC | Jun 18, 11:25 UTC | 3h 40m |
| 2026-06-17 | FDB1QV | EVN → DXB | Jun 17, 11:30 UTC | Jun 17, 11:40 UTC | 10m |
| 2026-06-17 | FDB2PJ | - | Jun 17, 09:30 UTC | Jun 17, 09:45 UTC | 15m |
| 2026-06-16 | FDB868 | DMM → DXB | Jun 16, 17:00 UTC | Jun 16, 17:40 UTC | 40m |
| 2026-06-13 | FDB444 | - | Jun 13, 04:20 UTC | Jun 13, 05:15 UTC | 55m |
| 2026-06-12 | FDB1114 | DAM → DXB | Jun 12, 00:15 UTC | Jun 12, 16:25 UTC | 16h 11m |
| 2026-06-11 | FDB445 | DXB → BOM | Jun 11, 09:50 UTC | Jun 11, 22:45 UTC | 12h 55m |
| 2026-06-08 | FDB746 | TIA → DXB | Jun 8, 12:15 UTC | Jun 8, 16:25 UTC | 4h 10m |
| 2026-06-07 | FDB34Q | DXB → TIA | Jun 7, 14:05 UTC | Jun 8, 09:30 UTC | 19h 25m |
| 2026-06-07 | FDB34Q | DXB → TIA | Jun 7, 13:40 UTC | Jun 8, 09:30 UTC | 19h 50m |
| 2026-06-07 | FDB759 | DXB → AYT | Jun 7, 08:50 UTC | Jun 7, 12:00 UTC | 3h 10m |
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-FMJ page for operator, model, and routing details .