sensors Mode-S transponder
C88092
ICAO 24-bit transponder address · allocated to Fiji
Currently assigned to DQ-FAD · BOEING 737 MAX 8
- Hex
- C88092
- Octal
- 62100222
- Decimal
- 13,140,114
- Country
- FJ
- Tail
- DQ-FAD
- Type
- B38M
- Flights observed
- 164
- Distinct callsigns
- 20
- Country
- FJ
- Last broadcast
- Jul 26, 19:35 UTC
Last known position
Country allocation
The ICAO 24-bit address C88092 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 |
|---|---|---|---|
| FJI935 | - | 19 | 2026-07-07 |
| FJI413 | - | 14 | 2026-07-13 |
| FJI914 | Air Pacific | 13 | 2026-07-16 |
| FJI461 | Air Pacific | 12 | 2026-07-22 |
| FJI412 | Air Pacific | 11 | 2026-07-26 |
| FJI460 | Air Pacific | 9 | 2026-07-23 |
| FJI451 | Air Pacific | 9 | 2026-07-19 |
| FJI934 | - | 8 | 2026-07-08 |
| FJI951 | Air Pacific | 7 | 2026-07-24 |
| FJI915 | - | 7 | 2026-07-14 |
| FJI971 | Air Pacific | 5 | 2026-06-25 |
| FJI961 | - | 5 | 2026-06-19 |
| FJI950 | Air Pacific | 5 | 2026-07-24 |
| FJI921 | Air Pacific | 5 | 2026-07-21 |
| FJI920 | Air Pacific | 5 | 2026-07-22 |
| FJI450 | - | 5 | 2026-07-20 |
| FJI981 | Air Pacific | 3 | 2026-07-24 |
| FJI980 | Air Pacific | 3 | 2026-07-25 |
| FJI960 | - | 3 | 2026-06-20 |
| FJI853 | - | 3 | 2026-07-10 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | FJI412 | AKL → NAN | Jul 26, 19:10 UTC | Jul 26, 19:35 UTC | 25m |
| 2026-07-25 | FJI412 | AKL → NAN | Jul 25, 19:15 UTC | Jul 26, 11:10 UTC | 15h 56m |
| 2026-07-25 | FJI980 | OOL → NAN | Jul 25, 02:55 UTC | Jul 25, 11:20 UTC | 8h 25m |
| 2026-07-24 | FJI981 | NAN → OOL | Jul 24, 23:25 UTC | Jul 25, 01:35 UTC | 2h 10m |
| 2026-07-24 | FJI950 | CBR → NAN | Jul 24, 03:25 UTC | Jul 25, 01:35 UTC | 22h 10m |
| 2026-07-24 | FJI951 | NAN → CBR | Jul 24, 01:05 UTC | Jul 24, 02:05 UTC | 1h 0m |
| 2026-07-23 | FJI460 | WLG → NAN | Jul 23, 04:40 UTC | Jul 24, 02:05 UTC | 21h 25m |
| 2026-07-22 | FJI461 | NAN → WLG | Jul 22, 19:20 UTC | Jul 23, 03:10 UTC | 7h 50m |
| 2026-07-22 | FJI920 | BNE → NAN | Jul 22, 02:00 UTC | Jul 22, 02:35 UTC | 35m |
| 2026-07-21 | FJI921 | NAN → BNE | Jul 21, 22:05 UTC | Jul 22, 00:15 UTC | 2h 10m |
| 2026-07-20 | FJI450 | - | Jul 20, 01:35 UTC | Jul 20, 02:15 UTC | 40m |
| 2026-07-19 | FJI451 | NAN → CHC | Jul 19, 04:35 UTC | Jul 19, 23:55 UTC | 19h 20m |
| 2026-07-19 | FJI451 | NAN → CHC | Jul 19, 04:15 UTC | Jul 19, 23:55 UTC | 19h 40m |
| 2026-07-19 | FJI917 | NAN → SYD | Jul 19, 01:50 UTC | Jul 19, 02:30 UTC | 40m |
| 2026-07-18 | FJI460 | WLG → SYD | Jul 18, 04:45 UTC | Jul 19, 02:30 UTC | 21h 45m |
| 2026-07-17 | FJI461 | - | Jul 17, 19:20 UTC | Jul 18, 03:30 UTC | 8h 11m |
| 2026-07-16 | FJI914 | SYD → NAN | Jul 16, 20:35 UTC | Jul 17, 11:04 UTC | 14h 30m |
| 2026-07-15 | FJI914 | SYD → SYD | Jul 15, 20:50 UTC | Jul 16, 12:49 UTC | 16h 0m |
| 2026-07-14 | FJI915 | - | Jul 14, 19:50 UTC | Jul 15, 11:50 UTC | 15h 59m |
| 2026-07-13 | FJI413 | - | Jul 13, 19:20 UTC | Jul 14, 10:40 UTC | 15h 20m |
| 2026-07-13 | FJI980 | - | Jul 13, 03:25 UTC | Jul 13, 10:55 UTC | 7h 30m |
| 2026-07-12 | FJI981 | - | Jul 12, 23:55 UTC | Jul 13, 02:15 UTC | 2h 20m |
| 2026-07-11 | FJI412 | - | Jul 11, 19:20 UTC | Jul 11, 19:45 UTC | 25m |
| 2026-07-11 | FJI980 | OOL → NAN | Jul 11, 02:55 UTC | Jul 11, 10:50 UTC | 7h 55m |
| 2026-07-11 | FJI981 | - | Jul 11, 00:45 UTC | Jul 11, 01:30 UTC | 45m |
| 2026-07-10 | FJI852 | - | Jul 10, 10:00 UTC | Jul 10, 10:20 UTC | 20m |
| 2026-07-10 | FJI853 | - | Jul 10, 06:50 UTC | Jul 10, 07:15 UTC | 25m |
| 2026-07-08 | FJI934 | - | Jul 8, 03:40 UTC | Jul 8, 05:05 UTC | 1h 25m |
| 2026-07-07 | FJI934 | MEL → MEL | Jul 7, 07:25 UTC | Jul 8, 02:10 UTC | 18h 45m |
| 2026-07-07 | FJI935 | ADL → MEL | Jul 7, 04:30 UTC | Jul 7, 05:25 UTC | 55m |
| 2026-07-07 | FJI935 | - | Jul 7, 00:30 UTC | Jul 7, 02:55 UTC | 2h 25m |
| 2026-07-06 | FJI935 | WLG → ADL | Jul 6, 04:45 UTC | Jul 7, 02:55 UTC | 22h 10m |
| 2026-07-05 | FJI461 | - | Jul 5, 19:15 UTC | Jul 6, 03:05 UTC | 7h 50m |
| 2026-07-05 | FJI950 | - | Jul 5, 02:45 UTC | Jul 5, 11:15 UTC | 8h 30m |
| 2026-07-05 | FJI951 | - | Jul 5, 00:15 UTC | Jul 5, 01:15 UTC | 1h 0m |
| 2026-07-04 | FJI460 | - | Jul 4, 04:35 UTC | Jul 5, 01:15 UTC | 20h 40m |
| 2026-07-04 | FJI460 | - | Jul 4, 04:25 UTC | Jul 5, 01:15 UTC | 20h 50m |
| 2026-07-03 | FJI461 | - | Jul 3, 19:25 UTC | Jul 4, 03:05 UTC | 7h 40m |
| 2026-07-03 | FJI413 | - | Jul 3, 10:50 UTC | Jul 3, 11:25 UTC | 35m |
| 2026-07-02 | FJI450 | - | Jul 2, 01:05 UTC | Jul 2, 02:30 UTC | 1h 25m |
| 2026-07-01 | FJI451 | - | Jul 1, 22:20 UTC | Jul 1, 23:45 UTC | 1h 25m |
| 2026-06-30 | FJI823 | - | Jun 30, 23:35 UTC | Jul 1, 22:30 UTC | 22h 55m |
| 2026-06-30 | FJI934 | - | Jun 30, 03:40 UTC | Jun 30, 21:30 UTC | 17h 50m |
| 2026-06-30 | FJI935 | - | Jun 30, 00:25 UTC | Jun 30, 02:00 UTC | 1h 36m |
| 2026-06-29 | FJI935 | - | Jun 29, 02:35 UTC | Jun 30, 02:00 UTC | 23h 26m |
| 2026-06-29 | FJI450 | - | Jun 29, 02:05 UTC | Jun 30, 00:30 UTC | 22h 25m |
| 2026-06-28 | FJI451 | - | Jun 28, 12:50 UTC | Jun 29, 00:54 UTC | 12h 5m |
| 2026-06-27 | FJI1466 | - | Jun 27, 23:10 UTC | Jun 28, 10:44 UTC | 11h 35m |
| 2026-06-27 | FJI1467 | - | Jun 27, 21:04 UTC | Jun 27, 21:55 UTC | 50m |
| 2026-06-27 | FJI461 | - | Jun 27, 05:39 UTC | Jun 27, 07:15 UTC | 1h 35m |
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-FAD page for operator, model, and routing details .