sensors Mode-S transponder
78097F
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-5713 · BOEING 737-800
- Hex
- 78097F
- Octal
- 36004577
- Decimal
- 7,866,751
- Country
- CN
- Tail
- B-5713
- Type
- B738
- Flights observed
- 53
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 11h ago
Last known position
Country allocation
The ICAO 24-bit address 78097F 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 |
|---|---|---|---|
| CHH7648 | - | 3 | 2026-07-11 |
| CHH6394 | - | 3 | 2026-07-03 |
| CHH7751 | Hainan Airlines | 2 | 2026-07-07 |
| CHH7746 | - | 2 | 2026-07-04 |
| CHH7741 | Hainan Airlines | 2 | 2026-06-13 |
| CHH7732 | Hainan Airlines | 2 | 2026-05-01 |
| CHH7726 | Hainan Airlines | 2 | 2026-04-15 |
| CHH7535 | - | 2 | 2026-07-09 |
| CHH7386 | Hainan Airlines | 2 | 2026-05-10 |
| CHH7328 | Hainan Airlines | 2 | 2026-05-18 |
| CHH7026 | Hainan Airlines | 2 | 2026-06-10 |
| CHH7852 | - | 1 | 2026-06-30 |
| CHH7809 | - | 1 | 2026-07-13 |
| CHH7776 | Hainan Airlines | 1 | 2026-07-05 |
| CHH7775 | - | 1 | 2026-07-05 |
| CHH7774 | Hainan Airlines | 1 | 2026-07-06 |
| CHH7773 | - | 1 | 2026-07-06 |
| CHH7771 | - | 1 | 2026-07-06 |
| CHH7745 | - | 1 | 2026-07-04 |
| CHH7744 | - | 1 | 2026-07-01 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | CHH7644 | - | Jul 14, 08:30 UTC | Jul 14, 08:40 UTC | 10m |
| 2026-07-13 | CHH7809 | - | Jul 13, 06:45 UTC | Jul 13, 07:05 UTC | 20m |
| 2026-07-12 | CHH7042 | - | Jul 12, 07:50 UTC | Jul 12, 13:25 UTC | 5h 35m |
| 2026-07-11 | CHH7648 | - | Jul 11, 11:50 UTC | Jul 12, 07:50 UTC | 20h 0m |
| 2026-07-11 | CHH7648 | - | Jul 11, 11:40 UTC | Jul 12, 07:50 UTC | 20h 10m |
| 2026-07-09 | CHH7535 | - | Jul 9, 15:40 UTC | Jul 9, 16:00 UTC | 20m |
| 2026-07-09 | CHH6218 | XIY → PEK | Jul 9, 12:50 UTC | Jul 9, 13:15 UTC | 25m |
| 2026-07-09 | CHH7569 | - | Jul 9, 02:40 UTC | Jul 9, 03:00 UTC | 20m |
| 2026-07-08 | CHH7522 | - | Jul 8, 14:35 UTC | Jul 8, 14:45 UTC | 10m |
| 2026-07-07 | - | - | Jul 7, 10:00 UTC | Jul 7, 10:10 UTC | 10m |
| 2026-07-07 | CHH7751 | SZX → CTU | Jul 7, 01:25 UTC | Jul 7, 01:35 UTC | 10m |
| 2026-07-06 | CHH7774 | KWE → SZX | Jul 6, 21:30 UTC | Jul 6, 21:40 UTC | 10m |
| 2026-07-06 | CHH7773 | - | Jul 6, 15:40 UTC | Jul 6, 15:50 UTC | 10m |
| 2026-07-06 | CHH7771 | - | Jul 6, 07:55 UTC | Jul 6, 08:05 UTC | 10m |
| 2026-07-05 | CHH7751 | SZX → CTU | Jul 5, 22:25 UTC | Jul 5, 22:35 UTC | 10m |
| 2026-07-05 | CHH7776 | TYN → SZX | Jul 5, 18:35 UTC | Jul 5, 18:50 UTC | 15m |
| 2026-07-05 | CHH7775 | - | Jul 5, 05:55 UTC | Jul 5, 06:05 UTC | 10m |
| 2026-07-04 | CHH7746 | - | Jul 4, 18:35 UTC | Jul 4, 18:55 UTC | 20m |
| 2026-07-04 | CHH7746 | - | Jul 4, 09:10 UTC | Jul 4, 09:35 UTC | 25m |
| 2026-07-04 | CHH7745 | - | Jul 4, 02:35 UTC | Jul 4, 02:45 UTC | 10m |
| 2026-07-03 | CHH6394 | - | Jul 3, 15:55 UTC | Jul 3, 16:05 UTC | 10m |
| 2026-07-02 | CHH7393 | - | Jul 2, 00:15 UTC | Jul 2, 00:25 UTC | 10m |
| 2026-07-01 | CHH7744 | - | Jul 1, 16:15 UTC | Jul 1, 16:40 UTC | 25m |
| 2026-06-30 | CHH7852 | - | Jun 30, 17:00 UTC | Jun 30, 17:10 UTC | 10m |
| 2026-06-14 | CHH7648 | SHE → HAK | Jun 14, 05:15 UTC | Jun 14, 14:20 UTC | 9h 5m |
| 2026-06-13 | CHH7741 | SZX → KWE | Jun 13, 03:50 UTC | Jun 13, 04:00 UTC | 9m |
| 2026-06-10 | CHH7026 | SZX → HAK | Jun 10, 13:45 UTC | Jun 10, 13:55 UTC | 10m |
| 2026-05-18 | CHH7528 | HRB → SYX | May 18, 15:50 UTC | May 19, 10:35 UTC | 18h 44m |
| 2026-05-18 | CHH7328 | CTU → SZX | May 18, 15:40 UTC | May 19, 10:35 UTC | 18h 54m |
| 2026-05-18 | CHH7328 | CTU → SZX | May 18, 00:55 UTC | May 18, 16:00 UTC | 15h 5m |
| 2026-05-10 | CHH7386 | HGH → SYX | May 10, 05:04 UTC | May 10, 10:19 UTC | 5h 15m |
| 2026-05-09 | CHH7386 | HGH → SYX | May 9, 09:55 UTC | May 10, 05:14 UTC | 19h 20m |
| 2026-05-09 | CHH7385 | SYX → HGH | May 9, 05:30 UTC | May 9, 10:10 UTC | 4h 40m |
| 2026-05-08 | CHH7535 | PEK → CSX | May 8, 15:25 UTC | May 9, 10:10 UTC | 18h 45m |
| 2026-05-08 | CHH7188 | WUH → PEK | May 8, 12:30 UTC | May 8, 12:39 UTC | 10m |
| 2026-05-08 | CHH7187 | PEK → WUH | May 8, 00:34 UTC | May 8, 00:54 UTC | 20m |
| 2026-05-07 | CHH7645 | - | May 7, 11:15 UTC | May 7, 11:30 UTC | 15m |
| 2026-05-07 | CHH7235 | CAN → CGO | May 7, 03:00 UTC | May 7, 03:20 UTC | 20m |
| 2026-05-06 | CHH6394 | - | May 6, 15:15 UTC | May 6, 15:25 UTC | 10m |
| 2026-05-02 | CHH7026 | SZX → HAK | May 2, 12:35 UTC | May 2, 12:45 UTC | 10m |
| 2026-05-02 | CHH7375 | SZX → TFU | May 2, 05:05 UTC | May 2, 05:15 UTC | 10m |
| 2026-05-01 | CHH7737 | SZX → NNY | May 1, 23:00 UTC | May 1, 23:10 UTC | 10m |
| 2026-05-01 | CHH7732 | SZX → SYX | May 1, 15:25 UTC | May 1, 15:35 UTC | 10m |
| 2026-04-29 | CHH7256 | NKG → SZX | Apr 29, 18:10 UTC | Apr 29, 18:30 UTC | 20m |
| 2026-04-29 | CHH7175 | SZX → TFU | Apr 29, 00:05 UTC | Apr 29, 00:20 UTC | 15m |
| 2026-04-28 | CHH7732 | SZX → SYX | Apr 28, 16:05 UTC | Apr 28, 16:20 UTC | 15m |
| 2026-04-27 | CHH7731 | SYX → SZX | Apr 27, 23:45 UTC | Apr 27, 23:55 UTC | 10m |
| 2026-04-18 | CHH6394 | - | Apr 18, 14:05 UTC | Apr 18, 14:20 UTC | 15m |
| 2026-04-15 | CHH7741 | SZX → KWE | Apr 15, 04:00 UTC | Apr 15, 04:10 UTC | 10m |
| 2026-04-15 | CHH7726 | PVG → SZX | Apr 15, 01:10 UTC | Apr 15, 01:55 UTC | 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-5713 page for operator, model, and routing details .