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
- 158
- Distinct callsigns
- 20
- Country
- FJ
- Last broadcast
- 10h ago
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 |
|---|---|---|---|
| FJI914 | - | 13 | 2026-07-11 |
| FJI961 | - | 12 | 2026-07-12 |
| FJI950 | - | 11 | 2026-06-28 |
| FJI915 | - | 11 | 2026-07-11 |
| FJI960 | - | 10 | 2026-07-13 |
| FJI921 | - | 9 | 2026-07-13 |
| FJI461 | - | 8 | 2026-06-28 |
| FJI951 | - | 7 | 2026-06-27 |
| FJI935 | - | 7 | 2026-06-15 |
| FJI460 | Air Pacific | 7 | 2026-06-13 |
| FJI451 | - | 7 | 2026-07-10 |
| FJI413 | Air Pacific | 7 | 2026-06-11 |
| FJI920 | - | 6 | 2026-07-14 |
| FJI823 | - | 6 | 2026-07-07 |
| FJI934 | - | 5 | 2026-06-16 |
| FJI981 | Air Pacific | 4 | 2026-07-08 |
| FJI853 | - | 4 | 2026-07-03 |
| 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-14 | FJI920 | - | Jul 14, 03:00 UTC | Jul 14, 04:35 UTC | 1h 35m |
| 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 |
| 2026-06-29 | FJI921 | WLG → BNE | Jun 29, 04:30 UTC | Jun 30, 00:25 UTC | 19h 55m |
| 2026-06-28 | FJI461 | - | Jun 28, 19:20 UTC | Jun 29, 03:14 UTC | 7h 55m |
| 2026-06-28 | FJI950 | - | Jun 28, 02:44 UTC | Jun 28, 11:19 UTC | 8h 35m |
| 2026-06-27 | FJI951 | - | Jun 27, 06:40 UTC | Jun 28, 01:25 UTC | 18h 45m |
| 2026-06-26 | FJI451 | - | Jun 26, 20:10 UTC | Jun 27, 05:15 UTC | 9h 5m |
| 2026-06-26 | FJI915 | - | Jun 26, 10:44 UTC | Jun 26, 11:49 UTC | 1h 5m |
| 2026-06-25 | FJI960 | - | Jun 25, 03:20 UTC | Jun 25, 05:20 UTC | 2h 0m |
| 2026-06-24 | FJI961 | - | Jun 24, 21:24 UTC | Jun 25, 01:50 UTC | 4h 25m |
| 2026-06-23 | FJI823 | HNL → CXI | Jun 23, 22:40 UTC | Jun 24, 21:29 UTC | 22h 50m |
| 2026-06-23 | FJI822 | CXI → HNL | Jun 23, 19:59 UTC | Jun 23, 20:40 UTC | 40m |
| 2026-06-22 | FJI914 | - | Jun 22, 20:14 UTC | Jun 22, 21:05 UTC | 50m |
| 2026-06-22 | FJI915 | - | Jun 22, 02:00 UTC | Jun 22, 12:05 UTC | 10h 5m |
| 2026-06-21 | FJI451 | HNL → CHC | Jun 21, 11:55 UTC | Jun 22, 00:29 UTC | 12h 35m |
| 2026-06-20 | FJI914 | SYD → HNL | Jun 20, 20:20 UTC | Jun 21, 07:55 UTC | 11h 35m |
| 2026-06-20 | FJI450 | - | Jun 20, 02:09 UTC | Jun 20, 11:49 UTC | 9h 40m |
| 2026-06-19 | FJI451 | - | Jun 19, 23:04 UTC | Jun 20, 00:39 UTC | 1h 35m |
| 2026-06-18 | FJI914 | - | Jun 18, 20:35 UTC | Jun 18, 21:25 UTC | 50m |
| 2026-06-18 | FJI915 | - | Jun 18, 02:35 UTC | Jun 18, 12:10 UTC | 9h 35m |
| 2026-06-18 | FJI981 | NAN → OOL | Jun 18, 00:35 UTC | Jun 18, 01:25 UTC | 50m |
| 2026-06-16 | FJI823 | HNL → CXI | Jun 16, 22:35 UTC | Jun 16, 23:25 UTC | 50m |
| 2026-06-16 | FJI934 | - | Jun 16, 03:50 UTC | Jun 16, 20:45 UTC | 16h 56m |
| 2026-06-15 | FJI935 | - | Jun 15, 23:54 UTC | Jun 16, 01:30 UTC | 1h 35m |
| 2026-06-15 | FJI935 | - | Jun 15, 03:10 UTC | Jun 16, 01:30 UTC | 22h 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 .