sensors Mode-S transponder
C880A8
ICAO 24-bit transponder address · allocated to Fiji
Currently assigned to DQ-FAM · AIRBUS A-350-900
- Hex
- C880A8
- Octal
- 62100250
- Decimal
- 13,140,136
- Country
- FJ
- Tail
- DQ-FAM
- Type
- A359
- Flights observed
- 88
- Distinct callsigns
- 17
- Country
- FJ
- Last broadcast
- 23h ago
Last known position
Country allocation
The ICAO 24-bit address C880A8 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 17 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| FJI911 | - | 21 | 2026-07-11 |
| FJI935 | - | 15 | 2026-07-09 |
| FJI910 | - | 12 | 2026-07-12 |
| FJI934 | - | 10 | 2026-07-10 |
| FJI890 | - | 6 | 2026-06-27 |
| FJI811 | - | 5 | 2026-07-13 |
| FJI810 | Air Pacific | 4 | 2026-06-10 |
| FJI891 | - | 3 | 2026-06-28 |
| FJI393 | - | 3 | 2026-07-08 |
| FJI2007 | Air Pacific | 2 | 2026-04-16 |
| FJI921 | Air Pacific | 1 | 2026-05-29 |
| FJI871 | - | 1 | 2026-07-06 |
| FJI392 | - | 1 | 2026-07-09 |
| FJI2802 | Air Pacific | 1 | 2026-06-14 |
| FJI2801 | Air Pacific | 1 | 2026-06-14 |
| FJI2006 | Air Pacific | 1 | 2026-05-13 |
| FJI1810 | Air Pacific | 1 | 2026-05-23 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | FJI811 | - | Jul 13, 07:10 UTC | Jul 13, 07:40 UTC | 30m |
| 2026-07-12 | FJI910 | - | Jul 12, 04:05 UTC | Jul 12, 19:50 UTC | 15h 45m |
| 2026-07-11 | FJI911 | SFO → SYD | Jul 11, 07:30 UTC | Jul 12, 01:50 UTC | 18h 20m |
| 2026-07-10 | FJI934 | MEL → SFO | Jul 10, 04:20 UTC | Jul 10, 20:55 UTC | 16h 35m |
| 2026-07-09 | FJI935 | - | Jul 9, 10:00 UTC | Jul 10, 02:20 UTC | 16h 20m |
| 2026-07-09 | FJI392 | - | Jul 9, 08:55 UTC | Jul 9, 09:15 UTC | 20m |
| 2026-07-08 | FJI393 | - | Jul 8, 21:30 UTC | Jul 8, 21:50 UTC | 20m |
| 2026-07-08 | FJI393 | - | Jul 8, 18:10 UTC | Jul 8, 20:40 UTC | 2h 30m |
| 2026-07-06 | FJI871 | - | Jul 6, 07:10 UTC | Jul 6, 07:35 UTC | 25m |
| 2026-07-05 | FJI934 | MEL → SFO | Jul 5, 04:15 UTC | Jul 5, 20:40 UTC | 16h 25m |
| 2026-07-04 | FJI935 | - | Jul 4, 08:05 UTC | Jul 5, 02:05 UTC | 18h 0m |
| 2026-07-04 | FJI935 | - | Jul 4, 07:45 UTC | Jul 5, 02:05 UTC | 18h 20m |
| 2026-07-03 | FJI910 | - | Jul 3, 03:55 UTC | Jul 3, 19:55 UTC | 16h 0m |
| 2026-07-02 | FJI911 | - | Jul 2, 08:35 UTC | Jul 3, 02:10 UTC | 17h 35m |
| 2026-07-01 | FJI393 | - | Jul 1, 03:55 UTC | Jul 1, 21:00 UTC | 17h 5m |
| 2026-06-30 | FJI911 | - | Jun 30, 07:20 UTC | Jul 1, 01:55 UTC | 18h 35m |
| 2026-06-29 | FJI910 | - | Jun 29, 04:30 UTC | Jun 29, 20:15 UTC | 15h 45m |
| 2026-06-29 | FJI911 | - | Jun 29, 01:29 UTC | Jun 29, 02:45 UTC | 1h 15m |
| 2026-06-28 | FJI891 | DFW → SYD | Jun 28, 04:15 UTC | Jun 29, 02:45 UTC | 22h 30m |
| 2026-06-27 | FJI890 | - | Jun 27, 04:05 UTC | Jun 27, 22:35 UTC | 18h 30m |
| 2026-06-27 | FJI890 | SYD → DFW | Jun 27, 03:44 UTC | Jun 27, 22:35 UTC | 18h 50m |
| 2026-06-26 | FJI911 | - | Jun 26, 07:14 UTC | Jun 27, 01:54 UTC | 18h 40m |
| 2026-06-25 | FJI934 | - | Jun 25, 04:20 UTC | Jun 25, 20:34 UTC | 16h 15m |
| 2026-06-25 | FJI935 | - | Jun 25, 01:24 UTC | Jun 25, 02:25 UTC | 1h 0m |
| 2026-06-24 | FJI935 | - | Jun 24, 07:05 UTC | Jun 25, 01:19 UTC | 18h 15m |
| 2026-06-23 | FJI910 | - | Jun 23, 03:45 UTC | Jun 23, 19:59 UTC | 16h 15m |
| 2026-06-23 | FJI911 | - | Jun 23, 01:04 UTC | Jun 23, 01:54 UTC | 50m |
| 2026-06-22 | FJI911 | - | Jun 22, 04:04 UTC | Jun 23, 01:54 UTC | 21h 50m |
| 2026-06-22 | FJI911 | SYD → SYD | Jun 22, 03:30 UTC | Jun 23, 01:54 UTC | 22h 25m |
| 2026-06-22 | FJI911 | - | Jun 22, 00:55 UTC | Jun 22, 01:40 UTC | 45m |
| 2026-06-21 | FJI891 | DFW → SYD | Jun 21, 04:49 UTC | Jun 22, 01:40 UTC | 20h 50m |
| 2026-06-20 | FJI890 | NAN → DFW | Jun 20, 03:29 UTC | Jun 20, 21:34 UTC | 18h 5m |
| 2026-06-19 | FJI911 | - | Jun 19, 07:14 UTC | Jun 20, 01:39 UTC | 18h 25m |
| 2026-06-18 | FJI934 | - | Jun 18, 04:30 UTC | Jun 18, 20:40 UTC | 16h 10m |
| 2026-06-18 | FJI935 | - | Jun 18, 00:00 UTC | Jun 18, 02:30 UTC | 2h 30m |
| 2026-06-17 | FJI935 | - | Jun 17, 07:10 UTC | Jun 18, 02:30 UTC | 19h 20m |
| 2026-06-16 | FJI910 | - | Jun 16, 03:55 UTC | Jun 16, 20:15 UTC | 16h 21m |
| 2026-06-15 | FJI911 | - | Jun 15, 07:15 UTC | Jun 16, 01:35 UTC | 18h 20m |
| 2026-06-14 | FJI2801 | SLC → NAN | Jun 14, 23:05 UTC | Jun 15, 00:45 UTC | 1h 39m |
| 2026-06-14 | FJI2802 | SFO → SLC | Jun 14, 03:30 UTC | Jun 14, 20:15 UTC | 16h 45m |
| 2026-06-14 | FJI911 | - | Jun 14, 00:10 UTC | Jun 14, 01:25 UTC | 1h 15m |
| 2026-06-12 | FJI934 | MEL → NAN | Jun 12, 03:55 UTC | Jun 12, 05:30 UTC | 1h 35m |
| 2026-06-12 | FJI935 | - | Jun 12, 00:25 UTC | Jun 12, 02:05 UTC | 1h 41m |
| 2026-06-11 | FJI935 | - | Jun 11, 07:15 UTC | Jun 12, 02:05 UTC | 18h 50m |
| 2026-06-10 | FJI810 | NAN → LAX | Jun 10, 19:25 UTC | Jun 10, 20:10 UTC | 45m |
| 2026-06-09 | FJI910 | SYD → NAN | Jun 9, 05:00 UTC | Jun 9, 05:40 UTC | 40m |
| 2026-06-09 | FJI911 | NAN → SYD | Jun 9, 00:30 UTC | Jun 9, 01:40 UTC | 1h 10m |
| 2026-06-08 | FJI934 | MEL → NAN | Jun 8, 04:20 UTC | Jun 9, 01:40 UTC | 21h 20m |
| 2026-06-08 | FJI935 | NAN → MEL | Jun 8, 00:55 UTC | Jun 8, 02:20 UTC | 1h 25m |
| 2026-06-07 | FJI935 | NAN → MEL | Jun 7, 06:05 UTC | Jun 8, 02:20 UTC | 20h 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-FAM page for operator, model, and routing details .