sensors Mode-S transponder
C8806F
ICAO 24-bit transponder address · allocated to Fiji
Currently assigned to DQ-FJW · AIRBUS A-330-300
- Hex
- C8806F
- Octal
- 62100157
- Decimal
- 13,140,079
- Country
- FJ
- Tail
- DQ-FJW
- Type
- A333
- Flights observed
- 128
- Distinct callsigns
- 9
- Country
- FJ
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address C8806F falls within the block assigned to Fiji (FJ) by ICAO Annex 10, Volume III. Every aircraft registered in Fiji 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 9 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| FJI411 | - | 29 | 2026-07-10 |
| FJI870 | - | 27 | 2026-07-08 |
| FJI871 | - | 25 | 2026-07-09 |
| FJI392 | - | 17 | 2026-07-12 |
| FJI393 | - | 15 | 2026-07-11 |
| FJI410 | - | 12 | 2026-07-13 |
| FJI935 | Air Pacific | 1 | 2026-06-04 |
| FJI934 | Air Pacific | 1 | 2026-06-05 |
| FJI363 | Air Pacific | 1 | 2026-06-03 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | FJI410 | - | Jul 13, 02:25 UTC | Jul 13, 02:50 UTC | 25m |
| 2026-07-12 | FJI392 | - | Jul 12, 08:40 UTC | Jul 13, 00:45 UTC | 16h 5m |
| 2026-07-11 | FJI393 | - | Jul 11, 21:30 UTC | Jul 11, 21:45 UTC | 15m |
| 2026-07-11 | FJI393 | - | Jul 11, 02:55 UTC | Jul 11, 20:40 UTC | 17h 45m |
| 2026-07-10 | FJI411 | - | Jul 10, 03:55 UTC | Jul 11, 01:15 UTC | 21h 20m |
| 2026-07-09 | FJI871 | SFO → AKL | Jul 9, 10:35 UTC | Jul 10, 02:15 UTC | 15h 40m |
| 2026-07-08 | FJI870 | - | Jul 8, 02:20 UTC | Jul 8, 20:40 UTC | 18h 20m |
| 2026-07-07 | FJI392 | - | Jul 7, 09:30 UTC | Jul 8, 00:40 UTC | 15h 10m |
| 2026-07-07 | FJI392 | - | Jul 7, 08:20 UTC | Jul 7, 08:40 UTC | 20m |
| 2026-07-06 | FJI393 | - | Jul 6, 20:35 UTC | Jul 6, 21:55 UTC | 1h 20m |
| 2026-07-06 | FJI393 | - | Jul 6, 02:25 UTC | Jul 6, 21:55 UTC | 19h 30m |
| 2026-07-05 | FJI392 | - | Jul 5, 09:40 UTC | Jul 6, 00:35 UTC | 14h 55m |
| 2026-07-05 | FJI392 | - | Jul 5, 08:35 UTC | Jul 5, 08:45 UTC | 10m |
| 2026-07-04 | FJI393 | - | Jul 4, 20:50 UTC | Jul 4, 22:05 UTC | 1h 15m |
| 2026-07-04 | FJI393 | - | Jul 4, 03:00 UTC | Jul 4, 22:05 UTC | 19h 5m |
| 2026-07-04 | FJI411 | - | Jul 4, 00:30 UTC | Jul 4, 01:00 UTC | 30m |
| 2026-07-03 | FJI411 | - | Jul 3, 02:15 UTC | Jul 4, 01:00 UTC | 22h 45m |
| 2026-07-02 | FJI411 | - | Jul 2, 07:00 UTC | Jul 3, 00:45 UTC | 17h 45m |
| 2026-07-01 | FJI870 | - | Jul 1, 02:15 UTC | Jul 1, 20:40 UTC | 18h 25m |
| 2026-06-30 | FJI392 | - | Jun 30, 09:30 UTC | Jul 1, 00:30 UTC | 15h 0m |
| 2026-06-30 | FJI392 | - | Jun 30, 08:30 UTC | Jun 30, 08:50 UTC | 20m |
| 2026-06-29 | FJI393 | - | Jun 29, 02:45 UTC | Jun 29, 21:30 UTC | 18h 45m |
| 2026-06-29 | FJI411 | - | Jun 29, 00:39 UTC | Jun 29, 01:00 UTC | 20m |
| 2026-06-28 | FJI392 | - | Jun 28, 09:50 UTC | Jun 28, 13:29 UTC | 3h 40m |
| 2026-06-27 | FJI393 | - | Jun 27, 21:29 UTC | Jun 27, 22:45 UTC | 1h 15m |
| 2026-06-27 | FJI393 | - | Jun 27, 02:45 UTC | Jun 27, 22:45 UTC | 20h 0m |
| 2026-06-27 | FJI411 | - | Jun 27, 00:34 UTC | Jun 27, 01:09 UTC | 35m |
| 2026-06-26 | FJI411 | AKL → AKL | Jun 26, 02:24 UTC | Jun 27, 01:09 UTC | 22h 45m |
| 2026-06-25 | FJI871 | - | Jun 25, 06:44 UTC | Jun 26, 00:50 UTC | 18h 5m |
| 2026-06-24 | FJI870 | - | Jun 24, 19:55 UTC | Jun 24, 20:20 UTC | 25m |
| 2026-06-24 | FJI410 | - | Jun 24, 02:45 UTC | Jun 24, 03:15 UTC | 30m |
| 2026-06-23 | FJI392 | - | Jun 23, 09:45 UTC | Jun 24, 00:49 UTC | 15h 5m |
| 2026-06-23 | FJI392 | - | Jun 23, 08:39 UTC | Jun 23, 08:54 UTC | 15m |
| 2026-06-22 | FJI393 | AKL → HKG | Jun 22, 02:25 UTC | Jun 22, 21:19 UTC | 18h 55m |
| 2026-06-21 | FJI392 | - | Jun 21, 09:40 UTC | Jun 22, 00:44 UTC | 15h 5m |
| 2026-06-21 | FJI392 | - | Jun 21, 08:35 UTC | Jun 21, 08:49 UTC | 15m |
| 2026-06-20 | FJI393 | - | Jun 20, 20:55 UTC | Jun 20, 22:10 UTC | 1h 15m |
| 2026-06-20 | FJI393 | - | Jun 20, 02:40 UTC | Jun 20, 22:10 UTC | 19h 30m |
| 2026-06-20 | FJI411 | - | Jun 20, 00:49 UTC | Jun 20, 01:09 UTC | 20m |
| 2026-06-19 | FJI410 | - | Jun 19, 02:39 UTC | Jun 19, 02:54 UTC | 15m |
| 2026-06-18 | FJI871 | - | Jun 18, 07:05 UTC | Jun 19, 00:45 UTC | 17h 39m |
| 2026-06-17 | FJI870 | - | Jun 17, 19:55 UTC | Jun 17, 20:25 UTC | 30m |
| 2026-06-17 | FJI410 | - | Jun 17, 02:25 UTC | Jun 17, 02:45 UTC | 20m |
| 2026-06-17 | FJI411 | - | Jun 17, 00:20 UTC | Jun 17, 00:45 UTC | 25m |
| 2026-06-16 | FJI392 | - | Jun 16, 08:49 UTC | Jun 16, 09:10 UTC | 20m |
| 2026-06-15 | FJI393 | NAN → HKG | Jun 15, 02:20 UTC | Jun 15, 21:35 UTC | 19h 15m |
| 2026-06-14 | FJI392 | HKG → NAN | Jun 14, 08:45 UTC | Jun 15, 00:20 UTC | 15h 34m |
| 2026-06-13 | FJI393 | NAN → HKG | Jun 13, 02:10 UTC | Jun 13, 21:35 UTC | 19h 24m |
| 2026-06-12 | FJI411 | - | Jun 12, 23:45 UTC | Jun 13, 00:20 UTC | 35m |
| 2026-06-12 | FJI411 | - | Jun 12, 02:15 UTC | Jun 13, 00:20 UTC | 22h 5m |
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 DQ-FJW page for operator, model, and routing details .