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
- 111
- Distinct callsigns
- 20
- Country
- FJ
- Last broadcast
- 1h 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 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| FJI393 | - | 19 | 2026-07-13 |
| FJI881 | - | 12 | 2026-07-08 |
| FJI392 | - | 12 | 2026-07-14 |
| FJI880 | - | 11 | 2026-07-07 |
| FJI921 | - | 8 | 2026-07-12 |
| FJI411 | - | 7 | 2026-06-23 |
| FJI410 | - | 7 | 2026-06-28 |
| FJI351 | - | 7 | 2026-06-30 |
| FJI934 | Air Pacific | 6 | 2026-05-30 |
| FJI935 | Air Pacific | 5 | 2026-05-30 |
| FJI350 | - | 4 | 2026-06-27 |
| FJI920 | - | 3 | 2026-07-06 |
| FJI911 | Air Pacific | 2 | 2026-06-02 |
| FJI910 | Air Pacific | 2 | 2026-06-03 |
| FJI870 | - | 1 | 2026-07-11 |
| FJI2805 | Air Pacific | 1 | 2026-06-14 |
| FJI2804 | Air Pacific | 1 | 2026-06-14 |
| FJI2802 | Air Pacific | 1 | 2026-06-05 |
| FJI2801 | Air Pacific | 1 | 2026-06-05 |
| FJI1350 | - | 1 | 2026-06-11 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | FJI392 | - | Jul 14, 08:35 UTC | Jul 14, 09:45 UTC | 1h 10m |
| 2026-07-13 | FJI393 | BNE → HKG | Jul 13, 02:45 UTC | Jul 13, 21:30 UTC | 18h 45m |
| 2026-07-12 | FJI921 | - | Jul 12, 06:10 UTC | Jul 13, 00:25 UTC | 18h 15m |
| 2026-07-11 | FJI870 | BNE → SFO | Jul 11, 02:25 UTC | Jul 11, 21:35 UTC | 19h 10m |
| 2026-07-10 | FJI392 | HKG → BNE | Jul 10, 08:40 UTC | Jul 11, 00:40 UTC | 16h 0m |
| 2026-07-09 | FJI393 | - | Jul 9, 21:30 UTC | Jul 9, 21:45 UTC | 15m |
| 2026-07-09 | FJI393 | - | Jul 9, 02:20 UTC | Jul 9, 20:35 UTC | 18h 15m |
| 2026-07-08 | FJI881 | YVR → BNE | Jul 8, 06:20 UTC | Jul 9, 00:40 UTC | 18h 20m |
| 2026-07-07 | FJI880 | - | Jul 7, 23:55 UTC | Jul 8, 00:25 UTC | 30m |
| 2026-07-06 | FJI920 | - | Jul 6, 02:35 UTC | Jul 6, 04:10 UTC | 1h 35m |
| 2026-07-05 | FJI881 | - | Jul 5, 06:35 UTC | Jul 6, 00:35 UTC | 18h 0m |
| 2026-07-04 | FJI880 | - | Jul 4, 17:10 UTC | Jul 4, 22:40 UTC | 5h 30m |
| 2026-07-04 | FJI880 | BNE → YVR | Jul 4, 02:10 UTC | Jul 4, 22:40 UTC | 20h 30m |
| 2026-07-03 | FJI881 | YVR → BNE | Jul 3, 06:25 UTC | Jul 4, 00:30 UTC | 18h 5m |
| 2026-07-02 | FJI880 | - | Jul 2, 02:25 UTC | Jul 2, 21:45 UTC | 19h 20m |
| 2026-07-01 | FJI921 | NRT → BNE | Jul 1, 08:40 UTC | Jul 2, 00:30 UTC | 15h 50m |
| 2026-06-30 | FJI351 | - | Jun 30, 20:35 UTC | Jun 30, 21:15 UTC | 40m |
| 2026-06-28 | FJI410 | - | Jun 28, 02:29 UTC | Jun 28, 02:54 UTC | 25m |
| 2026-06-27 | FJI350 | NRT → AKL | Jun 27, 09:09 UTC | Jun 28, 00:15 UTC | 15h 5m |
| 2026-06-26 | FJI351 | - | Jun 26, 20:24 UTC | Jun 26, 21:04 UTC | 40m |
| 2026-06-23 | FJI410 | - | Jun 23, 02:29 UTC | Jun 23, 02:55 UTC | 25m |
| 2026-06-23 | FJI411 | - | Jun 23, 00:04 UTC | Jun 23, 00:39 UTC | 35m |
| 2026-06-22 | FJI920 | BNE → AKL | Jun 22, 02:19 UTC | Jun 23, 00:39 UTC | 22h 20m |
| 2026-06-21 | FJI921 | - | Jun 21, 06:04 UTC | Jun 22, 00:29 UTC | 18h 25m |
| 2026-06-21 | FJI881 | YVR → BNE | Jun 21, 05:40 UTC | Jun 22, 00:29 UTC | 18h 50m |
| 2026-06-20 | FJI880 | BNE → YVR | Jun 20, 02:19 UTC | Jun 20, 20:55 UTC | 18h 35m |
| 2026-06-19 | FJI921 | - | Jun 19, 06:04 UTC | Jun 20, 00:34 UTC | 18h 30m |
| 2026-06-19 | FJI881 | - | Jun 19, 05:49 UTC | Jun 20, 00:34 UTC | 18h 45m |
| 2026-06-18 | FJI880 | BNE → YVR | Jun 18, 02:25 UTC | Jun 18, 21:45 UTC | 19h 20m |
| 2026-06-17 | FJI350 | NRT → BNE | Jun 17, 08:35 UTC | Jun 18, 00:40 UTC | 16h 5m |
| 2026-06-16 | FJI351 | NAN → NRT | Jun 16, 20:20 UTC | Jun 16, 21:10 UTC | 50m |
| 2026-06-14 | FJI2805 | SLC → NAN | Jun 14, 22:10 UTC | Jun 14, 23:54 UTC | 1h 45m |
| 2026-06-14 | FJI2804 | NAN → SLC | Jun 14, 18:15 UTC | Jun 14, 19:50 UTC | 1h 35m |
| 2026-06-13 | FJI350 | NRT → NAN | Jun 13, 08:50 UTC | Jun 13, 09:15 UTC | 25m |
| 2026-06-12 | FJI351 | NAN → NRT | Jun 12, 20:10 UTC | Jun 12, 21:10 UTC | 1h 0m |
| 2026-06-11 | FJI1350 | - | Jun 11, 08:55 UTC | Jun 11, 09:35 UTC | 40m |
| 2026-06-09 | FJI351 | NAN → NRT | Jun 9, 20:25 UTC | Jun 9, 21:05 UTC | 40m |
| 2026-06-08 | FJI410 | AKL → NAN | Jun 8, 02:30 UTC | Jun 8, 02:55 UTC | 25m |
| 2026-06-07 | FJI411 | NAN → AKL | Jun 7, 09:10 UTC | Jun 8, 00:45 UTC | 15h 35m |
| 2026-06-06 | FJI393 | NAN → HKG | Jun 6, 02:25 UTC | Jun 6, 21:40 UTC | 19h 15m |
| 2026-06-05 | FJI2801 | SLC → NAN | Jun 5, 06:05 UTC | Jun 6, 00:45 UTC | 18h 40m |
| 2026-06-05 | FJI2802 | SFO → SLC | Jun 5, 01:00 UTC | Jun 5, 02:35 UTC | 1h 35m |
| 2026-06-03 | FJI910 | SYD → NAN | Jun 3, 03:40 UTC | Jun 3, 20:40 UTC | 17h 0m |
| 2026-06-02 | FJI911 | NAN → SYD | Jun 2, 08:45 UTC | Jun 3, 01:55 UTC | 17h 10m |
| 2026-06-01 | FJI393 | NAN → HKG | Jun 1, 02:10 UTC | Jun 1, 21:40 UTC | 19h 30m |
| 2026-05-31 | FJI392 | HKG → NAN | May 31, 08:55 UTC | Jun 1, 00:25 UTC | 15h 30m |
| 2026-05-30 | FJI934 | MEL → NAN | May 30, 03:40 UTC | May 30, 21:20 UTC | 17h 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 |
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 .