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