sensors Mode-S transponder
896513
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-FMF · BOEING 737 MAX 8
- Hex
- 896513
- Octal
- 42262423
- Decimal
- 9,004,307
- Country
- AE
- Tail
- A6-FMF
- Type
- B38M
- Flights observed
- 106
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 23m ago
Last known position
Country allocation
The ICAO 24-bit address 896513 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 |
|---|---|---|---|
| FDB1133 | Fly Dubai | 6 | 2026-05-29 |
| FDB5WH | Fly Dubai | 4 | 2026-04-15 |
| FDB3PR | Fly Dubai | 4 | 2026-05-18 |
| FDB2MF | Fly Dubai | 4 | 2026-04-30 |
| FDB1134 | Fly Dubai | 4 | 2026-05-10 |
| FDB4XC | Fly Dubai | 3 | 2026-05-14 |
| FDB4CE | Fly Dubai | 3 | 2026-05-19 |
| FDB444 | Fly Dubai | 3 | 2026-04-16 |
| FDB905 | Fly Dubai | 2 | 2026-04-23 |
| FDB828 | Fly Dubai | 2 | 2026-05-17 |
| FDB707 | Fly Dubai | 2 | 2026-05-25 |
| FDB619 | Fly Dubai | 2 | 2026-04-25 |
| FDB5JD | Fly Dubai | 2 | 2026-05-05 |
| FDB580 | Fly Dubai | 2 | 2026-04-29 |
| FDB540 | - | 2 | 2026-04-13 |
| FDB539 | - | 2 | 2026-04-13 |
| FDB4XN | Fly Dubai | 2 | 2026-05-28 |
| FDB4GP | Fly Dubai | 2 | 2026-04-30 |
| FDB443 | Fly Dubai | 2 | 2026-04-16 |
| FDB3PL | Fly Dubai | 2 | 2026-05-09 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | FDB1133 | DXB → KTM | May 29, 10:05 UTC | May 30, 00:45 UTC | 14h 40m |
| 2026-05-28 | FDB1075 | DXB → JMK | May 28, 19:00 UTC | May 29, 10:10 UTC | 15h 10m |
| 2026-05-28 | FDB1BH | TBS → DXB | May 28, 09:05 UTC | May 28, 19:00 UTC | 9h 55m |
| 2026-05-28 | FDB4XN | DXB → TBS | May 28, 05:45 UTC | May 28, 06:05 UTC | 20m |
| 2026-05-26 | FDB1078 | CFU → DXB | May 26, 20:50 UTC | May 27, 15:05 UTC | 18h 15m |
| 2026-05-26 | FDB1078 | CFU → DXB | May 26, 18:55 UTC | May 27, 15:05 UTC | 20h 10m |
| 2026-05-26 | FDB573 | DXB → KTM | May 26, 04:35 UTC | May 26, 17:30 UTC | 12h 55m |
| 2026-05-25 | FDB707 | DXB → GYD | May 25, 11:35 UTC | May 26, 00:44 UTC | 13h 9m |
| 2026-05-25 | FDB707 | DXB → GYD | May 25, 01:55 UTC | May 26, 00:44 UTC | 22h 50m |
| 2026-05-24 | FDB1406 | BUD → DXB | May 24, 20:45 UTC | May 25, 12:10 UTC | 15h 25m |
| 2026-05-24 | FDB1405 | DXB → BUD | May 24, 18:35 UTC | May 24, 18:45 UTC | 10m |
| 2026-05-24 | FDB8860 | TIV → DXB | May 24, 05:45 UTC | May 24, 15:40 UTC | 9h 55m |
| 2026-05-23 | FDB8859 | DXB → TIV | May 23, 14:05 UTC | May 23, 14:20 UTC | 15m |
| 2026-05-21 | FDB570 | CMB → DXB | May 21, 23:45 UTC | May 22, 12:30 UTC | 12h 44m |
| 2026-05-21 | FDB569 | DXB → CMB | May 21, 06:40 UTC | May 21, 20:00 UTC | 13h 20m |
| 2026-05-21 | FDB1NU | DXB → OTP | May 21, 04:45 UTC | May 21, 05:05 UTC | 20m |
| 2026-05-20 | FDB1636 | TLV → DXB | May 20, 14:10 UTC | May 20, 14:25 UTC | 15m |
| 2026-05-19 | FDB4CE | BEG → DXB | May 19, 22:00 UTC | May 20, 02:40 UTC | 4h 40m |
| 2026-05-19 | FDB14Q | DXB → BEG | May 19, 15:45 UTC | May 19, 20:40 UTC | 4h 55m |
| 2026-05-18 | FDB3PR | SOF → DXB | May 18, 12:45 UTC | May 18, 16:45 UTC | 4h 0m |
| 2026-05-17 | FDB828 | MED → DXB | May 17, 19:15 UTC | May 18, 11:00 UTC | 15h 45m |
| 2026-05-17 | FDB828 | MED → DXB | May 17, 00:50 UTC | May 17, 23:45 UTC | 22h 55m |
| 2026-05-17 | FDB446 | BOM → DXB | May 17, 00:15 UTC | May 17, 19:20 UTC | 19h 5m |
| 2026-05-16 | FDB445 | DXB → BOM | May 16, 08:41 UTC | May 16, 22:35 UTC | 13h 55m |
| 2026-05-16 | FDB4XN | DXB → TBS | May 16, 06:10 UTC | May 16, 06:31 UTC | 20m |
| 2026-05-14 | FDB4XC | DXB → MCX | May 14, 21:55 UTC | May 14, 22:30 UTC | 35m |
| 2026-05-13 | FDB4XC | DXB → MCX | May 13, 23:10 UTC | May 14, 22:30 UTC | 23h 20m |
| 2026-05-13 | FDB4RM | DXB → SPX | May 13, 17:40 UTC | May 13, 20:55 UTC | 3h 15m |
| 2026-05-13 | FDB842 | RUH → DXB | May 13, 11:30 UTC | May 13, 12:35 UTC | 1h 5m |
| 2026-05-11 | FDB3HP | BSR → DXB | May 11, 15:20 UTC | May 11, 15:40 UTC | 20m |
| 2026-05-10 | FDB1134 | KTM → DXB | May 10, 03:45 UTC | May 10, 06:10 UTC | 2h 25m |
| 2026-05-09 | FDB1133 | DXB → KTM | May 9, 12:25 UTC | May 10, 01:24 UTC | 13h 0m |
| 2026-05-09 | FDB3PL | DXB → OTP | May 9, 10:05 UTC | May 9, 10:50 UTC | 45m |
| 2026-05-05 | FDB1126 | TLV → DXB | May 5, 15:30 UTC | May 5, 15:45 UTC | 15m |
| 2026-05-05 | FDB1125 | DXB → TLV | May 5, 13:15 UTC | May 5, 13:40 UTC | 25m |
| 2026-05-05 | FDB1125 | DXB → TLV | May 5, 10:55 UTC | May 5, 11:05 UTC | 10m |
| 2026-05-05 | FDB5JD | MCX → DXB | May 5, 02:45 UTC | May 5, 07:25 UTC | 4h 40m |
| 2026-05-04 | FDB1550 | TLV → DXB | May 4, 09:55 UTC | May 4, 11:20 UTC | 1h 25m |
| 2026-05-04 | FDB1550 | TLV → DXB | May 4, 08:05 UTC | May 4, 08:20 UTC | 15m |
| 2026-05-04 | FDB1549 | DXB → TLV | May 4, 02:35 UTC | May 4, 03:30 UTC | 55m |
| 2026-05-03 | FDB2RG | OTP → DXB | May 3, 17:10 UTC | May 3, 17:35 UTC | 25m |
| 2026-05-03 | FDB2RG | OTP → DXB | May 3, 12:30 UTC | May 3, 14:50 UTC | 2h 20m |
| 2026-05-02 | FDB3PL | DXB → OTP | May 2, 20:55 UTC | May 3, 11:00 UTC | 14h 4m |
| 2026-05-02 | FDB65E | EBB → DXB | May 2, 09:45 UTC | May 3, 06:40 UTC | 20h 54m |
| 2026-05-02 | FDB4CE | BEG → DXB | May 2, 02:50 UTC | May 2, 03:10 UTC | 20m |
| 2026-05-01 | FDB4CE | BEG → DXB | May 1, 21:50 UTC | May 1, 23:40 UTC | 1h 50m |
| 2026-05-01 | FDB14Q | DXB → BEG | May 1, 13:40 UTC | May 1, 19:45 UTC | 6h 5m |
| 2026-05-01 | FDB847 | DXB → RUH | May 1, 03:55 UTC | May 1, 09:00 UTC | 5h 5m |
| 2026-04-30 | FDB2MF | IST → DXB | Apr 30, 20:40 UTC | Apr 30, 21:45 UTC | 1h 5m |
| 2026-04-30 | FDB4GP | DXB → IST | Apr 30, 09:10 UTC | Apr 30, 10:20 UTC | 1h 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-FMF page for operator, model, and routing details .