sensors Mode-S transponder
780E6F
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-6108 · BOEING 737-800
- Hex
- 780E6F
- Octal
- 36007157
- Decimal
- 7,868,015
- Country
- CN
- Tail
- B-6108
- Type
- B738
- Flights observed
- 43
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address 780E6F 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 |
|---|---|---|---|
| CSH9469 | - | 6 | 2026-07-01 |
| CSH9559 | - | 4 | 2026-06-29 |
| CSH9130 | - | 3 | 2026-06-20 |
| CSH863 | Shanghai Airlines | 3 | 2026-04-17 |
| CSH840 | - | 3 | 2026-06-26 |
| CSH9470 | - | 2 | 2026-05-12 |
| CSH9435 | - | 2 | 2026-07-13 |
| CSH9080 | Shanghai Airlines | 2 | 2026-05-16 |
| CSH9064 | Shanghai Airlines | 2 | 2026-04-23 |
| CSH864 | Shanghai Airlines | 2 | 2026-04-18 |
| CSH839 | - | 2 | 2026-06-26 |
| CSH9503 | - | 1 | 2026-06-30 |
| CSH9477 | - | 1 | 2026-06-22 |
| CSH9310 | Shanghai Airlines | 1 | 2026-04-21 |
| CSH9297 | - | 1 | 2026-06-24 |
| CSH9124 | Shanghai Airlines | 1 | 2026-04-28 |
| CSH875 | - | 1 | 2026-07-14 |
| CSH866 | - | 1 | 2026-07-07 |
| CSH865 | - | 1 | 2026-07-07 |
| CSH831 | - | 1 | 2026-07-10 |
Recent flights last 43
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | CSH875 | - | Jul 14, 11:15 UTC | Jul 15, 03:25 UTC | 16h 9m |
| 2026-07-13 | CSH9435 | - | Jul 13, 04:20 UTC | Jul 13, 04:35 UTC | 15m |
| 2026-07-10 | CSH831 | - | Jul 10, 12:20 UTC | Jul 10, 20:20 UTC | 8h 0m |
| 2026-07-07 | CSH866 | - | Jul 7, 12:25 UTC | Jul 7, 16:35 UTC | 4h 10m |
| 2026-07-07 | CSH865 | - | Jul 7, 06:40 UTC | Jul 7, 11:00 UTC | 4h 20m |
| 2026-07-01 | CSH9469 | - | Jul 1, 11:50 UTC | Jul 2, 03:55 UTC | 16h 5m |
| 2026-06-30 | CSH9469 | - | Jun 30, 23:40 UTC | Jul 1, 15:00 UTC | 15h 20m |
| 2026-06-30 | CSH9503 | - | Jun 30, 15:50 UTC | Jul 1, 12:05 UTC | 20h 15m |
| 2026-06-29 | CSH9559 | - | Jun 29, 01:14 UTC | Jun 29, 04:30 UTC | 3h 15m |
| 2026-06-26 | CSH840 | - | Jun 26, 15:10 UTC | Jun 26, 17:35 UTC | 2h 25m |
| 2026-06-26 | CSH839 | - | Jun 26, 04:24 UTC | Jun 26, 13:34 UTC | 9h 10m |
| 2026-06-26 | CSH801 | - | Jun 26, 02:40 UTC | Jun 26, 03:05 UTC | 25m |
| 2026-06-24 | CSH9469 | - | Jun 24, 23:40 UTC | Jun 25, 12:19 UTC | 12h 40m |
| 2026-06-24 | CSH9297 | - | Jun 24, 14:34 UTC | Jun 24, 15:00 UTC | 25m |
| 2026-06-22 | CSH9477 | - | Jun 22, 05:40 UTC | Jun 22, 08:54 UTC | 3h 15m |
| 2026-06-20 | CSH9130 | - | Jun 20, 11:30 UTC | Jun 20, 11:44 UTC | 15m |
| 2026-06-17 | CSH9130 | - | Jun 17, 14:45 UTC | Jun 18, 11:20 UTC | 20h 35m |
| 2026-06-17 | CSH9130 | - | Jun 17, 12:30 UTC | Jun 18, 11:20 UTC | 22h 50m |
| 2026-06-03 | CSH9469 | - | Jun 3, 08:55 UTC | Jun 3, 12:05 UTC | 3h 10m |
| 2026-05-28 | CSH9559 | - | May 28, 05:20 UTC | May 28, 10:50 UTC | 5h 30m |
| 2026-05-27 | CSH9559 | - | May 27, 14:35 UTC | May 28, 10:50 UTC | 20h 15m |
| 2026-05-20 | CSH9435 | CGO → CGQ | May 20, 04:20 UTC | May 20, 04:35 UTC | 15m |
| 2026-05-16 | CSH9080 | CGQ → PVG | May 16, 23:40 UTC | May 17, 04:15 UTC | 4h 35m |
| 2026-05-13 | CSH9469 | - | May 13, 11:00 UTC | May 14, 06:50 UTC | 19h 50m |
| 2026-05-12 | CSH9470 | - | May 12, 23:50 UTC | May 13, 08:55 UTC | 9h 5m |
| 2026-05-10 | CSH9469 | - | May 10, 10:49 UTC | May 10, 11:20 UTC | 30m |
| 2026-05-10 | CSH9470 | - | May 10, 08:35 UTC | May 10, 08:50 UTC | 15m |
| 2026-05-05 | CSH9559 | - | May 5, 06:20 UTC | May 5, 09:45 UTC | 3h 25m |
| 2026-05-02 | CSH840 | BKK → PVG | May 2, 17:10 UTC | May 3, 11:15 UTC | 18h 4m |
| 2026-05-02 | CSH840 | BKK → PVG | May 2, 15:15 UTC | May 3, 11:15 UTC | 19h 59m |
| 2026-05-02 | CSH839 | PVG → BKK | May 2, 04:10 UTC | May 2, 14:00 UTC | 9h 50m |
| 2026-05-02 | CSH802 | TSA → PVG | May 2, 02:05 UTC | May 2, 02:45 UTC | 40m |
| 2026-04-29 | CSH9080 | CGQ → PVG | Apr 29, 23:35 UTC | Apr 30, 00:10 UTC | 35m |
| 2026-04-28 | CSH9124 | TVS → PVG | Apr 28, 03:30 UTC | Apr 28, 14:55 UTC | 11h 25m |
| 2026-04-23 | CSH9064 | HRB → PVG | Apr 23, 10:40 UTC | Apr 23, 11:15 UTC | 35m |
| 2026-04-21 | CSH9310 | CAN → PVG | Apr 21, 05:40 UTC | Apr 21, 05:50 UTC | 10m |
| 2026-04-20 | CSH830 | PUS → PVG | Apr 20, 00:45 UTC | Apr 20, 09:10 UTC | 8h 25m |
| 2026-04-18 | CSH864 | KUL → PVG | Apr 18, 02:30 UTC | Apr 18, 03:05 UTC | 35m |
| 2026-04-17 | CSH864 | KUL → PVG | Apr 17, 23:15 UTC | Apr 18, 15:00 UTC | 15h 45m |
| 2026-04-17 | CSH863 | PVG → KUL | Apr 17, 21:25 UTC | Apr 17, 21:55 UTC | 30m |
| 2026-04-17 | CSH863 | PVG → KUL | Apr 17, 20:20 UTC | Apr 17, 21:20 UTC | 1h 0m |
| 2026-04-17 | CSH863 | PVG → KUL | Apr 17, 17:25 UTC | Apr 17, 18:35 UTC | 1h 10m |
| 2026-04-17 | CSH9064 | HRB → PVG | Apr 17, 10:55 UTC | Apr 17, 11:10 UTC | 15m |
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-6108 page for operator, model, and routing details .