sensors Mode-S transponder
89648B
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-FGF · BOEING 737-800
- Hex
- 89648B
- Octal
- 42262213
- Decimal
- 9,004,171
- Country
- AE
- Tail
- A6-FGF
- Type
- B738
- Flights observed
- 35
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 11h ago
Last known position
Country allocation
The ICAO 24-bit address 89648B 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 |
|---|---|---|---|
| FDB868 | Fly Dubai | 3 | 2026-06-01 |
| FDB834 | Fly Dubai | 3 | 2026-05-18 |
| FDB3HP | Fly Dubai | 2 | 2026-05-29 |
| FDB1550 | Fly Dubai | 2 | 2026-06-01 |
| FDB1082 | Fly Dubai | 2 | 2026-06-03 |
| FDB9RQ | Fly Dubai | 1 | 2026-05-03 |
| FDB94F | Fly Dubai | 1 | 2026-05-02 |
| FDB884 | Fly Dubai | 1 | 2026-05-24 |
| FDB864 | Fly Dubai | 1 | 2026-05-13 |
| FDB863 | Fly Dubai | 1 | 2026-05-13 |
| FDB833 | Fly Dubai | 1 | 2026-04-15 |
| FDB7WA | Fly Dubai | 1 | 2026-04-27 |
| FDB7HD | Fly Dubai | 1 | 2026-04-25 |
| FDB760 | Fly Dubai | 1 | 2026-05-31 |
| FDB759 | Fly Dubai | 1 | 2026-05-30 |
| FDB5JN | Fly Dubai | 1 | 2026-05-02 |
| FDB59J | Fly Dubai | 1 | 2026-05-28 |
| FDB4RM | Fly Dubai | 1 | 2026-05-30 |
| FDB4PD | Fly Dubai | 1 | 2026-04-20 |
| FDB446 | Fly Dubai | 1 | 2026-05-23 |
Recent flights last 35
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-03 | FDB1082 | TLV → DXB | Jun 3, 15:00 UTC | Jun 4, 10:25 UTC | 19h 25m |
| 2026-06-03 | FDB1082 | TLV → DXB | Jun 3, 13:10 UTC | Jun 3, 13:30 UTC | 20m |
| 2026-06-02 | FDB1081 | DXB → TLV | Jun 2, 16:55 UTC | Jun 3, 11:25 UTC | 18h 30m |
| 2026-06-02 | FDB1126 | TLV → DXB | Jun 2, 15:05 UTC | Jun 3, 11:25 UTC | 20h 20m |
| 2026-06-01 | FDB868 | DMM → DXB | Jun 1, 16:45 UTC | Jun 1, 17:20 UTC | 35m |
| 2026-06-01 | FDB1550 | TLV → DXB | Jun 1, 10:20 UTC | Jun 1, 10:55 UTC | 35m |
| 2026-06-01 | FDB1550 | TLV → DXB | Jun 1, 08:25 UTC | Jun 1, 08:40 UTC | 15m |
| 2026-06-01 | FDB1549 | DXB → TLV | Jun 1, 06:30 UTC | Jun 1, 06:50 UTC | 20m |
| 2026-05-31 | FDB760 | AYT → DXB | May 31, 13:50 UTC | Jun 1, 04:35 UTC | 14h 45m |
| 2026-05-30 | FDB759 | DXB → AYT | May 30, 23:15 UTC | May 31, 12:05 UTC | 12h 50m |
| 2026-05-30 | FDB4RM | DXB → SPX | May 30, 12:20 UTC | May 30, 21:25 UTC | 9h 5m |
| 2026-05-29 | FDB3HP | BSR → DXB | May 29, 16:05 UTC | May 29, 16:40 UTC | 35m |
| 2026-05-28 | FDB59J | BAH → DXB | May 28, 15:50 UTC | May 28, 16:45 UTC | 55m |
| 2026-05-26 | FDB868 | DMM → DXB | May 26, 16:59 UTC | May 26, 18:05 UTC | 1h 5m |
| 2026-05-24 | FDB3HP | BSR → DXB | May 24, 14:50 UTC | May 24, 21:45 UTC | 6h 55m |
| 2026-05-24 | FDB884 | DMM → DXB | May 24, 05:45 UTC | May 24, 06:40 UTC | 55m |
| 2026-05-23 | FDB446 | BOM → DXB | May 23, 00:20 UTC | May 23, 00:45 UTC | 25m |
| 2026-05-22 | FDB445 | DXB → BOM | May 22, 22:05 UTC | May 22, 22:45 UTC | 40m |
| 2026-05-18 | FDB834 | JED → DXB | May 18, 08:01 UTC | May 18, 12:45 UTC | 4h 45m |
| 2026-05-17 | FDB868 | DMM → DXB | May 17, 17:10 UTC | May 17, 18:05 UTC | 55m |
| 2026-05-13 | FDB864 | DMM → DXB | May 13, 12:40 UTC | May 13, 13:45 UTC | 1h 5m |
| 2026-05-13 | FDB863 | DXB → DMM | May 13, 10:40 UTC | May 13, 11:05 UTC | 25m |
| 2026-05-03 | FDB9RQ | DOH → DXB | May 3, 07:00 UTC | May 3, 07:45 UTC | 45m |
| 2026-05-03 | FDB1 | DXB → DOH | May 3, 05:30 UTC | May 3, 05:45 UTC | 15m |
| 2026-05-02 | FDB5JN | MCT → DXB | May 2, 09:45 UTC | May 2, 10:15 UTC | 30m |
| 2026-05-02 | FDB94F | DXB → MCT | May 2, 07:30 UTC | May 2, 07:55 UTC | 25m |
| 2026-04-27 | FDB7WA | MCT → DXB | Apr 27, 18:30 UTC | Apr 27, 19:00 UTC | 30m |
| 2026-04-27 | FDB3PM | DXB → MCT | Apr 27, 16:00 UTC | Apr 27, 16:20 UTC | 20m |
| 2026-04-25 | FDB3UF | MCT → DXB | Apr 25, 06:00 UTC | Apr 25, 06:20 UTC | 20m |
| 2026-04-25 | FDB7HD | DXB → MCT | Apr 25, 03:45 UTC | Apr 25, 04:10 UTC | 25m |
| 2026-04-20 | FDB4PD | MCT → DXB | Apr 20, 13:20 UTC | Apr 20, 13:45 UTC | 25m |
| 2026-04-20 | FDB2AP | DXB → MCT | Apr 20, 11:00 UTC | Apr 20, 11:25 UTC | 25m |
| 2026-04-15 | FDB834 | JED → DXB | Apr 15, 13:01 UTC | Apr 15, 13:40 UTC | 40m |
| 2026-04-15 | FDB834 | JED → DXB | Apr 15, 12:40 UTC | Apr 15, 12:55 UTC | 15m |
| 2026-04-15 | FDB833 | DXB → JED | Apr 15, 07:25 UTC | Apr 15, 08:25 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-FGF page for operator, model, and routing details .