sensors Mode-S transponder
78025A
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-5705 · BOEING 737-800
- Hex
- 78025A
- Octal
- 36001132
- Decimal
- 7,864,922
- Country
- CN
- Tail
- B-5705
- Type
- B738
- Flights observed
- 55
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 78025A 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 |
|---|---|---|---|
| CSH9535 | - | 8 | 2026-07-02 |
| CSH9536 | - | 7 | 2026-07-08 |
| CSH9251 | - | 3 | 2026-06-25 |
| CSH9469 | - | 2 | 2026-07-13 |
| CSH9357 | Shanghai Airlines | 2 | 2026-06-01 |
| CSH9252 | - | 2 | 2026-06-25 |
| CSH9130 | - | 2 | 2026-06-28 |
| CSH834 | Shanghai Airlines | 2 | 2026-06-10 |
| CSH9559 | - | 1 | 2026-05-17 |
| CSH9503 | - | 1 | 2026-07-04 |
| CSH9477 | - | 1 | 2026-06-27 |
| CSH9470 | - | 1 | 2026-07-12 |
| CSH9449 | - | 1 | 2026-06-21 |
| CSH9435 | Shanghai Airlines | 1 | 2026-05-21 |
| CSH9362 | Shanghai Airlines | 1 | 2026-04-30 |
| CSH9361 | Shanghai Airlines | 1 | 2026-04-30 |
| CSH9358 | Shanghai Airlines | 1 | 2026-06-01 |
| CSH9290 | - | 1 | 2026-07-08 |
| CSH9258 | - | 1 | 2026-05-27 |
| CSH9134 | Shanghai Airlines | 1 | 2026-05-18 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | CSH9469 | - | Jul 13, 10:55 UTC | Jul 13, 11:20 UTC | 25m |
| 2026-07-12 | CSH9470 | - | Jul 12, 14:35 UTC | Jul 13, 09:15 UTC | 18h 40m |
| 2026-07-08 | CSH9290 | - | Jul 8, 11:00 UTC | Jul 9, 06:30 UTC | 19h 30m |
| 2026-07-08 | CSH9536 | - | Jul 8, 09:05 UTC | Jul 9, 06:30 UTC | 21h 25m |
| 2026-07-08 | CSH9536 | - | Jul 8, 06:35 UTC | Jul 9, 06:30 UTC | 23h 55m |
| 2026-07-08 | CSH9536 | - | Jul 8, 06:20 UTC | Jul 8, 11:00 UTC | 4h 40m |
| 2026-07-07 | CSH9536 | - | Jul 7, 10:50 UTC | Jul 8, 10:05 UTC | 23h 15m |
| 2026-07-04 | CSH9503 | - | Jul 4, 08:30 UTC | Jul 4, 15:15 UTC | 6h 45m |
| 2026-07-02 | CSH9535 | - | Jul 2, 06:20 UTC | Jul 2, 10:40 UTC | 4h 20m |
| 2026-06-30 | CSH802 | - | Jun 30, 05:10 UTC | Jun 30, 05:35 UTC | 25m |
| 2026-06-30 | CSH801 | - | Jun 30, 03:25 UTC | Jun 30, 04:00 UTC | 35m |
| 2026-06-28 | CSH9130 | - | Jun 28, 10:55 UTC | Jun 29, 04:20 UTC | 17h 25m |
| 2026-06-27 | CSH9477 | - | Jun 27, 05:49 UTC | Jun 27, 09:04 UTC | 3h 15m |
| 2026-06-25 | CSH9252 | - | Jun 25, 07:39 UTC | Jun 25, 07:49 UTC | 10m |
| 2026-06-25 | CSH9251 | - | Jun 25, 04:25 UTC | Jun 25, 04:40 UTC | 15m |
| 2026-06-22 | CSH9536 | - | Jun 22, 09:14 UTC | Jun 22, 11:09 UTC | 1h 55m |
| 2026-06-22 | CSH9535 | - | Jun 22, 06:00 UTC | Jun 22, 06:54 UTC | 55m |
| 2026-06-21 | CSH9449 | - | Jun 21, 03:30 UTC | Jun 21, 04:10 UTC | 40m |
| 2026-06-20 | CSH9251 | - | Jun 20, 04:29 UTC | Jun 20, 07:34 UTC | 3h 5m |
| 2026-06-14 | CSH9072 | - | Jun 14, 04:20 UTC | Jun 14, 13:05 UTC | 8h 45m |
| 2026-06-11 | CSH9469 | - | Jun 11, 08:45 UTC | Jun 11, 11:55 UTC | 3h 10m |
| 2026-06-10 | CSH834 | BKK → PVG | Jun 10, 10:35 UTC | Jun 11, 09:00 UTC | 22h 25m |
| 2026-06-10 | CSH834 | BKK → PVG | Jun 10, 10:10 UTC | Jun 10, 12:30 UTC | 2h 20m |
| 2026-06-10 | CSH833 | PVG → BKK | Jun 10, 06:00 UTC | Jun 10, 08:25 UTC | 2h 25m |
| 2026-06-05 | CSH9536 | SYX → PVG | Jun 5, 09:15 UTC | Jun 5, 10:15 UTC | 1h 0m |
| 2026-06-04 | CSH810 | HKG → SHA | Jun 4, 11:10 UTC | Jun 5, 06:05 UTC | 18h 55m |
| 2026-06-04 | CSH809 | SHA → HKG | Jun 4, 08:30 UTC | Jun 4, 09:05 UTC | 35m |
| 2026-06-01 | CSH9358 | ZUH → PVG | Jun 1, 11:45 UTC | Jun 1, 12:00 UTC | 15m |
| 2026-06-01 | CSH9357 | PVG → ZUH | Jun 1, 02:55 UTC | Jun 1, 09:25 UTC | 6h 30m |
| 2026-05-31 | CSH9357 | PVG → ZUH | May 31, 12:55 UTC | Jun 1, 09:25 UTC | 20h 30m |
| 2026-05-27 | CSH9258 | - | May 27, 10:10 UTC | May 27, 10:30 UTC | 20m |
| 2026-05-25 | CSH9130 | HLD → PVG | May 25, 11:10 UTC | May 26, 03:40 UTC | 16h 29m |
| 2026-05-21 | CSH9435 | CGO → CGQ | May 21, 04:15 UTC | May 21, 04:35 UTC | 20m |
| 2026-05-19 | CSH886 | KUL → PVG | May 19, 08:40 UTC | May 19, 12:40 UTC | 4h 0m |
| 2026-05-19 | CSH885 | PVG → KUL | May 19, 02:55 UTC | May 19, 06:50 UTC | 3h 55m |
| 2026-05-18 | CSH9134 | BAV → PVG | May 18, 07:25 UTC | May 18, 07:45 UTC | 20m |
| 2026-05-17 | CSH9559 | - | May 17, 01:00 UTC | May 17, 05:20 UTC | 4h 20m |
| 2026-05-14 | CSH9252 | HAK → SHA | May 14, 09:35 UTC | May 14, 10:35 UTC | 1h 0m |
| 2026-05-09 | CSH9535 | PVG → SYX | May 9, 05:50 UTC | May 9, 09:50 UTC | 4h 0m |
| 2026-05-08 | CSH9535 | PVG → SYX | May 8, 10:59 UTC | May 9, 09:50 UTC | 22h 50m |
| 2026-05-07 | CSH9535 | PVG → SYX | May 7, 05:50 UTC | May 7, 11:05 UTC | 5h 15m |
| 2026-05-06 | CSH9535 | PVG → SYX | May 6, 07:35 UTC | May 7, 06:10 UTC | 22h 34m |
| 2026-05-06 | CSH9251 | PVG → HAK | May 6, 04:40 UTC | May 6, 07:50 UTC | 3h 10m |
| 2026-05-05 | CSH9536 | SYX → PVG | May 5, 09:40 UTC | May 6, 07:50 UTC | 22h 10m |
| 2026-05-05 | CSH9535 | PVG → SYX | May 5, 05:40 UTC | May 5, 09:50 UTC | 4h 10m |
| 2026-05-04 | CSH9535 | PVG → SYX | May 4, 12:00 UTC | May 5, 09:50 UTC | 21h 51m |
| 2026-04-30 | CSH9362 | ZUH → SHA | Apr 30, 13:45 UTC | Apr 30, 13:55 UTC | 10m |
| 2026-04-30 | CSH9361 | SHA → ZUH | Apr 30, 11:25 UTC | Apr 30, 11:50 UTC | 25m |
| 2026-04-30 | CSH818 | MFM → SHA | Apr 30, 06:05 UTC | Apr 30, 07:05 UTC | 1h 0m |
| 2026-04-30 | CSH817 | SHA → MFM | Apr 30, 04:05 UTC | Apr 30, 04:20 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-5705 page for operator, model, and routing details .