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