sensors Mode-S transponder
780A3B
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-KQI · BOEING 777-300ER
- Hex
- 780A3B
- Octal
- 36005073
- Decimal
- 7,866,939
- Country
- CN
- Tail
- B-KQI
- Type
- B77W
- Flights observed
- 200
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 48m ago
Last known position
Country allocation
The ICAO 24-bit address 780A3B 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 |
|---|---|---|---|
| CPA253 | - | 29 | 2026-07-11 |
| CPA254 | - | 27 | 2026-07-12 |
| CPA251 | Cathay Pacific | 24 | 2026-07-01 |
| CPA252 | Cathay Pacific | 16 | 2026-07-02 |
| CPA881 | - | 14 | 2026-07-13 |
| CPA880 | - | 13 | 2026-07-12 |
| CPA831 | - | 10 | 2026-07-03 |
| CPA830 | - | 10 | 2026-07-14 |
| CPA234 | Cathay Pacific | 9 | 2026-05-22 |
| CPA233 | Cathay Pacific | 9 | 2026-05-21 |
| CPA391 | - | 8 | 2026-07-09 |
| CPA390 | - | 7 | 2026-07-09 |
| CPA882 | Cathay Pacific | 6 | 2026-05-29 |
| CPA883 | Cathay Pacific | 4 | 2026-05-30 |
| CPA774 | Cathay Pacific | 2 | 2026-04-29 |
| CPA743 | - | 2 | 2026-06-13 |
| CPA431 | - | 2 | 2026-06-13 |
| CPA104 | - | 2 | 2026-06-30 |
| CPA742 | Cathay Pacific | 1 | 2026-06-13 |
| CPA717 | Cathay Pacific | 1 | 2026-04-29 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | CPA830 | - | Jul 14, 01:40 UTC | Jul 14, 04:45 UTC | 3h 5m |
| 2026-07-13 | CPA881 | - | Jul 13, 08:35 UTC | Jul 13, 22:10 UTC | 13h 35m |
| 2026-07-12 | CPA880 | - | Jul 12, 16:30 UTC | Jul 13, 05:31 UTC | 13h 0m |
| 2026-07-12 | CPA254 | ZGN → HKG | Jul 12, 08:25 UTC | Jul 12, 09:00 UTC | 35m |
| 2026-07-11 | CPA254 | - | Jul 11, 21:25 UTC | Jul 12, 00:20 UTC | 2h 55m |
| 2026-07-11 | CPA253 | - | Jul 11, 13:55 UTC | Jul 11, 19:15 UTC | 5h 20m |
| 2026-07-11 | CPA253 | - | Jul 11, 05:55 UTC | Jul 11, 06:10 UTC | 15m |
| 2026-07-10 | CPA881 | - | Jul 10, 08:45 UTC | Jul 10, 22:35 UTC | 13h 50m |
| 2026-07-09 | CPA880 | - | Jul 9, 16:35 UTC | Jul 10, 05:20 UTC | 12h 45m |
| 2026-07-09 | CPA391 | - | Jul 9, 06:05 UTC | Jul 9, 08:40 UTC | 2h 35m |
| 2026-07-09 | CPA390 | - | Jul 9, 01:15 UTC | Jul 9, 01:30 UTC | 15m |
| 2026-07-08 | CPA881 | LAX → HKG | Jul 8, 09:25 UTC | Jul 8, 23:15 UTC | 13h 50m |
| 2026-07-07 | CPA880 | HKG → LAX | Jul 7, 18:45 UTC | Jul 8, 07:05 UTC | 12h 20m |
| 2026-07-07 | CPA254 | ZGN → HKG | Jul 7, 09:10 UTC | Jul 7, 10:30 UTC | 1h 20m |
| 2026-07-06 | CPA254 | - | Jul 6, 22:00 UTC | Jul 7, 02:15 UTC | 4h 15m |
| 2026-07-06 | CPA253 | HKG → LHR | Jul 6, 13:55 UTC | Jul 6, 19:10 UTC | 5h 15m |
| 2026-07-06 | CPA253 | HKG → LHR | Jul 6, 05:35 UTC | Jul 6, 05:50 UTC | 15m |
| 2026-07-05 | CPA881 | LAX → HKG | Jul 5, 08:40 UTC | Jul 5, 22:20 UTC | 13h 40m |
| 2026-07-04 | CPA880 | HKG → LAX | Jul 4, 16:30 UTC | Jul 5, 05:10 UTC | 12h 40m |
| 2026-07-03 | CPA831 | JFK → HKG | Jul 3, 20:25 UTC | Jul 4, 11:45 UTC | 15h 20m |
| 2026-07-03 | CPA830 | HKG → JFK | Jul 3, 02:40 UTC | Jul 3, 18:05 UTC | 15h 25m |
| 2026-07-02 | CPA252 | LHR → HKG | Jul 2, 11:40 UTC | Jul 2, 23:20 UTC | 11h 40m |
| 2026-07-01 | CPA251 | HKG → LHR | Jul 1, 23:30 UTC | Jul 2, 04:30 UTC | 5h 0m |
| 2026-07-01 | CPA251 | HKG → LHR | Jul 1, 15:30 UTC | Jul 1, 15:45 UTC | 15m |
| 2026-07-01 | CPA391 | - | Jul 1, 06:05 UTC | Jul 1, 08:50 UTC | 2h 45m |
| 2026-07-01 | CPA390 | - | Jul 1, 01:20 UTC | Jul 1, 01:35 UTC | 15m |
| 2026-06-30 | CPA104 | - | Jun 30, 13:15 UTC | Jun 30, 13:35 UTC | 20m |
| 2026-06-30 | CPA104 | - | Jun 30, 04:45 UTC | Jun 30, 12:25 UTC | 7h 40m |
| 2026-06-29 | CPA105 | HKG → MEL | Jun 29, 16:35 UTC | Jun 30, 01:04 UTC | 8h 30m |
| 2026-06-28 | CPA831 | JFK → HKG | Jun 28, 21:24 UTC | Jun 29, 13:00 UTC | 15h 35m |
| 2026-06-28 | CPA830 | HKG → JFK | Jun 28, 03:59 UTC | Jun 28, 18:59 UTC | 15h 0m |
| 2026-06-27 | CPA252 | LHR → HKG | Jun 27, 12:39 UTC | Jun 28, 00:04 UTC | 11h 25m |
| 2026-06-27 | CPA251 | HKG → LHR | Jun 27, 00:05 UTC | Jun 27, 04:54 UTC | 4h 50m |
| 2026-06-26 | CPA251 | HKG → LHR | Jun 26, 15:29 UTC | Jun 26, 15:45 UTC | 15m |
| 2026-06-26 | CPA254 | - | Jun 26, 08:34 UTC | Jun 26, 09:14 UTC | 40m |
| 2026-06-25 | CPA254 | - | Jun 25, 21:25 UTC | Jun 26, 00:30 UTC | 3h 5m |
| 2026-06-25 | CPA253 | HKG → LHR | Jun 25, 13:59 UTC | Jun 25, 15:20 UTC | 1h 20m |
| 2026-06-25 | CPA253 | HKG → LHR | Jun 25, 05:44 UTC | Jun 25, 05:55 UTC | 10m |
| 2026-06-24 | CPA252 | LHR → HKG | Jun 24, 11:54 UTC | Jun 24, 23:40 UTC | 11h 45m |
| 2026-06-23 | CPA251 | HKG → LHR | Jun 23, 23:24 UTC | Jun 24, 04:15 UTC | 4h 50m |
| 2026-06-23 | CPA251 | HKG → LHR | Jun 23, 15:04 UTC | Jun 23, 15:19 UTC | 15m |
| 2026-06-22 | CPA831 | JFK → HKG | Jun 22, 19:34 UTC | Jun 23, 11:14 UTC | 15h 40m |
| 2026-06-22 | CPA830 | HKG → JFK | Jun 22, 01:29 UTC | Jun 22, 16:50 UTC | 15h 20m |
| 2026-06-21 | CPA391 | - | Jun 21, 06:24 UTC | Jun 21, 09:20 UTC | 2h 55m |
| 2026-06-21 | CPA390 | - | Jun 21, 01:25 UTC | Jun 21, 01:39 UTC | 15m |
| 2026-06-20 | CPA881 | LAX → HKG | Jun 20, 08:49 UTC | Jun 20, 19:55 UTC | 11h 5m |
| 2026-06-19 | CPA880 | HKG → LAX | Jun 19, 16:25 UTC | Jun 20, 04:44 UTC | 12h 20m |
| 2026-06-19 | CPA254 | - | Jun 19, 09:40 UTC | Jun 19, 10:14 UTC | 35m |
| 2026-06-18 | CPA254 | - | Jun 18, 22:20 UTC | Jun 19, 02:39 UTC | 4h 19m |
| 2026-06-18 | CPA253 | HKG → LHR | Jun 18, 15:00 UTC | Jun 18, 20:05 UTC | 5h 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-KQI page for operator, model, and routing details .