sensors Mode-S transponder
78203D
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-32G3 · AIRBUS A-320neo
- Hex
- 78203D
- Octal
- 36020075
- Decimal
- 7,872,573
- Country
- CN
- Tail
- B-32G3
- Type
- A20N
- Flights observed
- 80
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address 78203D 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 |
|---|---|---|---|
| CQH8549 | Spring Airlines | 7 | 2026-04-24 |
| CQH8550 | Spring Airlines | 4 | 2026-04-25 |
| CQH7259 | Spring Airlines | 4 | 2026-04-19 |
| CQH6523 | Spring Airlines | 4 | 2026-04-24 |
| CQH6411 | - | 4 | 2026-07-08 |
| CQH7432 | Spring Airlines | 3 | 2026-05-31 |
| CQH8731 | Spring Airlines | 2 | 2026-05-28 |
| CQH7252 | - | 2 | 2026-05-14 |
| CQH7200 | - | 2 | 2026-06-21 |
| CQH6987 | - | 2 | 2026-06-10 |
| CQH6922 | - | 2 | 2026-06-21 |
| CQH6921 | Spring Airlines | 2 | 2026-06-21 |
| CQH6874 | Spring Airlines | 2 | 2026-06-01 |
| CQH6731 | - | 2 | 2026-07-09 |
| CQH6481 | Spring Airlines | 2 | 2026-06-03 |
| CQH8934 | - | 1 | 2026-06-20 |
| CQH8876 | Spring Airlines | 1 | 2026-04-29 |
| CQH8875 | Spring Airlines | 1 | 2026-04-28 |
| CQH8870 | - | 1 | 2026-04-13 |
| CQH8716 | Spring Airlines | 1 | 2026-05-26 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-11 | CQH6599 | - | Jul 11, 10:30 UTC | Jul 12, 04:20 UTC | 17h 50m |
| 2026-07-09 | CQH6732 | - | Jul 9, 13:50 UTC | Jul 9, 14:10 UTC | 20m |
| 2026-07-09 | CQH6731 | - | Jul 9, 11:05 UTC | Jul 9, 11:30 UTC | 25m |
| 2026-07-08 | CQH6411 | - | Jul 8, 10:00 UTC | Jul 8, 10:15 UTC | 15m |
| 2026-07-03 | CQH6411 | - | Jul 3, 10:25 UTC | Jul 3, 10:40 UTC | 15m |
| 2026-07-01 | CQH6411 | - | Jul 1, 09:55 UTC | Jul 1, 10:10 UTC | 15m |
| 2026-06-26 | CQH6411 | - | Jun 26, 09:55 UTC | Jun 26, 10:10 UTC | 15m |
| 2026-06-22 | CQH7286 | - | Jun 22, 01:49 UTC | Jun 22, 04:15 UTC | 2h 25m |
| 2026-06-21 | CQH7419 | - | Jun 21, 22:24 UTC | Jun 22, 00:24 UTC | 2h 0m |
| 2026-06-21 | CQH7200 | - | Jun 21, 18:35 UTC | Jun 21, 18:54 UTC | 20m |
| 2026-06-21 | CQH7200 | - | Jun 21, 14:24 UTC | Jun 21, 15:54 UTC | 1h 30m |
| 2026-06-21 | CQH7199 | - | Jun 21, 12:44 UTC | Jun 21, 13:04 UTC | 20m |
| 2026-06-21 | CQH6922 | - | Jun 21, 05:44 UTC | Jun 21, 06:04 UTC | 20m |
| 2026-06-21 | CQH6922 | - | Jun 21, 02:30 UTC | Jun 21, 02:50 UTC | 20m |
| 2026-06-21 | CQH6921 | CAN → KUL | Jun 21, 00:40 UTC | Jun 21, 00:59 UTC | 20m |
| 2026-06-20 | CQH6921 | CAN → KUL | Jun 20, 21:40 UTC | Jun 20, 21:55 UTC | 15m |
| 2026-06-20 | CQH8934 | - | Jun 20, 14:39 UTC | Jun 20, 16:05 UTC | 1h 25m |
| 2026-06-20 | CQH8511 | - | Jun 20, 11:54 UTC | Jun 20, 13:34 UTC | 1h 40m |
| 2026-06-18 | CQH6628 | CNX → XIY | Jun 18, 14:50 UTC | Jun 19, 03:15 UTC | 12h 24m |
| 2026-06-18 | CQH6627 | XIY → CNX | Jun 18, 12:55 UTC | Jun 18, 13:25 UTC | 30m |
| 2026-06-16 | CQH8598 | - | Jun 16, 09:40 UTC | Jun 16, 13:50 UTC | 4h 10m |
| 2026-06-16 | CQH8597 | - | Jun 16, 04:20 UTC | Jun 16, 07:30 UTC | 3h 10m |
| 2026-06-14 | CQH6900 | PUS → PVG | Jun 14, 13:15 UTC | Jun 14, 13:50 UTC | 35m |
| 2026-06-14 | CQH6899 | - | Jun 14, 11:45 UTC | Jun 14, 12:05 UTC | 20m |
| 2026-06-10 | CQH6988 | - | Jun 10, 07:35 UTC | Jun 10, 09:15 UTC | 1h 40m |
| 2026-06-10 | CQH6987 | - | Jun 10, 04:45 UTC | Jun 10, 06:10 UTC | 1h 25m |
| 2026-06-09 | CQH6987 | - | Jun 9, 09:45 UTC | Jun 10, 06:10 UTC | 20h 25m |
| 2026-06-04 | CQH8673 | SJW → HRB | Jun 4, 08:50 UTC | Jun 4, 09:05 UTC | 15m |
| 2026-06-04 | CQH8662 | CGQ → SJW | Jun 4, 06:00 UTC | Jun 4, 06:10 UTC | 10m |
| 2026-06-03 | CQH6481 | SZX → DOY | Jun 3, 22:30 UTC | Jun 3, 22:40 UTC | 10m |
| 2026-06-01 | CQH6481 | SZX → DOY | Jun 1, 22:50 UTC | Jun 1, 23:05 UTC | 15m |
| 2026-06-01 | CQH6874 | NGB → SZX | Jun 1, 15:55 UTC | Jun 1, 16:35 UTC | 40m |
| 2026-05-31 | CQH6874 | NGB → SZX | May 31, 17:20 UTC | Jun 1, 16:35 UTC | 23h 15m |
| 2026-05-31 | CQH7432 | DMK → NGB | May 31, 08:55 UTC | May 31, 17:25 UTC | 8h 30m |
| 2026-05-30 | CQH7432 | DMK → NGB | May 30, 09:35 UTC | May 31, 09:10 UTC | 23h 35m |
| 2026-05-30 | CQH7432 | DMK → NGB | May 30, 07:30 UTC | May 30, 10:00 UTC | 2h 30m |
| 2026-05-30 | CQH7431 | NGB → BKK | May 30, 02:45 UTC | May 30, 06:20 UTC | 3h 35m |
| 2026-05-29 | CQH7385 | NGB → SYX | May 29, 11:10 UTC | May 29, 11:45 UTC | 35m |
| 2026-05-28 | CQH8731 | SHE → NGB | May 28, 16:10 UTC | May 29, 11:45 UTC | 19h 35m |
| 2026-05-28 | CQH8731 | SHE → NGB | May 28, 13:30 UTC | May 29, 11:45 UTC | 22h 15m |
| 2026-05-26 | CQH8716 | HKG → PVG | May 26, 06:14 UTC | May 26, 07:24 UTC | 1h 10m |
| 2026-05-26 | CQH8715 | PVG → HKG | May 26, 03:50 UTC | May 26, 05:10 UTC | 1h 20m |
| 2026-05-23 | CQH6294 | BKK → XIY | May 23, 19:55 UTC | May 23, 20:50 UTC | 55m |
| 2026-05-23 | CQH6293 | XIY → BKK | May 23, 16:45 UTC | May 23, 17:40 UTC | 55m |
| 2026-05-22 | CQH7502 | BKK → TFU | May 22, 04:30 UTC | May 22, 10:30 UTC | 6h 0m |
| 2026-05-22 | CQH7501 | TFU → BKK | May 22, 02:05 UTC | May 22, 03:10 UTC | 1h 5m |
| 2026-05-15 | CQH7520 | SZX → SHA | May 15, 07:00 UTC | May 15, 07:10 UTC | 10m |
| 2026-05-14 | CQH7252 | - | May 14, 14:01 UTC | May 14, 14:10 UTC | 10m |
| 2026-05-06 | CQH7252 | - | May 6, 13:20 UTC | May 6, 13:35 UTC | 15m |
| 2026-05-06 | CQH7596 | ZUH → YTY | May 6, 06:05 UTC | May 6, 06:15 UTC | 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-32G3 page for operator, model, and routing details .