sensors Mode-S transponder
7BB0BC
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-2694 · BOEING 737-800
- Hex
- 7BB0BC
- Octal
- 36730274
- Decimal
- 8,106,172
- Country
- CN
- Tail
- B-2694
- Type
- B738
- Flights observed
- 73
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 17h ago
Last known position
Country allocation
The ICAO 24-bit address 7BB0BC 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 |
|---|---|---|---|
| CSN3631 | - | 11 | 2026-07-18 |
| CSN6079 | - | 7 | 2026-07-13 |
| CSN6080 | - | 6 | 2026-07-13 |
| CSN3780 | - | 5 | 2026-07-01 |
| CSN3356 | - | 5 | 2026-07-10 |
| CSN3355 | - | 4 | 2026-07-10 |
| CSN3016 | - | 4 | 2026-06-26 |
| CSN3015 | - | 4 | 2026-06-26 |
| CSN3872 | China Southern Airlines | 2 | 2026-05-19 |
| CSN3774 | - | 2 | 2026-07-10 |
| CSN3632 | - | 2 | 2026-07-18 |
| CSN8727 | China Southern Airlines | 1 | 2026-05-01 |
| CSN8706 | China Southern Airlines | 1 | 2026-06-11 |
| CSN8585 | China Southern Airlines | 1 | 2026-06-23 |
| CSN8519 | China Southern Airlines | 1 | 2026-05-29 |
| CSN8464 | China Southern Airlines | 1 | 2026-05-31 |
| CSN8463 | China Southern Airlines | 1 | 2026-05-30 |
| CSN8280 | - | 1 | 2026-06-29 |
| CSN8279 | - | 1 | 2026-06-24 |
| CSN8270 | - | 1 | 2026-07-07 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-18 | CSN5628 | HRB → WUH | Jul 18, 09:50 UTC | Jul 19, 01:40 UTC | 15h 50m |
| 2026-07-18 | CSN3632 | - | Jul 18, 05:20 UTC | Jul 19, 01:40 UTC | 20h 20m |
| 2026-07-18 | CSN3631 | - | Jul 18, 01:25 UTC | Jul 18, 14:15 UTC | 12h 51m |
| 2026-07-17 | CSN3631 | - | Jul 17, 08:25 UTC | Jul 18, 05:35 UTC | 21h 11m |
| 2026-07-17 | CSN3631 | - | Jul 17, 05:30 UTC | Jul 18, 01:39 UTC | 20h 10m |
| 2026-07-13 | CSN6224 | - | Jul 13, 11:50 UTC | Jul 13, 12:00 UTC | 10m |
| 2026-07-13 | CSN6080 | - | Jul 13, 05:25 UTC | Jul 13, 06:10 UTC | 45m |
| 2026-07-13 | CSN6079 | - | Jul 13, 03:15 UTC | Jul 13, 03:55 UTC | 40m |
| 2026-07-10 | CSN3774 | - | Jul 10, 23:05 UTC | Jul 10, 23:20 UTC | 15m |
| 2026-07-10 | CSN3356 | - | Jul 10, 11:40 UTC | Jul 10, 11:55 UTC | 15m |
| 2026-07-10 | CSN3355 | - | Jul 10, 09:55 UTC | Jul 10, 10:15 UTC | 20m |
| 2026-07-07 | CSN8270 | - | Jul 7, 08:35 UTC | Jul 7, 08:45 UTC | 10m |
| 2026-07-01 | CSN3780 | - | Jul 1, 01:15 UTC | Jul 1, 04:35 UTC | 3h 20m |
| 2026-06-29 | CSN8280 | - | Jun 29, 09:14 UTC | Jun 29, 13:00 UTC | 3h 45m |
| 2026-06-26 | CSN3016 | - | Jun 26, 11:14 UTC | Jun 26, 11:30 UTC | 15m |
| 2026-06-26 | CSN3015 | - | Jun 26, 09:24 UTC | Jun 26, 09:50 UTC | 25m |
| 2026-06-25 | CSN3780 | - | Jun 25, 09:29 UTC | Jun 26, 04:45 UTC | 19h 15m |
| 2026-06-24 | CSN8279 | - | Jun 24, 09:45 UTC | Jun 25, 02:10 UTC | 16h 25m |
| 2026-06-24 | CSN3780 | - | Jun 24, 04:30 UTC | Jun 25, 02:10 UTC | 21h 40m |
| 2026-06-24 | CSN3779 | CAN → NGB | Jun 24, 01:04 UTC | Jun 24, 13:14 UTC | 12h 10m |
| 2026-06-23 | CSN8585 | WUH → HLD | Jun 23, 09:54 UTC | Jun 24, 04:44 UTC | 18h 50m |
| 2026-06-23 | CSN3631 | - | Jun 23, 01:35 UTC | Jun 23, 10:10 UTC | 8h 35m |
| 2026-06-22 | CSN3631 | - | Jun 22, 12:30 UTC | Jun 23, 10:10 UTC | 21h 40m |
| 2026-06-22 | CSN3631 | - | Jun 22, 09:24 UTC | Jun 23, 05:54 UTC | 20h 30m |
| 2026-06-16 | CSN3368 | WUH → CAN | Jun 16, 01:45 UTC | Jun 16, 01:55 UTC | 10m |
| 2026-06-13 | CSN3356 | SZX → WUH | Jun 13, 14:10 UTC | Jun 13, 14:20 UTC | 10m |
| 2026-06-11 | CSN8706 | PKX → WUH | Jun 11, 09:45 UTC | Jun 11, 10:15 UTC | 30m |
| 2026-06-10 | CSN3356 | SZX → WUH | Jun 10, 11:30 UTC | Jun 10, 11:40 UTC | 10m |
| 2026-06-10 | CSN3355 | WUH → SZX | Jun 10, 09:00 UTC | Jun 10, 09:25 UTC | 25m |
| 2026-06-10 | CSN3780 | NGB → CAN | Jun 10, 04:20 UTC | Jun 10, 04:35 UTC | 15m |
| 2026-06-06 | CSN3780 | NGB → CAN | Jun 6, 00:55 UTC | Jun 6, 04:40 UTC | 3h 45m |
| 2026-06-05 | CSN3356 | SZX → WUH | Jun 5, 14:20 UTC | Jun 5, 14:35 UTC | 15m |
| 2026-06-05 | CSN3355 | WUH → SZX | Jun 5, 12:00 UTC | Jun 5, 12:20 UTC | 20m |
| 2026-06-05 | CSN6080 | ICN → WUH | Jun 5, 05:20 UTC | Jun 5, 05:50 UTC | 30m |
| 2026-06-05 | CSN6079 | WUH → ICN | Jun 5, 02:55 UTC | Jun 5, 03:25 UTC | 30m |
| 2026-06-03 | CSN3632 | HZA → SZX | Jun 3, 01:00 UTC | Jun 3, 05:40 UTC | 4h 40m |
| 2026-05-31 | CSN8464 | SZX → WUH | May 31, 00:20 UTC | May 31, 00:35 UTC | 15m |
| 2026-05-30 | CSN8463 | WUH → SZX | May 30, 17:20 UTC | May 30, 17:40 UTC | 20m |
| 2026-05-29 | CSN8519 | WUH → CAN | May 29, 18:00 UTC | May 29, 18:15 UTC | 15m |
| 2026-05-29 | CSN6080 | ICN → WUH | May 29, 05:35 UTC | May 29, 06:05 UTC | 30m |
| 2026-05-29 | CSN6079 | WUH → ICN | May 29, 03:00 UTC | May 29, 03:35 UTC | 35m |
| 2026-05-27 | CSN3631 | SZX → HZA | May 27, 01:09 UTC | May 27, 05:45 UTC | 4h 35m |
| 2026-05-22 | CSN3016 | TPE → WUH | May 22, 11:25 UTC | May 22, 11:45 UTC | 20m |
| 2026-05-22 | CSN3015 | WUH → TPE | May 22, 09:40 UTC | May 22, 10:15 UTC | 35m |
| 2026-05-19 | CSN3872 | NKG → CAN | May 19, 03:05 UTC | May 19, 03:15 UTC | 10m |
| 2026-05-13 | CSN3356 | SZX → WUH | May 13, 11:55 UTC | May 13, 12:05 UTC | 10m |
| 2026-05-13 | CSN3355 | WUH → SZX | May 13, 09:30 UTC | May 13, 09:55 UTC | 25m |
| 2026-05-09 | - | - | May 9, 04:00 UTC | May 9, 04:15 UTC | 15m |
| 2026-05-07 | CSN3631 | SZX → HZA | May 7, 12:25 UTC | May 8, 05:39 UTC | 17h 15m |
| 2026-05-07 | CSN3631 | SZX → HZA | May 7, 09:20 UTC | May 8, 05:39 UTC | 20h 19m |
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-2694 page for operator, model, and routing details .