sensors Mode-S transponder
7817BB
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-30AP · AIRBUS A-320neo
- Hex
- 7817BB
- Octal
- 36013673
- Decimal
- 7,870,395
- Country
- CN
- Tail
- B-30AP
- Type
- A20N
- Flights observed
- 52
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 7h ago
Last known position
Country allocation
The ICAO 24-bit address 7817BB 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 |
|---|---|---|---|
| CSZ9301 | Shenzhen Airlines | 5 | 2026-06-04 |
| CSZ8983 | - | 4 | 2026-06-04 |
| CSZ9635 | Shenzhen Airlines | 3 | 2026-05-12 |
| CSZ9616 | - | 2 | 2026-05-13 |
| CSZ9615 | - | 2 | 2026-05-13 |
| CSZ9606 | Shenzhen Airlines | 2 | 2026-05-06 |
| CSZ9465 | Shenzhen Airlines | 2 | 2026-06-01 |
| CSZ9302 | Shenzhen Airlines | 2 | 2026-06-03 |
| CSZ9239 | Shenzhen Airlines | 2 | 2026-06-02 |
| CSZ9214 | Shenzhen Airlines | 2 | 2026-05-30 |
| CSZ9129 | Shenzhen Airlines | 2 | 2026-05-30 |
| CSZ8993 | Shenzhen Airlines | 2 | 2026-05-25 |
| CSZ9962 | - | 1 | 2026-04-22 |
| CSZ9876 | Shenzhen Airlines | 1 | 2026-04-23 |
| CSZ9868 | Shenzhen Airlines | 1 | 2026-04-30 |
| CSZ9853 | Shenzhen Airlines | 1 | 2026-04-28 |
| CSZ9636 | Shenzhen Airlines | 1 | 2026-05-13 |
| CSZ9605 | Shenzhen Airlines | 1 | 2026-05-05 |
| CSZ9467 | Shenzhen Airlines | 1 | 2026-05-15 |
| CSZ9455 | Shenzhen Airlines | 1 | 2026-04-28 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-04 | CSZ8983 | - | Jun 4, 08:30 UTC | Jun 4, 08:45 UTC | 15m |
| 2026-06-04 | CSZ9301 | SZX → CGO | Jun 4, 00:15 UTC | Jun 4, 00:30 UTC | 15m |
| 2026-06-03 | CSZ8983 | - | Jun 3, 08:15 UTC | Jun 3, 09:10 UTC | 55m |
| 2026-06-03 | CSZ9302 | CGO → SZX | Jun 3, 06:15 UTC | Jun 3, 06:25 UTC | 10m |
| 2026-06-03 | CSZ9301 | SZX → CGO | Jun 3, 00:00 UTC | Jun 3, 00:15 UTC | 15m |
| 2026-06-02 | CSZ9239 | SZX → URC | Jun 2, 02:20 UTC | Jun 2, 02:30 UTC | 10m |
| 2026-06-01 | CSZ9465 | SZX → CKG | Jun 1, 08:55 UTC | Jun 1, 09:05 UTC | 10m |
| 2026-06-01 | CSZ9301 | SZX → CGO | Jun 1, 01:05 UTC | Jun 1, 01:20 UTC | 15m |
| 2026-05-31 | CSZ9465 | SZX → CKG | May 31, 09:00 UTC | May 31, 09:10 UTC | 10m |
| 2026-05-30 | CSZ9235 | SZX → XNN | May 30, 23:45 UTC | May 31, 00:00 UTC | 15m |
| 2026-05-30 | CSZ9130 | HET → SZX | May 30, 12:50 UTC | May 30, 13:05 UTC | 15m |
| 2026-05-30 | CSZ9129 | SZX → HET | May 30, 05:55 UTC | May 30, 06:15 UTC | 20m |
| 2026-05-30 | CSZ9214 | XIY → SZX | May 30, 01:20 UTC | May 30, 01:35 UTC | 15m |
| 2026-05-25 | CSZ8993 | CAN → HAK | May 25, 14:00 UTC | May 25, 14:10 UTC | 10m |
| 2026-05-22 | CSZ8903 | CAN → CGO | May 22, 00:20 UTC | May 22, 00:35 UTC | 15m |
| 2026-05-15 | CSZ9415 | SZX → CTU | May 15, 22:55 UTC | May 15, 23:10 UTC | 15m |
| 2026-05-15 | CSZ9467 | SZX → CKG | May 15, 14:10 UTC | May 15, 14:25 UTC | 15m |
| 2026-05-15 | CSZ9239 | SZX → URC | May 15, 02:25 UTC | May 15, 02:35 UTC | 10m |
| 2026-05-14 | CSZ9234 | XNN → SZX | May 14, 14:45 UTC | May 14, 14:55 UTC | 10m |
| 2026-05-14 | CSZ9233 | SZX → XNN | May 14, 08:00 UTC | May 14, 08:15 UTC | 15m |
| 2026-05-13 | CSZ9616 | - | May 13, 11:25 UTC | May 13, 11:35 UTC | 10m |
| 2026-05-13 | CSZ9615 | - | May 13, 03:55 UTC | May 13, 04:10 UTC | 15m |
| 2026-05-13 | CSZ9636 | CGQ → SZX | May 13, 00:55 UTC | May 13, 01:10 UTC | 15m |
| 2026-05-12 | CSZ9635 | SZX → CGQ | May 12, 12:55 UTC | May 12, 13:10 UTC | 15m |
| 2026-05-12 | CSZ9129 | SZX → HET | May 12, 03:30 UTC | May 12, 03:40 UTC | 10m |
| 2026-05-11 | CSZ9635 | SZX → CGQ | May 11, 12:50 UTC | May 11, 13:00 UTC | 10m |
| 2026-05-11 | CSZ9615 | - | May 11, 03:45 UTC | May 11, 03:55 UTC | 10m |
| 2026-05-10 | CSZ9635 | SZX → CGQ | May 10, 12:49 UTC | May 10, 12:59 UTC | 10m |
| 2026-05-10 | CSZ9329 | CGO → SZX | May 10, 01:00 UTC | May 10, 01:20 UTC | 20m |
| 2026-05-09 | CSZ8983 | - | May 9, 08:55 UTC | May 9, 09:15 UTC | 20m |
| 2026-05-09 | CSZ9301 | SZX → CGO | May 9, 00:10 UTC | May 9, 00:25 UTC | 15m |
| 2026-05-08 | CSZ9238 | LHW → SZX | May 8, 10:25 UTC | May 8, 10:35 UTC | 10m |
| 2026-05-08 | CSZ9237 | SZX → LHW | May 8, 03:19 UTC | May 8, 03:35 UTC | 15m |
| 2026-05-07 | CSZ8984 | - | May 7, 14:10 UTC | May 7, 14:20 UTC | 10m |
| 2026-05-07 | CSZ8983 | - | May 7, 08:20 UTC | May 7, 08:35 UTC | 15m |
| 2026-05-07 | CSZ9302 | CGO → SZX | May 7, 05:55 UTC | May 7, 06:15 UTC | 20m |
| 2026-05-07 | CSZ9301 | SZX → CGO | May 7, 00:00 UTC | May 7, 00:10 UTC | 10m |
| 2026-05-06 | CSZ9125 | SZX → TSN | May 6, 06:45 UTC | May 6, 06:55 UTC | 10m |
| 2026-05-06 | CSZ9606 | JDZ → CAN | May 6, 04:50 UTC | May 6, 05:10 UTC | 20m |
| 2026-05-05 | CSZ9606 | JDZ → CAN | May 5, 15:40 UTC | May 6, 02:35 UTC | 10h 55m |
| 2026-05-05 | CSZ9605 | CAN → JDZ | May 5, 13:00 UTC | May 5, 13:15 UTC | 15m |
| 2026-05-05 | CSZ9616 | - | May 5, 11:30 UTC | May 5, 11:50 UTC | 20m |
| 2026-05-05 | CSZ9214 | XIY → SZX | May 5, 01:05 UTC | May 5, 01:15 UTC | 10m |
| 2026-04-30 | CSZ9868 | HGH → SZX | Apr 30, 10:00 UTC | Apr 30, 10:10 UTC | 10m |
| 2026-04-28 | CSZ9853 | SZX → NKG | Apr 28, 13:00 UTC | Apr 28, 13:10 UTC | 10m |
| 2026-04-28 | - | - | Apr 28, 11:35 UTC | Apr 28, 11:45 UTC | 10m |
| 2026-04-28 | CSZ9455 | SZX → KMG | Apr 28, 03:25 UTC | Apr 28, 03:40 UTC | 15m |
| 2026-04-23 | CSZ9876 | HAK → SZX | Apr 23, 01:30 UTC | Apr 23, 02:10 UTC | 40m |
| 2026-04-22 | CSZ9962 | - | Apr 22, 00:05 UTC | Apr 22, 00:15 UTC | 10m |
| 2026-04-19 | CSZ8993 | CAN → HAK | Apr 19, 14:05 UTC | Apr 19, 14: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-30AP page for operator, model, and routing details .