sensors Mode-S transponder
78022E
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-KPO · BOEING 777-300ER
- Hex
- 78022E
- Octal
- 36001056
- Decimal
- 7,864,878
- Country
- CN
- Tail
- B-KPO
- Type
- B77W
- Flights observed
- 111
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 5h ago
Last known position
Country allocation
The ICAO 24-bit address 78022E 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 |
|---|---|---|---|
| CPA885 | - | 14 | 2026-06-13 |
| CPA884 | Cathay Pacific | 12 | 2026-06-12 |
| CPA289 | Cathay Pacific | 10 | 2026-06-14 |
| CPA549 | Cathay Pacific | 9 | 2026-06-10 |
| CPA288 | Cathay Pacific | 8 | 2026-06-14 |
| CPA255 | Cathay Pacific | 6 | 2026-06-02 |
| CPA548 | Cathay Pacific | 5 | 2026-06-10 |
| CPA250 | Cathay Pacific | 4 | 2026-06-04 |
| CPA234 | Cathay Pacific | 4 | 2026-05-13 |
| CPA233 | Cathay Pacific | 4 | 2026-05-13 |
| CPA178 | Cathay Pacific | 4 | 2026-06-07 |
| CPA873 | Cathay Pacific | 3 | 2026-05-27 |
| CPA100 | Cathay Pacific | 3 | 2026-05-29 |
| CPA872 | Cathay Pacific | 2 | 2026-05-26 |
| CPA867 | Cathay Pacific | 2 | 2026-06-05 |
| CPA367 | Cathay Pacific | 2 | 2026-05-25 |
| CPA254 | - | 2 | 2026-06-17 |
| CPA253 | Cathay Pacific | 2 | 2026-06-16 |
| CPA181 | Cathay Pacific | 2 | 2026-05-28 |
| CPA163 | Cathay Pacific | 2 | 2026-06-07 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-17 | CPA254 | - | Jun 17, 09:05 UTC | Jun 17, 09:45 UTC | 40m |
| 2026-06-16 | CPA254 | - | Jun 16, 21:40 UTC | Jun 17, 01:50 UTC | 4h 10m |
| 2026-06-16 | CPA253 | HKG → LHR | Jun 16, 13:50 UTC | Jun 16, 19:15 UTC | 5h 25m |
| 2026-06-16 | CPA253 | HKG → LHR | Jun 16, 05:40 UTC | Jun 16, 05:55 UTC | 15m |
| 2026-06-15 | CPA138 | SYD → HKG | Jun 15, 12:49 UTC | Jun 15, 21:30 UTC | 8h 40m |
| 2026-06-15 | CPA139 | HKG → SYD | Jun 15, 02:15 UTC | Jun 15, 10:45 UTC | 8h 30m |
| 2026-06-14 | CPA288 | FRA → HKG | Jun 14, 22:35 UTC | Jun 14, 23:05 UTC | 30m |
| 2026-06-14 | CPA288 | FRA → HKG | Jun 14, 12:05 UTC | Jun 14, 14:10 UTC | 2h 5m |
| 2026-06-14 | CPA289 | HKG → FRA | Jun 14, 01:05 UTC | Jun 14, 05:25 UTC | 4h 20m |
| 2026-06-13 | CPA289 | HKG → FRA | Jun 13, 16:25 UTC | Jun 13, 16:45 UTC | 20m |
| 2026-06-13 | CPA885 | - | Jun 13, 10:40 UTC | Jun 13, 11:00 UTC | 20m |
| 2026-06-12 | CPA885 | - | Jun 12, 20:40 UTC | Jun 13, 10:05 UTC | 13h 24m |
| 2026-06-12 | CPA884 | HKG → LAX | Jun 12, 06:10 UTC | Jun 12, 17:15 UTC | 11h 5m |
| 2026-06-12 | CPA884 | HKG → LAX | Jun 12, 05:25 UTC | Jun 12, 05:40 UTC | 15m |
| 2026-06-11 | CPA288 | FRA → HKG | Jun 11, 23:10 UTC | Jun 11, 23:30 UTC | 20m |
| 2026-06-11 | CPA288 | FRA → HKG | Jun 11, 12:30 UTC | Jun 11, 14:45 UTC | 2h 15m |
| 2026-06-10 | CPA289 | HKG → FRA | Jun 10, 23:50 UTC | Jun 11, 05:00 UTC | 5h 10m |
| 2026-06-10 | CPA289 | HKG → FRA | Jun 10, 16:20 UTC | Jun 10, 16:35 UTC | 15m |
| 2026-06-10 | CPA549 | HND → HKG | Jun 10, 12:10 UTC | Jun 10, 12:25 UTC | 15m |
| 2026-06-10 | CPA549 | HND → HKG | Jun 10, 08:15 UTC | Jun 10, 11:35 UTC | 3h 20m |
| 2026-06-10 | CPA548 | HKG → HND | Jun 10, 01:15 UTC | Jun 10, 04:40 UTC | 3h 25m |
| 2026-06-08 | CPA885 | LAX → HKG | Jun 8, 21:00 UTC | Jun 9, 11:30 UTC | 14h 30m |
| 2026-06-08 | CPA884 | HKG → LAX | Jun 8, 06:40 UTC | Jun 8, 18:00 UTC | 11h 20m |
| 2026-06-08 | CPA884 | HKG → LAX | Jun 8, 06:00 UTC | Jun 8, 06:10 UTC | 10m |
| 2026-06-07 | CPA178 | MEL → HKG | Jun 7, 23:35 UTC | Jun 7, 23:40 UTC | 5m |
| 2026-06-07 | CPA178 | MEL → HKG | Jun 7, 14:20 UTC | Jun 7, 21:50 UTC | 7h 30m |
| 2026-06-07 | CPA163 | HKG → MEL | Jun 7, 04:00 UTC | Jun 7, 12:15 UTC | 8h 15m |
| 2026-06-06 | CPA288 | FRA → HKG | Jun 6, 12:04 UTC | Jun 6, 23:24 UTC | 11h 20m |
| 2026-06-06 | CPA289 | HKG → FRA | Jun 6, 01:00 UTC | Jun 6, 05:05 UTC | 4h 5m |
| 2026-06-05 | CPA289 | HKG → FRA | Jun 5, 16:20 UTC | Jun 5, 16:35 UTC | 15m |
| 2026-06-05 | CPA867 | YVR → HKG | Jun 5, 10:30 UTC | Jun 5, 10:45 UTC | 15m |
| 2026-06-04 | CPA867 | YVR → HKG | Jun 4, 22:10 UTC | Jun 5, 09:55 UTC | 11h 45m |
| 2026-06-04 | CPA810 | HKG → YVR | Jun 4, 08:45 UTC | Jun 4, 20:00 UTC | 11h 15m |
| 2026-06-04 | CPA250 | LHR → HKG | Jun 4, 05:30 UTC | Jun 4, 06:00 UTC | 30m |
| 2026-06-03 | CPA250 | LHR → HKG | Jun 3, 18:05 UTC | Jun 3, 22:25 UTC | 4h 20m |
| 2026-06-02 | CPA255 | HKG → LHR | Jun 2, 20:45 UTC | Jun 3, 05:15 UTC | 8h 30m |
| 2026-06-02 | CPA255 | HKG → LHR | Jun 2, 15:30 UTC | Jun 2, 15:45 UTC | 15m |
| 2026-06-02 | CPA885 | LAX → HKG | Jun 2, 10:00 UTC | Jun 2, 10:15 UTC | 15m |
| 2026-06-01 | CPA885 | LAX → HKG | Jun 1, 20:35 UTC | Jun 2, 09:25 UTC | 12h 50m |
| 2026-06-01 | CPA884 | HKG → LAX | Jun 1, 05:00 UTC | Jun 1, 17:15 UTC | 12h 15m |
| 2026-05-31 | CPA288 | FRA → HKG | May 31, 22:50 UTC | May 31, 23:10 UTC | 20m |
| 2026-05-31 | CPA288 | FRA → HKG | May 31, 12:15 UTC | May 31, 15:50 UTC | 3h 35m |
| 2026-05-30 | CPA289 | HKG → FRA | May 30, 21:20 UTC | May 31, 01:11 UTC | 3h 51m |
| 2026-05-30 | CPA289 | HKG → FRA | May 30, 16:15 UTC | May 30, 16:35 UTC | 20m |
| 2026-05-30 | CPA549 | HND → HKG | May 30, 07:35 UTC | May 30, 11:25 UTC | 3h 50m |
| 2026-05-30 | CPA548 | HKG → HND | May 30, 01:10 UTC | May 30, 04:50 UTC | 3h 40m |
| 2026-05-29 | CPA100 | SYD → HKG | May 29, 12:55 UTC | May 29, 13:20 UTC | 25m |
| 2026-05-29 | CPA100 | SYD → HKG | May 29, 04:45 UTC | May 29, 12:05 UTC | 7h 20m |
| 2026-05-28 | CPA181 | HKG → SYD | May 28, 17:10 UTC | May 29, 01:40 UTC | 8h 30m |
| 2026-05-28 | CPA319 | PVG → HKG | May 28, 00:35 UTC | May 28, 06:45 UTC | 6h 10m |
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-KPO page for operator, model, and routing details .