sensors Mode-S transponder
780220
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-KPI · BOEING 777-300ER
- Hex
- 780220
- Octal
- 36001040
- Decimal
- 7,864,864
- Country
- CN
- Tail
- B-KPI
- Type
- B77W
- Flights observed
- 197
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 4m ago
Current position
Country allocation
The ICAO 24-bit address 780220 falls within the block assigned to China (CN) by ICAO Annex 10, Volume III. Every aircraft registered in China 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 |
|---|---|---|---|
| CPA178 | Cathay Pacific | 14 | 2026-07-05 |
| CPA873 | Cathay Pacific | 12 | 2026-07-04 |
| CPA872 | Cathay Pacific | 12 | 2026-07-03 |
| CPA289 | Cathay Pacific | 11 | 2026-04-28 |
| CPA288 | Cathay Pacific | 11 | 2026-04-29 |
| CPA100 | - | 11 | 2026-07-12 |
| CPA885 | - | 10 | 2026-07-06 |
| CPA255 | - | 10 | 2026-07-08 |
| CPA250 | - | 10 | 2026-07-09 |
| CPA884 | - | 9 | 2026-07-06 |
| CPA865 | Cathay Pacific | 8 | 2026-06-26 |
| CPA581 | Cathay Pacific | 8 | 2026-05-06 |
| CPA163 | - | 8 | 2026-07-05 |
| CPA181 | - | 7 | 2026-07-11 |
| CPA867 | - | 6 | 2026-07-09 |
| CPA580 | Cathay Pacific | 6 | 2026-05-06 |
| CPA888 | Cathay Pacific | 4 | 2026-06-25 |
| CPA810 | - | 4 | 2026-07-09 |
| CPA549 | - | 4 | 2026-07-03 |
| CPA233 | Cathay Pacific | 4 | 2026-06-15 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | CPA883 | - | Jul 14, 07:45 UTC | Jul 14, 18:00 UTC | 10h 15m |
| 2026-07-13 | CPA882 | - | Jul 13, 11:30 UTC | Jul 14, 00:55 UTC | 13h 25m |
| 2026-07-12 | CPA100 | - | Jul 12, 12:55 UTC | Jul 12, 13:05 UTC | 10m |
| 2026-07-12 | CPA100 | - | Jul 12, 04:20 UTC | Jul 12, 12:05 UTC | 7h 45m |
| 2026-07-11 | CPA181 | HKG → SYD | Jul 11, 17:00 UTC | Jul 12, 01:20 UTC | 8h 20m |
| 2026-07-11 | CPA100 | SYD → HKG | Jul 11, 04:20 UTC | Jul 11, 13:10 UTC | 8h 50m |
| 2026-07-10 | CPA181 | - | Jul 10, 17:00 UTC | Jul 11, 01:25 UTC | 8h 25m |
| 2026-07-09 | CPA867 | YVR → HKG | Jul 9, 22:15 UTC | Jul 10, 10:35 UTC | 12h 20m |
| 2026-07-09 | CPA810 | HKG → YVR | Jul 9, 08:15 UTC | Jul 9, 19:50 UTC | 11h 35m |
| 2026-07-09 | CPA250 | - | Jul 9, 04:55 UTC | Jul 9, 05:25 UTC | 30m |
| 2026-07-08 | CPA250 | - | Jul 8, 17:50 UTC | Jul 8, 22:05 UTC | 4h 15m |
| 2026-07-08 | CPA255 | - | Jul 8, 00:05 UTC | Jul 8, 05:20 UTC | 5h 15m |
| 2026-07-07 | CPA255 | - | Jul 7, 15:50 UTC | Jul 7, 16:05 UTC | 15m |
| 2026-07-06 | CPA885 | LAX → HKG | Jul 6, 20:50 UTC | Jul 7, 11:00 UTC | 14h 10m |
| 2026-07-06 | CPA884 | HKG → LAX | Jul 6, 05:05 UTC | Jul 6, 17:50 UTC | 12h 45m |
| 2026-07-05 | CPA178 | MEL → HKG | Jul 5, 22:20 UTC | Jul 5, 22:40 UTC | 20m |
| 2026-07-05 | CPA178 | MEL → HKG | Jul 5, 14:10 UTC | Jul 5, 21:30 UTC | 7h 20m |
| 2026-07-05 | CPA163 | HKG → MEL | Jul 5, 03:40 UTC | Jul 5, 12:15 UTC | 8h 35m |
| 2026-07-04 | CPA873 | SFO → HKG | Jul 4, 08:35 UTC | Jul 4, 21:50 UTC | 13h 15m |
| 2026-07-03 | CPA872 | HKG → SFO | Jul 3, 17:30 UTC | Jul 4, 05:35 UTC | 12h 5m |
| 2026-07-03 | CPA549 | - | Jul 3, 12:15 UTC | Jul 3, 12:30 UTC | 15m |
| 2026-07-03 | CPA549 | - | Jul 3, 08:45 UTC | Jul 3, 11:40 UTC | 2h 55m |
| 2026-07-03 | CPA548 | HKG → HND | Jul 3, 01:30 UTC | Jul 3, 05:10 UTC | 3h 40m |
| 2026-07-02 | CPA873 | SFO → HKG | Jul 2, 08:40 UTC | Jul 2, 21:50 UTC | 13h 10m |
| 2026-07-01 | CPA872 | HKG → SFO | Jul 1, 17:45 UTC | Jul 2, 05:30 UTC | 11h 45m |
| 2026-07-01 | CPA704 | BKK → HKG | Jul 1, 15:00 UTC | Jul 1, 15:05 UTC | 5m |
| 2026-07-01 | CPA701 | - | Jul 1, 11:10 UTC | Jul 1, 11:35 UTC | 25m |
| 2026-07-01 | CPA701 | - | Jul 1, 09:15 UTC | Jul 1, 10:10 UTC | 55m |
| 2026-07-01 | CPA930 | - | Jul 1, 05:50 UTC | Jul 1, 07:25 UTC | 1h 35m |
| 2026-07-01 | CPA901 | - | Jul 1, 02:05 UTC | Jul 1, 03:45 UTC | 1h 40m |
| 2026-06-29 | CPA873 | SFO → HKG | Jun 29, 09:05 UTC | Jun 29, 22:30 UTC | 13h 25m |
| 2026-06-28 | CPA872 | HKG → SFO | Jun 28, 17:39 UTC | Jun 29, 05:20 UTC | 11h 40m |
| 2026-06-27 | CPA138 | SYD → HKG | Jun 27, 12:15 UTC | Jun 27, 20:59 UTC | 8h 45m |
| 2026-06-27 | CPA139 | - | Jun 27, 02:04 UTC | Jun 27, 10:29 UTC | 8h 25m |
| 2026-06-26 | CPA865 | YVR → HKG | Jun 26, 21:10 UTC | Jun 26, 21:30 UTC | 20m |
| 2026-06-26 | CPA865 | YVR → HKG | Jun 26, 08:50 UTC | Jun 26, 20:34 UTC | 11h 45m |
| 2026-06-25 | CPA888 | HKG → YVR | Jun 25, 17:34 UTC | Jun 26, 04:39 UTC | 11h 5m |
| 2026-06-24 | CPA885 | - | Jun 24, 20:44 UTC | Jun 25, 10:55 UTC | 14h 10m |
| 2026-06-24 | CPA884 | - | Jun 24, 05:09 UTC | Jun 24, 17:25 UTC | 12h 15m |
| 2026-06-23 | CPA178 | MEL → HKG | Jun 23, 14:04 UTC | Jun 23, 22:55 UTC | 8h 50m |
| 2026-06-23 | CPA163 | HKG → MEL | Jun 23, 03:39 UTC | Jun 23, 12:05 UTC | 8h 25m |
| 2026-06-22 | CPA178 | MEL → HKG | Jun 22, 13:59 UTC | Jun 22, 22:49 UTC | 8h 50m |
| 2026-06-22 | CPA163 | HKG → MEL | Jun 22, 03:45 UTC | Jun 22, 12:05 UTC | 8h 20m |
| 2026-06-20 | CPA873 | SFO → HKG | Jun 20, 08:44 UTC | Jun 20, 21:49 UTC | 13h 5m |
| 2026-06-19 | CPA872 | HKG → SFO | Jun 19, 17:34 UTC | Jun 20, 05:49 UTC | 12h 15m |
| 2026-06-19 | CPA100 | - | Jun 19, 04:25 UTC | Jun 19, 13:39 UTC | 9h 15m |
| 2026-06-18 | CPA181 | HKG → SYD | Jun 18, 17:25 UTC | Jun 19, 01:39 UTC | 8h 14m |
| 2026-06-16 | CPA885 | - | Jun 16, 20:55 UTC | Jun 17, 11:00 UTC | 14h 5m |
| 2026-06-16 | CPA884 | - | Jun 16, 05:10 UTC | Jun 16, 17:45 UTC | 12h 35m |
| 2026-06-15 | CPA234 | MXP → HKG | Jun 15, 11:19 UTC | Jun 15, 22:25 UTC | 11h 5m |
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 B-KPI page for operator, model, and routing details .