sensors Mode-S transponder
896604
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-FKN · BOEING 737 MAX 8
- Hex
- 896604
- Octal
- 42263004
- Decimal
- 9,004,548
- Country
- AE
- Tail
- A6-FKN
- Type
- B38M
- Flights observed
- 60
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 896604 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 |
|---|---|---|---|
| FDB1212 | Fly Dubai | 6 | 2026-05-23 |
| FDB884 | Fly Dubai | 3 | 2026-05-15 |
| FDB3JE | Fly Dubai | 3 | 2026-05-10 |
| FDB176 | Fly Dubai | 3 | 2026-05-25 |
| FDB175 | Fly Dubai | 3 | 2026-05-25 |
| FDB1211 | Fly Dubai | 3 | 2026-05-23 |
| FDB883 | Fly Dubai | 2 | 2026-05-15 |
| FDB808 | Fly Dubai | 2 | 2026-05-23 |
| FDB71T | Fly Dubai | 2 | 2026-05-28 |
| FDB5PG | Fly Dubai | 2 | 2026-05-09 |
| FDB5JA | Fly Dubai | 2 | 2026-04-18 |
| FDB569 | Fly Dubai | 2 | 2026-05-22 |
| FDB308 | Fly Dubai | 2 | 2026-05-03 |
| FDB307 | Fly Dubai | 2 | 2026-05-03 |
| FDB1626 | Fly Dubai | 2 | 2026-05-30 |
| FDB948 | Fly Dubai | 1 | 2026-05-08 |
| FDB871 | - | 1 | 2026-05-16 |
| FDB870 | Fly Dubai | 1 | 2026-05-05 |
| FDB869 | Fly Dubai | 1 | 2026-05-05 |
| FDB827 | Fly Dubai | 1 | 2026-05-04 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-01 | FDB7UE | EVN → DXB | Jun 1, 11:20 UTC | Jun 1, 12:05 UTC | 45m |
| 2026-05-31 | FDB2PE | BEY → DXB | May 31, 15:45 UTC | Jun 1, 06:35 UTC | 14h 50m |
| 2026-05-30 | FDB1626 | TLV → DXB | May 30, 17:05 UTC | May 31, 11:25 UTC | 18h 20m |
| 2026-05-30 | FDB1626 | TLV → DXB | May 30, 16:45 UTC | May 31, 11:25 UTC | 18h 40m |
| 2026-05-30 | FDB1625 | DXB → TLV | May 30, 15:10 UTC | May 30, 15:20 UTC | 10m |
| 2026-05-29 | FDB1QV | EVN → DXB | May 29, 06:30 UTC | May 29, 14:50 UTC | 8h 20m |
| 2026-05-28 | FDB71T | TBS → DXB | May 28, 15:30 UTC | May 29, 14:50 UTC | 23h 20m |
| 2026-05-28 | FDB71T | TBS → DXB | May 28, 12:35 UTC | May 29, 06:40 UTC | 18h 5m |
| 2026-05-27 | FDB1636 | TLV → DXB | May 27, 15:45 UTC | May 28, 07:40 UTC | 15h 55m |
| 2026-05-26 | FDB1635 | DXB → TLV | May 26, 16:00 UTC | May 27, 12:05 UTC | 20h 5m |
| 2026-05-25 | FDB176 | HBE → DXB | May 25, 21:19 UTC | May 26, 16:00 UTC | 18h 40m |
| 2026-05-25 | FDB175 | DXB → HBE | May 25, 18:20 UTC | May 25, 18:55 UTC | 35m |
| 2026-05-23 | FDB808 | JED → DXB | May 23, 21:05 UTC | May 24, 14:05 UTC | 17h 0m |
| 2026-05-23 | FDB808 | JED → DXB | May 23, 16:25 UTC | May 24, 14:05 UTC | 21h 40m |
| 2026-05-23 | FDB1212 | TLV → DXB | May 23, 12:50 UTC | May 23, 21:45 UTC | 8h 55m |
| 2026-05-23 | FDB1212 | TLV → DXB | May 23, 11:00 UTC | May 23, 11:20 UTC | 20m |
| 2026-05-23 | FDB1211 | DXB → TLV | May 23, 06:35 UTC | May 23, 07:25 UTC | 50m |
| 2026-05-22 | FDB570 | CMB → DXB | May 22, 20:50 UTC | May 22, 22:45 UTC | 1h 55m |
| 2026-05-22 | FDB569 | DXB → CMB | May 22, 05:30 UTC | May 22, 18:50 UTC | 13h 20m |
| 2026-05-21 | FDB1212 | TLV → DXB | May 21, 13:05 UTC | May 22, 05:35 UTC | 16h 30m |
| 2026-05-21 | FDB1212 | TLV → DXB | May 21, 11:15 UTC | May 21, 11:35 UTC | 20m |
| 2026-05-21 | FDB1211 | DXB → TLV | May 21, 09:15 UTC | May 21, 09:40 UTC | 25m |
| 2026-05-20 | FDB7KL | AMM → DXB | May 20, 03:20 UTC | May 20, 22:15 UTC | 18h 56m |
| 2026-05-19 | FDB1212 | TLV → DXB | May 19, 13:55 UTC | May 20, 03:55 UTC | 14h 0m |
| 2026-05-19 | FDB1212 | TLV → DXB | May 19, 12:15 UTC | May 19, 12:30 UTC | 15m |
| 2026-05-19 | FDB1211 | DXB → TLV | May 19, 10:05 UTC | May 19, 10:45 UTC | 40m |
| 2026-05-18 | FDB569 | DXB → CMB | May 18, 16:45 UTC | May 19, 08:10 UTC | 15h 24m |
| 2026-05-16 | FDB871 | - | May 16, 19:00 UTC | May 16, 23:35 UTC | 4h 35m |
| 2026-05-15 | FDB176 | HBE → DXB | May 15, 21:20 UTC | May 16, 00:10 UTC | 2h 50m |
| 2026-05-15 | FDB175 | DXB → HBE | May 15, 16:45 UTC | May 15, 19:20 UTC | 2h 35m |
| 2026-05-15 | FDB884 | DMM → DXB | May 15, 05:50 UTC | May 15, 06:50 UTC | 1h 0m |
| 2026-05-15 | FDB883 | DXB → DMM | May 15, 04:00 UTC | May 15, 04:10 UTC | 10m |
| 2026-05-14 | FDB7AQ | DXB → ISU | May 14, 06:10 UTC | May 14, 13:40 UTC | 7h 30m |
| 2026-05-13 | FDB807 | DXB → JED | May 13, 15:55 UTC | May 13, 21:55 UTC | 6h 0m |
| 2026-05-10 | FDB3JE | MRV → DXB | May 10, 16:10 UTC | May 10, 19:54 UTC | 3h 45m |
| 2026-05-09 | FDB5PG | DXB → MRV | May 9, 17:49 UTC | May 9, 22:30 UTC | 4h 40m |
| 2026-05-08 | FDB948 | AQI → DXB | May 8, 11:25 UTC | May 8, 12:00 UTC | 35m |
| 2026-05-07 | FDB884 | DMM → DXB | May 7, 07:25 UTC | May 7, 08:05 UTC | 40m |
| 2026-05-06 | FDB3JE | MRV → DXB | May 6, 17:00 UTC | May 7, 05:15 UTC | 12h 14m |
| 2026-05-05 | FDB3JE | MRV → DXB | May 5, 20:40 UTC | May 6, 18:15 UTC | 21h 34m |
| 2026-05-05 | FDB5PG | DXB → MRV | May 5, 18:30 UTC | May 6, 17:00 UTC | 22h 30m |
| 2026-05-05 | FDB870 | DMM → DXB | May 5, 12:10 UTC | May 5, 13:55 UTC | 1h 45m |
| 2026-05-05 | FDB869 | DXB → DMM | May 5, 08:40 UTC | May 5, 09:45 UTC | 1h 5m |
| 2026-05-04 | FDB827 | DXB → MED | May 4, 18:40 UTC | May 5, 00:00 UTC | 5h 20m |
| 2026-05-03 | FDB308 | KBL → DXB | May 3, 09:55 UTC | May 3, 15:05 UTC | 5h 10m |
| 2026-05-03 | FDB307 | DXB → KBL | May 3, 07:55 UTC | May 3, 08:20 UTC | 25m |
| 2026-05-02 | FDB176 | HBE → DXB | May 2, 21:25 UTC | May 3, 00:25 UTC | 3h 0m |
| 2026-05-02 | FDB175 | DXB → HBE | May 2, 15:35 UTC | May 2, 19:35 UTC | 4h 0m |
| 2026-05-02 | FDB884 | DMM → DXB | May 2, 05:40 UTC | May 2, 06:35 UTC | 55m |
| 2026-05-02 | FDB883 | DXB → DMM | May 2, 03:10 UTC | May 2, 04:05 UTC | 55m |
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-FKN page for operator, model, and routing details .