sensors Mode-S transponder
780B6B
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-5856 · BOEING 737-800
- Hex
- 780B6B
- Octal
- 36005553
- Decimal
- 7,867,243
- Country
- CN
- Tail
- B-5856
- Type
- B738
- Flights observed
- 38
- Distinct callsigns
- 18
- Country
- CN
- Last broadcast
- 6d ago
Last known position
Country allocation
The ICAO 24-bit address 780B6B 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 18 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| CDG7629 | - | 7 | 2026-06-20 |
| CDG2320 | - | 7 | 2026-07-13 |
| CDG7630 | - | 5 | 2026-06-20 |
| CDG1177 | - | 3 | 2026-07-17 |
| CDG4910 | - | 2 | 2026-07-01 |
| CDG1178 | - | 2 | 2026-07-17 |
| CDG8407 | Shandong Airlines | 1 | 2026-05-07 |
| CDG7948 | Shandong Airlines | 1 | 2026-05-23 |
| CDG7946 | Shandong Airlines | 1 | 2026-04-23 |
| CDG7645 | Shandong Airlines | 1 | 2026-05-17 |
| CDG4912 | - | 1 | 2026-06-18 |
| CDG4911 | - | 1 | 2026-06-18 |
| CDG4652 | - | 1 | 2026-07-16 |
| CDG4632 | Shandong Airlines | 1 | 2026-05-02 |
| CDG4631 | Shandong Airlines | 1 | 2026-05-02 |
| CDG4618 | - | 1 | 2026-07-09 |
| CDG4617 | - | 1 | 2026-07-09 |
| CDG2319 | - | 1 | 2026-06-30 |
Recent flights last 38
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | CDG1178 | - | Jul 17, 08:59 UTC | Jul 17, 09:15 UTC | 15m |
| 2026-07-17 | CDG1177 | - | Jul 17, 04:04 UTC | Jul 17, 04:20 UTC | 15m |
| 2026-07-16 | CDG4652 | - | Jul 16, 13:25 UTC | Jul 16, 13:40 UTC | 15m |
| 2026-07-13 | CDG2320 | - | Jul 13, 23:40 UTC | Jul 13, 23:50 UTC | 10m |
| 2026-07-09 | CDG4618 | - | Jul 9, 13:25 UTC | Jul 9, 13:55 UTC | 30m |
| 2026-07-09 | CDG4617 | - | Jul 9, 11:30 UTC | Jul 9, 12:05 UTC | 35m |
| 2026-07-07 | CDG2320 | SHE → TYN | Jul 7, 23:30 UTC | Jul 7, 23:40 UTC | 10m |
| 2026-07-05 | CDG1178 | - | Jul 5, 08:55 UTC | Jul 5, 09:05 UTC | 10m |
| 2026-07-05 | CDG1177 | - | Jul 5, 06:40 UTC | Jul 5, 06:50 UTC | 10m |
| 2026-07-05 | CDG1177 | - | Jul 5, 03:55 UTC | Jul 5, 04:10 UTC | 15m |
| 2026-07-01 | CDG4910 | - | Jul 1, 04:55 UTC | Jul 1, 05:05 UTC | 10m |
| 2026-06-30 | CDG2319 | - | Jun 30, 08:35 UTC | Jun 30, 09:00 UTC | 25m |
| 2026-06-29 | CDG2320 | SHE → TYN | Jun 29, 23:29 UTC | Jun 29, 23:39 UTC | 10m |
| 2026-06-24 | CDG2320 | SHE → TYN | Jun 24, 23:29 UTC | Jun 24, 23:45 UTC | 15m |
| 2026-06-20 | CDG2320 | SHE → TYN | Jun 20, 23:29 UTC | Jun 20, 23:45 UTC | 15m |
| 2026-06-20 | CDG7630 | - | Jun 20, 08:39 UTC | Jun 20, 08:49 UTC | 10m |
| 2026-06-20 | CDG7629 | - | Jun 20, 06:45 UTC | Jun 20, 07:04 UTC | 20m |
| 2026-06-19 | CDG7630 | - | Jun 19, 11:04 UTC | Jun 19, 11:14 UTC | 10m |
| 2026-06-19 | CDG7629 | - | Jun 19, 08:34 UTC | Jun 19, 08:59 UTC | 25m |
| 2026-06-18 | CDG4912 | - | Jun 18, 14:10 UTC | Jun 18, 14:25 UTC | 15m |
| 2026-06-18 | CDG4911 | - | Jun 18, 11:30 UTC | Jun 18, 11:45 UTC | 15m |
| 2026-06-13 | CDG7630 | SZX → YNT | Jun 13, 09:00 UTC | Jun 13, 09:10 UTC | 10m |
| 2026-06-13 | CDG7629 | - | Jun 13, 07:20 UTC | Jun 13, 07:30 UTC | 10m |
| 2026-05-27 | CDG4910 | ZUH → KHN | May 27, 04:14 UTC | May 27, 04:30 UTC | 15m |
| 2026-05-23 | CDG7948 | WUH → SHE | May 23, 06:20 UTC | May 23, 06:30 UTC | 10m |
| 2026-05-17 | CDG7645 | CGQ → YNT | May 17, 15:01 UTC | May 17, 15:31 UTC | 30m |
| 2026-05-07 | CDG8407 | HET → TNA | May 7, 09:10 UTC | May 7, 09:35 UTC | 25m |
| 2026-05-04 | CDG7630 | SZX → YNT | May 4, 08:45 UTC | May 4, 08:55 UTC | 10m |
| 2026-05-04 | CDG7629 | YNT → SZX | May 4, 07:10 UTC | May 4, 07:30 UTC | 20m |
| 2026-05-02 | CDG4632 | HKG → TAO | May 2, 09:50 UTC | May 2, 10:55 UTC | 1h 5m |
| 2026-05-02 | CDG4631 | TAO → HKG | May 2, 06:30 UTC | May 2, 07:55 UTC | 1h 25m |
| 2026-04-28 | CDG7630 | SZX → YNT | Apr 28, 08:40 UTC | Apr 28, 08:50 UTC | 10m |
| 2026-04-28 | CDG7629 | YNT → SZX | Apr 28, 07:00 UTC | Apr 28, 07:20 UTC | 20m |
| 2026-04-23 | CDG2320 | SHE → TYN | Apr 23, 23:25 UTC | Apr 23, 23:35 UTC | 10m |
| 2026-04-23 | CDG7946 | SHE → XMN | Apr 23, 08:30 UTC | Apr 23, 09:10 UTC | 40m |
| 2026-04-21 | CDG7629 | YNT → SZX | Apr 21, 08:30 UTC | Apr 21, 08:40 UTC | 10m |
| 2026-04-19 | CDG2320 | SHE → TYN | Apr 19, 23:25 UTC | Apr 19, 23:35 UTC | 10m |
| 2026-04-17 | CDG7629 | YNT → SZX | Apr 17, 07:55 UTC | Apr 17, 08:05 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-5856 page for operator, model, and routing details .