sensors Mode-S transponder
896608
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-FKR · BOEING 737 MAX 8
- Hex
- 896608
- Octal
- 42263010
- Decimal
- 9,004,552
- Country
- AE
- Tail
- A6-FKR
- Type
- B38M
- Flights observed
- 80
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 6h ago
Last known position
Country allocation
The ICAO 24-bit address 896608 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 |
|---|---|---|---|
| FDB64X | - | 4 | 2026-05-06 |
| FDB9RF | Fly Dubai | 3 | 2026-04-30 |
| FDB75L | Fly Dubai | 3 | 2026-04-28 |
| FDB574 | Fly Dubai | 3 | 2026-05-14 |
| FDB454 | Fly Dubai | 3 | 2026-04-30 |
| FDB16T | Fly Dubai | 3 | 2026-06-01 |
| FDB15L | Fly Dubai | 3 | 2026-04-28 |
| FDB884 | Fly Dubai | 2 | 2026-05-28 |
| FDB871 | - | 2 | 2026-04-13 |
| FDB870 | Fly Dubai | 2 | 2026-05-18 |
| FDB864 | Fly Dubai | 2 | 2026-05-21 |
| FDB863 | Fly Dubai | 2 | 2026-05-05 |
| FDB7KL | Fly Dubai | 2 | 2026-05-17 |
| FDB501 | Fly Dubai | 2 | 2026-05-01 |
| FDB3TH | Fly Dubai | 2 | 2026-04-17 |
| FDB3JE | Fly Dubai | 2 | 2026-05-20 |
| FDB1AR | - | 2 | 2026-04-19 |
| FDB176 | Fly Dubai | 2 | 2026-05-30 |
| FDB175 | Fly Dubai | 2 | 2026-05-30 |
| FDB1626 | Fly Dubai | 2 | 2026-05-28 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-01 | FDB828 | MED → DXB | Jun 1, 18:30 UTC | Jun 2, 13:25 UTC | 18h 55m |
| 2026-06-01 | FDB16T | BAH → DXB | Jun 1, 14:05 UTC | Jun 1, 14:55 UTC | 50m |
| 2026-05-31 | FDB184 | HBE → DXB | May 31, 18:15 UTC | May 31, 20:45 UTC | 2h 30m |
| 2026-05-30 | FDB183 | DXB → HBE | May 30, 23:50 UTC | May 31, 16:50 UTC | 17h 0m |
| 2026-05-30 | FDB176 | HBE → DXB | May 30, 21:20 UTC | May 31, 16:50 UTC | 19h 30m |
| 2026-05-30 | FDB175 | DXB → HBE | May 30, 08:50 UTC | May 30, 19:10 UTC | 10h 20m |
| 2026-05-29 | FDB807 | DXB → JED | May 29, 16:40 UTC | May 30, 06:20 UTC | 13h 40m |
| 2026-05-28 | FDB1626 | TLV → DXB | May 28, 18:35 UTC | May 29, 17:00 UTC | 22h 25m |
| 2026-05-28 | FDB1626 | TLV → DXB | May 28, 16:45 UTC | May 28, 19:15 UTC | 2h 30m |
| 2026-05-28 | FDB884 | DMM → DXB | May 28, 05:50 UTC | May 28, 06:50 UTC | 1h 0m |
| 2026-05-26 | FDB1BH | TBS → DXB | May 26, 10:39 UTC | May 27, 02:24 UTC | 15h 45m |
| 2026-05-25 | FDB4XN | DXB → TBS | May 25, 14:10 UTC | May 26, 09:15 UTC | 19h 5m |
| 2026-05-25 | FDB884 | DMM → DXB | May 25, 05:50 UTC | May 25, 06:50 UTC | 1h 0m |
| 2026-05-23 | FDB830 | JED → DXB | May 23, 04:05 UTC | May 23, 16:35 UTC | 12h 30m |
| 2026-05-22 | FDB71T | TBS → DXB | May 22, 12:35 UTC | May 23, 06:40 UTC | 18h 4m |
| 2026-05-21 | FDB872 | - | May 21, 19:50 UTC | May 22, 10:35 UTC | 14h 45m |
| 2026-05-21 | FDB864 | DMM → DXB | May 21, 12:50 UTC | May 21, 13:45 UTC | 55m |
| 2026-05-20 | FDB3JE | MRV → DXB | May 20, 16:20 UTC | May 20, 19:40 UTC | 3h 20m |
| 2026-05-19 | FDB3JE | MRV → DXB | May 19, 18:25 UTC | May 20, 17:50 UTC | 23h 26m |
| 2026-05-18 | FDB870 | DMM → DXB | May 18, 10:10 UTC | May 18, 11:10 UTC | 1h 0m |
| 2026-05-17 | FDB7KL | AMM → DXB | May 17, 21:25 UTC | May 17, 22:10 UTC | 45m |
| 2026-05-15 | FDB7KL | AMM → DXB | May 15, 16:25 UTC | May 16, 09:51 UTC | 17h 26m |
| 2026-05-14 | FDB574 | KTM → DXB | May 14, 20:05 UTC | May 15, 16:30 UTC | 20h 24m |
| 2026-05-14 | FDB574 | KTM → DXB | May 14, 18:15 UTC | May 15, 16:30 UTC | 22h 14m |
| 2026-05-14 | FDB574 | KTM → DXB | May 14, 17:55 UTC | May 14, 20:40 UTC | 2h 45m |
| 2026-05-14 | FDB573 | DXB → KTM | May 14, 05:55 UTC | May 14, 15:20 UTC | 9h 25m |
| 2026-05-13 | FDB868 | DMM → DXB | May 13, 16:45 UTC | May 13, 17:50 UTC | 1h 5m |
| 2026-05-13 | FDB867 | DXB → DMM | May 13, 14:15 UTC | May 13, 15:05 UTC | 50m |
| 2026-05-12 | FDB16T | BAH → DXB | May 12, 14:25 UTC | May 12, 15:15 UTC | 50m |
| 2026-05-12 | FDB832 | JED → DXB | May 12, 05:55 UTC | May 12, 06:20 UTC | 25m |
| 2026-05-09 | FDB176 | HBE → DXB | May 9, 21:00 UTC | May 10, 13:49 UTC | 16h 50m |
| 2026-05-09 | FDB175 | DXB → HBE | May 9, 16:20 UTC | May 9, 19:10 UTC | 2h 50m |
| 2026-05-06 | FDB808 | JED → DXB | May 6, 16:35 UTC | May 7, 10:15 UTC | 17h 40m |
| 2026-05-06 | FDB64X | - | May 6, 12:05 UTC | May 7, 10:15 UTC | 22h 10m |
| 2026-05-05 | FDB64X | - | May 5, 16:06 UTC | May 6, 12:40 UTC | 20h 35m |
| 2026-05-05 | FDB64X | - | May 5, 15:01 UTC | May 6, 12:40 UTC | 21h 40m |
| 2026-05-05 | FDB863 | DXB → DMM | May 5, 12:00 UTC | May 5, 13:10 UTC | 1h 10m |
| 2026-05-04 | FDB7ZK | DOH → DXB | May 4, 20:30 UTC | May 4, 21:10 UTC | 40m |
| 2026-05-04 | FDB3YK | DXB → DOH | May 4, 13:40 UTC | May 4, 14:10 UTC | 30m |
| 2026-05-03 | FDB43F | DXB → KHI | May 3, 15:45 UTC | May 3, 20:35 UTC | 4h 50m |
| 2026-05-03 | FDB870 | DMM → DXB | May 3, 10:10 UTC | May 3, 11:05 UTC | 55m |
| 2026-05-03 | FDB869 | DXB → DMM | May 3, 07:40 UTC | May 3, 08:35 UTC | 55m |
| 2026-05-02 | FDB502 | DAC → DXB | May 2, 02:20 UTC | May 2, 07:15 UTC | 4h 55m |
| 2026-05-01 | FDB501 | DXB → DAC | May 1, 23:55 UTC | May 2, 00:55 UTC | 1h 0m |
| 2026-05-01 | FDB501 | DXB → DAC | May 1, 20:45 UTC | May 1, 21:05 UTC | 20m |
| 2026-05-01 | FDB864 | DMM → DXB | May 1, 12:40 UTC | May 1, 13:35 UTC | 55m |
| 2026-05-01 | FDB863 | DXB → DMM | May 1, 10:05 UTC | May 1, 11:00 UTC | 55m |
| 2026-04-30 | FDB454 | COK → DXB | Apr 30, 21:05 UTC | May 1, 00:35 UTC | 3h 30m |
| 2026-04-30 | FDB9RF | DXB → COK | Apr 30, 15:50 UTC | Apr 30, 19:15 UTC | 3h 25m |
| 2026-04-29 | FDB8098 | - | Apr 29, 03:24 UTC | Apr 29, 03:49 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-FKR page for operator, model, and routing details .