sensors Mode-S transponder
78150A
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-205Z · BOEING 737-800
- Hex
- 78150A
- Octal
- 36012412
- Decimal
- 7,869,706
- Country
- CN
- Tail
- B-205Z
- Type
- B738
- Flights observed
- 49
- Distinct callsigns
- 19
- Country
- CN
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 78150A 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 19 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| CSH9333 | - | 7 | 2026-06-15 |
| CSH9334 | Shanghai Airlines | 5 | 2026-05-25 |
| CSH857 | Shanghai Airlines | 4 | 2026-06-09 |
| CSH828 | Shanghai Airlines | 4 | 2026-06-12 |
| CSH805 | Shanghai Airlines | 4 | 2026-06-01 |
| CSH839 | Shanghai Airlines | 3 | 2026-06-08 |
| CSH827 | - | 3 | 2026-06-12 |
| CSH810 | - | 3 | 2026-06-19 |
| CSH809 | - | 3 | 2026-06-19 |
| CSH851 | - | 2 | 2026-06-19 |
| CSH840 | Shanghai Airlines | 2 | 2026-06-01 |
| CSH806 | Shanghai Airlines | 2 | 2026-05-28 |
| CSH9537 | Shanghai Airlines | 1 | 2026-04-27 |
| CSH9535 | Shanghai Airlines | 1 | 2026-05-19 |
| CSH856 | Shanghai Airlines | 1 | 2026-05-30 |
| CSH855 | Shanghai Airlines | 1 | 2026-05-30 |
| CSH852 | - | 1 | 2026-06-19 |
| CSH830 | - | 1 | 2026-06-13 |
| CSH829 | - | 1 | 2026-06-13 |
Recent flights last 49
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-19 | CSH810 | - | Jun 19, 11:14 UTC | Jun 19, 12:25 UTC | 1h 10m |
| 2026-06-19 | CSH809 | - | Jun 19, 09:04 UTC | Jun 19, 09:24 UTC | 20m |
| 2026-06-19 | CSH852 | - | Jun 19, 03:29 UTC | Jun 19, 03:55 UTC | 25m |
| 2026-06-19 | CSH851 | - | Jun 19, 01:34 UTC | Jun 19, 02:14 UTC | 40m |
| 2026-06-15 | CSH9333 | - | Jun 15, 09:40 UTC | Jun 15, 10:55 UTC | 1h 15m |
| 2026-06-13 | CSH830 | - | Jun 13, 09:00 UTC | Jun 13, 09:25 UTC | 25m |
| 2026-06-13 | CSH829 | - | Jun 13, 06:55 UTC | Jun 13, 07:10 UTC | 15m |
| 2026-06-12 | CSH828 | ICN → PVG | Jun 12, 09:55 UTC | Jun 13, 01:25 UTC | 15h 30m |
| 2026-06-12 | CSH827 | - | Jun 12, 07:50 UTC | Jun 12, 08:30 UTC | 40m |
| 2026-06-09 | CSH857 | PVG → HKT | Jun 9, 11:20 UTC | Jun 9, 19:20 UTC | 8h 0m |
| 2026-06-08 | CSH857 | PVG → HKT | Jun 8, 17:30 UTC | Jun 9, 13:55 UTC | 20h 25m |
| 2026-06-08 | CSH857 | PVG → HKT | Jun 8, 15:10 UTC | Jun 9, 13:55 UTC | 22h 45m |
| 2026-06-08 | CSH839 | PVG → BKK | Jun 8, 04:40 UTC | Jun 8, 13:35 UTC | 8h 55m |
| 2026-06-07 | CSH828 | ICN → PVG | Jun 7, 09:40 UTC | Jun 8, 04:40 UTC | 19h 0m |
| 2026-06-07 | CSH827 | PVG → ICN | Jun 7, 07:55 UTC | Jun 7, 08:25 UTC | 30m |
| 2026-06-05 | CSH828 | ICN → PVG | Jun 5, 09:30 UTC | Jun 6, 04:50 UTC | 19h 20m |
| 2026-06-05 | CSH827 | PVG → ICN | Jun 5, 07:45 UTC | Jun 5, 08:20 UTC | 35m |
| 2026-06-02 | CSH828 | ICN → PVG | Jun 2, 09:45 UTC | Jun 2, 10:10 UTC | 25m |
| 2026-06-01 | CSH840 | BKK → PVG | Jun 1, 15:20 UTC | Jun 2, 08:35 UTC | 17h 15m |
| 2026-06-01 | CSH839 | PVG → BKK | Jun 1, 05:45 UTC | Jun 1, 13:25 UTC | 7h 40m |
| 2026-06-01 | CSH805 | PVG → MFM | Jun 1, 03:50 UTC | Jun 1, 04:10 UTC | 20m |
| 2026-06-01 | CSH805 | PVG → MFM | Jun 1, 02:55 UTC | Jun 1, 03:20 UTC | 25m |
| 2026-05-30 | CSH856 | BKK → PVG | May 30, 12:20 UTC | May 30, 14:40 UTC | 2h 20m |
| 2026-05-30 | CSH855 | PVG → BKK | May 30, 03:10 UTC | May 30, 10:45 UTC | 7h 35m |
| 2026-05-28 | CSH840 | BKK → PVG | May 28, 15:15 UTC | May 28, 17:35 UTC | 2h 20m |
| 2026-05-28 | CSH839 | PVG → BKK | May 28, 06:35 UTC | May 28, 13:40 UTC | 7h 5m |
| 2026-05-28 | CSH806 | MFM → PVG | May 28, 05:35 UTC | May 28, 05:55 UTC | 20m |
| 2026-05-27 | CSH857 | PVG → HKT | May 27, 11:25 UTC | May 28, 04:05 UTC | 16h 40m |
| 2026-05-25 | CSH9334 | SZX → SHA | May 25, 09:40 UTC | May 25, 09:50 UTC | 10m |
| 2026-05-25 | CSH9333 | SHA → SZX | May 25, 06:50 UTC | May 25, 07:10 UTC | 20m |
| 2026-05-24 | CSH810 | HKG → SHA | May 24, 12:05 UTC | May 24, 13:15 UTC | 1h 10m |
| 2026-05-24 | CSH809 | SHA → HKG | May 24, 03:30 UTC | May 24, 10:20 UTC | 6h 50m |
| 2026-05-24 | CSH851 | SHA → TSA | May 24, 01:35 UTC | May 24, 02:00 UTC | 25m |
| 2026-05-23 | CSH810 | HKG → SHA | May 23, 11:15 UTC | May 23, 12:05 UTC | 50m |
| 2026-05-23 | CSH809 | SHA → HKG | May 23, 09:10 UTC | May 23, 09:30 UTC | 20m |
| 2026-05-22 | CSH9334 | SZX → SHA | May 22, 10:55 UTC | May 22, 11:05 UTC | 10m |
| 2026-05-22 | CSH9333 | SHA → SZX | May 22, 08:10 UTC | May 22, 08:30 UTC | 20m |
| 2026-05-19 | CSH9535 | PVG → SYX | May 19, 05:40 UTC | May 19, 10:00 UTC | 4h 20m |
| 2026-05-14 | CSH9334 | SZX → SHA | May 14, 12:35 UTC | May 14, 12:50 UTC | 15m |
| 2026-05-14 | CSH9333 | SHA → SZX | May 14, 10:15 UTC | May 14, 10:35 UTC | 20m |
| 2026-05-13 | CSH9334 | SZX → SHA | May 13, 10:00 UTC | May 13, 10:10 UTC | 10m |
| 2026-05-13 | CSH9333 | SHA → SZX | May 13, 07:25 UTC | May 13, 07:45 UTC | 20m |
| 2026-05-12 | CSH9334 | SZX → SHA | May 12, 09:50 UTC | May 12, 10:00 UTC | 10m |
| 2026-05-12 | CSH9333 | SHA → SZX | May 12, 06:50 UTC | May 12, 07:10 UTC | 20m |
| 2026-05-07 | CSH806 | MFM → PVG | May 7, 05:40 UTC | May 7, 06:40 UTC | 1h 0m |
| 2026-05-07 | CSH805 | PVG → MFM | May 7, 04:00 UTC | May 7, 04:15 UTC | 15m |
| 2026-05-07 | CSH805 | PVG → MFM | May 7, 03:00 UTC | May 7, 03:20 UTC | 20m |
| 2026-04-30 | CSH9333 | SHA → SZX | Apr 30, 06:55 UTC | Apr 30, 07:10 UTC | 15m |
| 2026-04-27 | CSH9537 | SHA → SYX | Apr 27, 00:40 UTC | Apr 27, 05:25 UTC | 4h 45m |
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-205Z page for operator, model, and routing details .