sensors Mode-S transponder
C88018
ICAO 24-bit transponder address · allocated to Fiji
Currently assigned to DQ-FJT · AIRBUS A-330-200
- Hex
- C88018
- Octal
- 62100030
- Decimal
- 13,139,992
- Country
- FJ
- Tail
- DQ-FJT
- Type
- A332
- Flights observed
- 65
- Distinct callsigns
- 14
- Country
- FJ
- Last broadcast
- 4h ago
Last known position
Country allocation
The ICAO 24-bit address C88018 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 14 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| FJI393 | Air Pacific | 14 | 2026-05-25 |
| FJI392 | Air Pacific | 9 | 2026-05-26 |
| FJI881 | Air Pacific | 7 | 2026-05-17 |
| FJI934 | Air Pacific | 6 | 2026-05-30 |
| FJI935 | Air Pacific | 5 | 2026-05-30 |
| FJI880 | Air Pacific | 5 | 2026-05-16 |
| FJI411 | Air Pacific | 5 | 2026-05-02 |
| FJI921 | Air Pacific | 4 | 2026-04-26 |
| FJI410 | Air Pacific | 4 | 2026-05-25 |
| FJI351 | Air Pacific | 2 | 2026-05-08 |
| FJI920 | - | 1 | 2026-04-13 |
| FJI911 | Air Pacific | 1 | 2026-05-19 |
| FJI910 | Air Pacific | 1 | 2026-05-20 |
| FJI350 | Air Pacific | 1 | 2026-04-15 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | FJI934 | MEL → NAN | May 30, 03:40 UTC | May 30, 05:20 UTC | 1h 40m |
| 2026-05-30 | FJI935 | NAN → MEL | May 30, 00:00 UTC | May 30, 01:40 UTC | 1h 40m |
| 2026-05-29 | FJI934 | MEL → NAN | May 29, 04:05 UTC | May 30, 01:40 UTC | 21h 35m |
| 2026-05-29 | FJI934 | MEL → NAN | May 29, 03:55 UTC | May 30, 01:40 UTC | 21h 45m |
| 2026-05-28 | FJI935 | NAN → MEL | May 28, 23:40 UTC | May 29, 01:35 UTC | 1h 55m |
| 2026-05-26 | FJI392 | HKG → NAN | May 26, 09:35 UTC | May 26, 10:44 UTC | 1h 10m |
| 2026-05-25 | FJI393 | NAN → HKG | May 25, 21:45 UTC | May 25, 23:04 UTC | 1h 20m |
| 2026-05-25 | FJI410 | AKL → NAN | May 25, 02:15 UTC | May 25, 02:35 UTC | 20m |
| 2026-05-24 | FJI392 | HKG → NAN | May 24, 08:30 UTC | May 24, 09:40 UTC | 1h 10m |
| 2026-05-24 | FJI393 | NAN → HKG | May 24, 04:00 UTC | May 24, 05:20 UTC | 1h 20m |
| 2026-05-23 | FJI393 | NAN → HKG | May 23, 08:40 UTC | May 24, 05:20 UTC | 20h 41m |
| 2026-05-22 | FJI934 | MEL → NAN | May 22, 04:50 UTC | May 22, 21:05 UTC | 16h 15m |
| 2026-05-21 | FJI935 | NAN → MEL | May 21, 11:45 UTC | May 22, 02:05 UTC | 14h 20m |
| 2026-05-20 | FJI910 | SYD → NAN | May 20, 03:40 UTC | May 20, 04:15 UTC | 35m |
| 2026-05-19 | FJI911 | NAN → SYD | May 19, 08:45 UTC | May 20, 01:35 UTC | 16h 50m |
| 2026-05-18 | FJI393 | NAN → HKG | May 18, 20:30 UTC | May 18, 21:45 UTC | 1h 15m |
| 2026-05-17 | FJI881 | YVR → NAN | May 17, 05:30 UTC | May 17, 11:01 UTC | 5h 30m |
| 2026-05-16 | FJI880 | NAN → YVR | May 16, 02:05 UTC | May 16, 21:45 UTC | 19h 40m |
| 2026-05-15 | FJI392 | HKG → NAN | May 15, 09:30 UTC | May 16, 00:25 UTC | 14h 54m |
| 2026-05-14 | FJI393 | NAN → HKG | May 14, 20:35 UTC | May 14, 22:10 UTC | 1h 35m |
| 2026-05-14 | FJI393 | NAN → HKG | May 14, 02:50 UTC | May 14, 22:10 UTC | 19h 20m |
| 2026-05-13 | FJI881 | YVR → NAN | May 13, 06:05 UTC | May 14, 00:50 UTC | 18h 45m |
| 2026-05-13 | FJI881 | YVR → NAN | May 13, 05:30 UTC | May 14, 00:50 UTC | 19h 20m |
| 2026-05-12 | FJI880 | NAN → YVR | May 12, 15:15 UTC | May 12, 20:55 UTC | 5h 40m |
| 2026-05-10 | FJI934 | MEL → NAN | May 10, 04:15 UTC | May 10, 05:55 UTC | 1h 40m |
| 2026-05-09 | FJI935 | NAN → MEL | May 9, 08:45 UTC | May 10, 02:14 UTC | 17h 30m |
| 2026-05-08 | FJI351 | NAN → NRT | May 8, 20:30 UTC | May 8, 21:10 UTC | 40m |
| 2026-05-07 | FJI410 | AKL → NAN | May 7, 02:35 UTC | May 7, 03:00 UTC | 25m |
| 2026-05-06 | FJI881 | YVR → NAN | May 6, 06:05 UTC | May 7, 00:25 UTC | 18h 20m |
| 2026-05-06 | FJI881 | YVR → NAN | May 6, 05:40 UTC | May 7, 00:25 UTC | 18h 44m |
| 2026-05-05 | FJI880 | NAN → YVR | May 5, 15:05 UTC | May 5, 20:30 UTC | 5h 25m |
| 2026-05-04 | FJI410 | AKL → NAN | May 4, 02:30 UTC | May 4, 02:54 UTC | 25m |
| 2026-05-03 | FJI392 | HKG → NAN | May 3, 09:20 UTC | May 4, 00:25 UTC | 15h 5m |
| 2026-05-02 | FJI393 | NAN → HKG | May 2, 20:45 UTC | May 2, 22:05 UTC | 1h 20m |
| 2026-05-02 | FJI393 | NAN → HKG | May 2, 02:15 UTC | May 2, 22:05 UTC | 19h 50m |
| 2026-05-02 | FJI411 | NAN → AKL | May 2, 00:05 UTC | May 2, 00:40 UTC | 35m |
| 2026-05-01 | FJI934 | MEL → NAN | May 1, 04:10 UTC | May 2, 00:40 UTC | 20h 30m |
| 2026-04-30 | FJI935 | NAN → MEL | Apr 30, 11:25 UTC | May 1, 02:00 UTC | 14h 35m |
| 2026-04-28 | FJI392 | HKG → NAN | Apr 28, 08:35 UTC | Apr 28, 09:35 UTC | 1h 0m |
| 2026-04-27 | FJI393 | NAN → HKG | Apr 27, 02:15 UTC | Apr 27, 22:00 UTC | 19h 45m |
| 2026-04-26 | FJI921 | NAN → BNE | Apr 26, 06:05 UTC | Apr 27, 00:20 UTC | 18h 15m |
| 2026-04-26 | FJI881 | YVR → NAN | Apr 26, 05:35 UTC | Apr 27, 00:20 UTC | 18h 45m |
| 2026-04-25 | FJI880 | NAN → YVR | Apr 25, 03:55 UTC | Apr 25, 21:35 UTC | 17h 40m |
| 2026-04-24 | FJI392 | HKG → NAN | Apr 24, 09:45 UTC | Apr 25, 01:35 UTC | 15h 50m |
| 2026-04-23 | FJI393 | NAN → HKG | Apr 23, 20:45 UTC | Apr 23, 22:20 UTC | 1h 35m |
| 2026-04-23 | FJI393 | NAN → HKG | Apr 23, 02:25 UTC | Apr 23, 22:20 UTC | 19h 55m |
| 2026-04-22 | FJI921 | NAN → BNE | Apr 22, 06:05 UTC | Apr 23, 00:40 UTC | 18h 35m |
| 2026-04-22 | FJI881 | YVR → NAN | Apr 22, 05:35 UTC | Apr 23, 00:40 UTC | 19h 5m |
| 2026-04-21 | FJI880 | NAN → YVR | Apr 21, 02:20 UTC | Apr 21, 21:55 UTC | 19h 35m |
| 2026-04-21 | FJI411 | NAN → AKL | Apr 21, 00:05 UTC | Apr 21, 00:35 UTC | 30m |
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-FJT page for operator, model, and routing details .