sensors Mode-S transponder
780212
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-KPF · BOEING 777-300ER
- Hex
- 780212
- Octal
- 36001022
- Decimal
- 7,864,850
- Country
- CN
- Tail
- B-KPF
- Type
- B77W
- Flights observed
- 196
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 2h ago
Last known position
Country allocation
The ICAO 24-bit address 780212 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 |
|---|---|---|---|
| CPA810 | Cathay Pacific | 16 | 2026-07-04 |
| CPA250 | - | 16 | 2026-07-14 |
| CPA867 | - | 13 | 2026-07-04 |
| CPA255 | - | 11 | 2026-07-12 |
| CPA289 | Cathay Pacific | 9 | 2026-07-05 |
| CPA288 | Cathay Pacific | 9 | 2026-07-06 |
| CPA865 | Cathay Pacific | 8 | 2026-06-22 |
| CPA581 | - | 8 | 2026-07-07 |
| CPA549 | - | 8 | 2026-06-13 |
| CPA178 | Cathay Pacific | 8 | 2026-06-15 |
| CPA100 | - | 8 | 2026-06-17 |
| CPA888 | Cathay Pacific | 7 | 2026-06-21 |
| CPA884 | - | 7 | 2026-07-11 |
| CPA548 | - | 7 | 2026-06-13 |
| CPA873 | Cathay Pacific | 6 | 2026-07-01 |
| CPA872 | Cathay Pacific | 6 | 2026-06-30 |
| CPA580 | - | 6 | 2026-07-07 |
| CPA233 | Cathay Pacific | 6 | 2026-07-07 |
| CPA885 | - | 5 | 2026-07-11 |
| CPA234 | - | 5 | 2026-07-08 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | CPA250 | - | Jul 14, 05:30 UTC | Jul 14, 05:50 UTC | 20m |
| 2026-07-13 | CPA250 | - | Jul 13, 18:10 UTC | Jul 13, 22:30 UTC | 4h 20m |
| 2026-07-12 | CPA255 | - | Jul 12, 23:50 UTC | Jul 13, 05:10 UTC | 5h 20m |
| 2026-07-12 | CPA255 | - | Jul 12, 15:45 UTC | Jul 12, 16:05 UTC | 20m |
| 2026-07-11 | CPA885 | - | Jul 11, 21:35 UTC | Jul 12, 10:55 UTC | 13h 20m |
| 2026-07-11 | CPA884 | HKG → LAX | Jul 11, 05:05 UTC | Jul 11, 18:10 UTC | 13h 5m |
| 2026-07-08 | CPA234 | - | Jul 8, 21:30 UTC | Jul 8, 22:10 UTC | 40m |
| 2026-07-08 | CPA234 | - | Jul 8, 11:15 UTC | Jul 8, 14:40 UTC | 3h 25m |
| 2026-07-07 | CPA233 | HKG → MXP | Jul 7, 22:10 UTC | Jul 8, 05:40 UTC | 7h 30m |
| 2026-07-07 | CPA233 | HKG → MXP | Jul 7, 17:05 UTC | Jul 7, 17:20 UTC | 15m |
| 2026-07-07 | CPA581 | - | Jul 7, 08:45 UTC | Jul 7, 13:20 UTC | 4h 35m |
| 2026-07-07 | CPA580 | - | Jul 7, 02:40 UTC | Jul 7, 07:10 UTC | 4h 30m |
| 2026-07-06 | CPA288 | FRA → HKG | Jul 6, 12:20 UTC | Jul 6, 23:10 UTC | 10h 50m |
| 2026-07-05 | CPA289 | HKG → FRA | Jul 5, 21:05 UTC | Jul 6, 04:35 UTC | 7h 30m |
| 2026-07-05 | CPA289 | HKG → FRA | Jul 5, 16:05 UTC | Jul 5, 16:25 UTC | 20m |
| 2026-07-04 | CPA867 | YVR → HKG | Jul 4, 22:20 UTC | Jul 5, 10:50 UTC | 12h 30m |
| 2026-07-04 | CPA810 | HKG → YVR | Jul 4, 09:15 UTC | Jul 4, 19:40 UTC | 10h 25m |
| 2026-07-04 | CPA810 | HKG → YVR | Jul 4, 08:25 UTC | Jul 4, 08:45 UTC | 20m |
| 2026-07-04 | CPA250 | LHR → HKG | Jul 4, 04:50 UTC | Jul 4, 05:15 UTC | 25m |
| 2026-07-03 | CPA250 | LHR → HKG | Jul 3, 17:35 UTC | Jul 3, 21:45 UTC | 4h 10m |
| 2026-07-02 | CPA255 | - | Jul 2, 23:50 UTC | Jul 3, 05:05 UTC | 5h 15m |
| 2026-07-02 | CPA255 | HKG → CAN | Jul 2, 15:40 UTC | Jul 2, 16:00 UTC | 20m |
| 2026-07-01 | CPA873 | SFO → HKG | Jul 1, 08:35 UTC | Jul 1, 21:55 UTC | 13h 20m |
| 2026-06-30 | CPA872 | HKG → SFO | Jun 30, 17:25 UTC | Jul 1, 05:15 UTC | 11h 50m |
| 2026-06-29 | CPA885 | - | Jun 29, 20:49 UTC | Jun 30, 10:50 UTC | 14h 1m |
| 2026-06-29 | CPA884 | - | Jun 29, 06:19 UTC | Jun 29, 17:49 UTC | 11h 30m |
| 2026-06-29 | CPA884 | - | Jun 29, 05:24 UTC | Jun 29, 05:45 UTC | 20m |
| 2026-06-28 | CPA288 | FRA → HKG | Jun 28, 22:34 UTC | Jun 28, 22:59 UTC | 25m |
| 2026-06-28 | CPA288 | FRA → HKG | Jun 28, 12:09 UTC | Jun 28, 15:49 UTC | 3h 40m |
| 2026-06-28 | CPA289 | HKG → FRA | Jun 28, 00:50 UTC | Jun 28, 04:59 UTC | 4h 10m |
| 2026-06-27 | CPA289 | HKG → FRA | Jun 27, 16:10 UTC | Jun 27, 16:24 UTC | 15m |
| 2026-06-26 | CPA885D | - | Jun 26, 01:10 UTC | Jun 26, 15:25 UTC | 14h 15m |
| 2026-06-25 | CPA884 | - | Jun 25, 10:55 UTC | Jun 25, 22:20 UTC | 11h 25m |
| 2026-06-25 | CPA884 | - | Jun 25, 10:04 UTC | Jun 25, 10:20 UTC | 15m |
| 2026-06-25 | CPA250 | LHR → HKG | Jun 25, 05:50 UTC | Jun 25, 06:25 UTC | 35m |
| 2026-06-24 | CPA250 | LHR → HKG | Jun 24, 18:05 UTC | Jun 24, 22:29 UTC | 4h 25m |
| 2026-06-23 | CPA255 | HKG → LHR | Jun 23, 15:59 UTC | Jun 24, 05:24 UTC | 13h 25m |
| 2026-06-22 | CPA865 | YVR → HKG | Jun 22, 08:40 UTC | Jun 22, 20:55 UTC | 12h 15m |
| 2026-06-21 | CPA888 | HKG → YVR | Jun 21, 17:10 UTC | Jun 22, 04:34 UTC | 11h 25m |
| 2026-06-21 | CPA902 | - | Jun 21, 14:44 UTC | Jun 21, 15:09 UTC | 25m |
| 2026-06-21 | CPA902 | - | Jun 21, 13:24 UTC | Jun 21, 13:59 UTC | 35m |
| 2026-06-21 | CPA903 | HKG → MNL | Jun 21, 09:15 UTC | Jun 21, 11:30 UTC | 2h 15m |
| 2026-06-20 | CPA581 | CTS → HKG | Jun 20, 08:19 UTC | Jun 20, 12:39 UTC | 4h 20m |
| 2026-06-20 | CPA580 | HKG → CTS | Jun 20, 01:55 UTC | Jun 20, 06:24 UTC | 4h 30m |
| 2026-06-19 | CPA234 | MXP → HKG | Jun 19, 11:04 UTC | Jun 19, 22:19 UTC | 11h 15m |
| 2026-06-19 | CPA233 | HKG → MXP | Jun 19, 03:55 UTC | Jun 19, 07:59 UTC | 4h 5m |
| 2026-06-18 | CPA233 | HKG → MXP | Jun 18, 19:25 UTC | Jun 18, 19:45 UTC | 20m |
| 2026-06-18 | CPA902 | - | Jun 18, 15:00 UTC | Jun 18, 15:15 UTC | 15m |
| 2026-06-18 | CPA902 | - | Jun 18, 13:30 UTC | Jun 18, 14:25 UTC | 55m |
| 2026-06-18 | CPA903 | HKG → MNL | Jun 18, 10:00 UTC | Jun 18, 11:40 UTC | 1h 40m |
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-KPF page for operator, model, and routing details .