sensors Mode-S transponder
896512
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-FMG · BOEING 737 MAX 8
- Hex
- 896512
- Octal
- 42262422
- Decimal
- 9,004,306
- Country
- AE
- Tail
- A6-FMG
- Type
- B38M
- Flights observed
- 115
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 3h ago
Last known position
Country allocation
The ICAO 24-bit address 896512 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 |
|---|---|---|---|
| FDB539 | Fly Dubai | 4 | 2026-04-29 |
| FDB441 | Fly Dubai | 4 | 2026-04-26 |
| FDB1082 | Fly Dubai | 4 | 2026-04-23 |
| FDB7AF | Fly Dubai | 3 | 2026-04-27 |
| FDB5WB | Fly Dubai | 3 | 2026-05-21 |
| FDB579 | Fly Dubai | 3 | 2026-04-17 |
| FDB540 | Fly Dubai | 3 | 2026-04-29 |
| FDB4CE | Fly Dubai | 3 | 2026-05-21 |
| FDB3UM | Fly Dubai | 3 | 2026-05-28 |
| FDB3PL | Fly Dubai | 3 | 2026-05-02 |
| FDB2RG | Fly Dubai | 3 | 2026-05-02 |
| FDB15L | Fly Dubai | 3 | 2026-04-15 |
| FDB833 | Fly Dubai | 2 | 2026-04-13 |
| FDB830 | Fly Dubai | 2 | 2026-04-16 |
| FDB829 | Fly Dubai | 2 | 2026-04-16 |
| FDB811 | Fly Dubai | 2 | 2026-04-17 |
| FDB7XZ | Fly Dubai | 2 | 2026-05-08 |
| FDB7ML | Fly Dubai | 2 | 2026-05-24 |
| FDB580 | Fly Dubai | 2 | 2026-04-17 |
| FDB3PR | Fly Dubai | 2 | 2026-05-04 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | FDB446 | BOM → DXB | May 30, 00:20 UTC | May 30, 00:45 UTC | 25m |
| 2026-05-29 | FDB93Q | NAP → DXB | May 29, 11:45 UTC | May 29, 22:25 UTC | 10h 40m |
| 2026-05-28 | FDB3UM | DXB → NAP | May 28, 15:50 UTC | May 29, 09:20 UTC | 17h 30m |
| 2026-05-28 | FDB3UM | DXB → NAP | May 28, 12:35 UTC | May 29, 09:20 UTC | 20h 45m |
| 2026-05-28 | FDB3UM | DXB → NAP | May 28, 12:05 UTC | May 29, 09:20 UTC | 21h 15m |
| 2026-05-27 | FDB3XU | KRK → DXB | May 27, 10:55 UTC | May 28, 06:30 UTC | 19h 35m |
| 2026-05-26 | FDB4GA | DXB → KRK | May 26, 15:14 UTC | May 27, 09:05 UTC | 17h 51m |
| 2026-05-26 | FDB5PS | TBS → DXB | May 26, 02:15 UTC | May 26, 05:59 UTC | 3h 45m |
| 2026-05-25 | FDB746 | TIA → DXB | May 25, 12:10 UTC | May 26, 00:19 UTC | 12h 9m |
| 2026-05-24 | FDB34Q | DXB → TIA | May 24, 15:55 UTC | May 25, 10:10 UTC | 18h 15m |
| 2026-05-24 | FDB7ML | RMO → DXB | May 24, 12:35 UTC | May 25, 10:10 UTC | 21h 35m |
| 2026-05-24 | FDB7ML | RMO → DXB | May 24, 12:00 UTC | May 25, 10:10 UTC | 22h 10m |
| 2026-05-23 | FDB1QS | PRG → DXB | May 23, 19:35 UTC | May 24, 09:55 UTC | 14h 20m |
| 2026-05-22 | FDB3CF | DXB → PRG | May 22, 01:20 UTC | May 22, 17:35 UTC | 16h 15m |
| 2026-05-21 | FDB3CF | DXB → PRG | May 21, 20:10 UTC | May 22, 17:35 UTC | 21h 25m |
| 2026-05-21 | FDB5WB | BEY → DXB | May 21, 14:35 UTC | May 22, 12:20 UTC | 21h 45m |
| 2026-05-21 | FDB5WB | BEY → DXB | May 21, 12:35 UTC | May 22, 12:20 UTC | 23h 45m |
| 2026-05-21 | FDB5WB | BEY → DXB | May 21, 02:35 UTC | May 22, 01:20 UTC | 22h 45m |
| 2026-05-21 | FDB4CE | BEG → DXB | May 21, 02:15 UTC | May 21, 20:15 UTC | 18h 0m |
| 2026-05-20 | FDB4CE | BEG → DXB | May 20, 22:35 UTC | May 21, 20:15 UTC | 21h 40m |
| 2026-05-20 | FDB4CE | BEG → DXB | May 20, 21:50 UTC | May 21, 20:15 UTC | 22h 25m |
| 2026-05-20 | FDB14Q | DXB → BEG | May 20, 18:50 UTC | May 20, 20:10 UTC | 1h 20m |
| 2026-05-19 | FDB4TB | DXB → VKO | May 19, 14:10 UTC | May 19, 14:35 UTC | 25m |
| 2026-05-16 | FDB1303 | DXB → NQZ | May 16, 17:15 UTC | May 16, 17:35 UTC | 20m |
| 2026-05-16 | FDB910 | JED → DXB | May 16, 11:01 UTC | May 16, 11:35 UTC | 35m |
| 2026-05-13 | FDB1126 | TLV → DXB | May 13, 15:10 UTC | May 13, 18:25 UTC | 3h 15m |
| 2026-05-13 | FDB1125 | DXB → TLV | May 13, 12:45 UTC | May 13, 13:00 UTC | 15m |
| 2026-05-12 | FDB1212 | TLV → DXB | May 12, 10:40 UTC | May 12, 10:55 UTC | 15m |
| 2026-05-12 | FDB1211 | DXB → TLV | May 12, 08:40 UTC | May 12, 08:55 UTC | 15m |
| 2026-05-11 | FDB1BM | - | May 11, 12:25 UTC | May 11, 17:15 UTC | 4h 51m |
| 2026-05-11 | FDB52X | DXB → SJJ | May 11, 04:50 UTC | May 11, 10:20 UTC | 5h 30m |
| 2026-05-10 | FDB4TA | ZAG → DXB | May 10, 12:44 UTC | May 10, 17:49 UTC | 5h 5m |
| 2026-05-10 | FDB4MA | DXB → ZAG | May 10, 08:15 UTC | May 10, 11:05 UTC | 2h 50m |
| 2026-05-08 | FDB7XZ | BGW → DXB | May 8, 12:04 UTC | May 9, 01:15 UTC | 13h 10m |
| 2026-05-07 | FDB7XZ | BGW → DXB | May 7, 21:25 UTC | May 8, 12:49 UTC | 15h 25m |
| 2026-05-04 | FDB3PR | SOF → DXB | May 4, 12:45 UTC | May 4, 20:30 UTC | 7h 46m |
| 2026-05-04 | FDB5WH | DXB → SOF | May 4, 05:45 UTC | May 4, 10:45 UTC | 5h 0m |
| 2026-05-03 | FDB3PR | SOF → DXB | May 3, 12:50 UTC | May 3, 17:45 UTC | 4h 55m |
| 2026-05-02 | FDB2RG | OTP → DXB | May 2, 17:20 UTC | May 3, 10:50 UTC | 17h 29m |
| 2026-05-02 | FDB2RG | OTP → DXB | May 2, 15:05 UTC | May 3, 10:50 UTC | 19h 44m |
| 2026-05-02 | FDB3PL | DXB → OTP | May 2, 06:55 UTC | May 2, 12:25 UTC | 5h 30m |
| 2026-05-01 | FDB1KS | BEG → DXB | May 1, 12:10 UTC | May 1, 17:20 UTC | 5h 10m |
| 2026-05-01 | FDB9YD | DXB → BEG | May 1, 04:15 UTC | May 1, 10:20 UTC | 6h 5m |
| 2026-04-30 | FDB9QG | KHI → DXB | Apr 30, 20:20 UTC | Apr 30, 20:45 UTC | 25m |
| 2026-04-30 | FDB43F | DXB → KHI | Apr 30, 15:40 UTC | Apr 30, 16:00 UTC | 20m |
| 2026-04-30 | FDB870 | DMM → DXB | Apr 30, 10:25 UTC | Apr 30, 11:35 UTC | 1h 10m |
| 2026-04-30 | FDB869 | DXB → DMM | Apr 30, 07:40 UTC | Apr 30, 08:40 UTC | 1h 0m |
| 2026-04-30 | FDB732 | ASB → DXB | Apr 30, 03:30 UTC | Apr 30, 03:50 UTC | 20m |
| 2026-04-29 | FDB731 | DXB → ASB | Apr 29, 18:10 UTC | Apr 29, 18:35 UTC | 25m |
| 2026-04-29 | FDB540 | KTM → DXB | Apr 29, 15:55 UTC | Apr 29, 16:20 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-FMG page for operator, model, and routing details .