sensors Mode-S transponder
780B98
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-1902 · BOEING 737-800
- Hex
- 780B98
- Octal
- 36005630
- Decimal
- 7,867,288
- Country
- CN
- Tail
- B-1902
- Type
- B738
- Flights observed
- 50
- Distinct callsigns
- 17
- Country
- CN
- Last broadcast
- 5d ago
Last known position
Country allocation
The ICAO 24-bit address 780B98 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 17 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| CGN8435 | Chang'an Airlines | 6 | 2026-07-26 |
| CGN8418 | - | 6 | 2026-06-30 |
| CGN8351 | - | 5 | 2026-06-28 |
| CGN8349 | Chang'an Airlines | 5 | 2026-06-08 |
| CGN8456 | Chang'an Airlines | 4 | 2026-06-05 |
| CGN8352 | - | 4 | 2026-06-28 |
| CGN8455 | Chang'an Airlines | 3 | 2026-06-06 |
| CGN6002 | Chang'an Airlines | 3 | 2026-05-16 |
| CGN8495 | Chang'an Airlines | 2 | 2026-05-05 |
| CGN8316 | Chang'an Airlines | 2 | 2026-06-25 |
| CGN8315 | Chang'an Airlines | 2 | 2026-06-20 |
| CGN6005 | Chang'an Airlines | 2 | 2026-06-06 |
| CGN6001 | Chang'an Airlines | 2 | 2026-05-12 |
| CGN8464 | - | 1 | 2026-04-23 |
| CGN8415 | - | 1 | 2026-07-02 |
| CGN8325 | Chang'an Airlines | 1 | 2026-06-02 |
| CGN6023 | Chang'an Airlines | 1 | 2026-05-02 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | CGN8435 | KWE → SHE | Jul 26, 10:15 UTC | Jul 26, 10:30 UTC | 15m |
| 2026-07-23 | CGN8435 | - | Jul 23, 10:05 UTC | Jul 24, 01:40 UTC | 15h 35m |
| 2026-07-20 | CGN8435 | - | Jul 20, 10:20 UTC | Jul 20, 10:35 UTC | 15m |
| 2026-07-15 | CGN8435 | - | Jul 15, 10:10 UTC | Jul 15, 10:25 UTC | 15m |
| 2026-07-11 | CGN8435 | - | Jul 11, 10:15 UTC | Jul 11, 10:25 UTC | 10m |
| 2026-07-02 | CGN8435 | - | Jul 2, 10:30 UTC | Jul 2, 10:40 UTC | 10m |
| 2026-07-02 | CGN8415 | - | Jul 2, 02:40 UTC | Jul 2, 02:55 UTC | 15m |
| 2026-06-30 | CGN8418 | - | Jun 30, 10:55 UTC | Jun 30, 11:10 UTC | 15m |
| 2026-06-28 | CGN8352 | - | Jun 28, 15:14 UTC | Jun 28, 15:34 UTC | 20m |
| 2026-06-28 | CGN8351 | - | Jun 28, 12:35 UTC | Jun 28, 13:10 UTC | 35m |
| 2026-06-27 | CGN8418 | - | Jun 27, 12:25 UTC | Jun 27, 12:39 UTC | 15m |
| 2026-06-25 | CGN8316 | BZX → XIY | Jun 25, 11:30 UTC | Jun 25, 11:44 UTC | 15m |
| 2026-06-24 | CGN8352 | - | Jun 24, 14:15 UTC | Jun 25, 09:05 UTC | 18h 50m |
| 2026-06-24 | CGN8352 | - | Jun 24, 12:04 UTC | Jun 25, 09:05 UTC | 21h 0m |
| 2026-06-24 | CGN8351 | - | Jun 24, 11:50 UTC | Jun 25, 09:05 UTC | 21h 15m |
| 2026-06-22 | CGN8352 | - | Jun 22, 14:19 UTC | Jun 22, 14:49 UTC | 30m |
| 2026-06-22 | CGN8351 | - | Jun 22, 11:30 UTC | Jun 22, 12:00 UTC | 30m |
| 2026-06-21 | CGN8351 | - | Jun 21, 14:24 UTC | Jun 22, 12:00 UTC | 21h 35m |
| 2026-06-21 | CGN8351 | - | Jun 21, 11:40 UTC | Jun 21, 12:10 UTC | 30m |
| 2026-06-20 | CGN8315 | BZX → HAK | Jun 20, 08:44 UTC | Jun 20, 09:05 UTC | 20m |
| 2026-06-13 | CGN8418 | ZUH → JGS | Jun 13, 10:55 UTC | Jun 13, 11:10 UTC | 15m |
| 2026-06-11 | CGN8418 | ZUH → JGS | Jun 11, 12:30 UTC | Jun 11, 12:40 UTC | 10m |
| 2026-06-09 | CGN8418 | ZUH → JGS | Jun 9, 11:00 UTC | Jun 9, 11:10 UTC | 10m |
| 2026-06-08 | CGN8349 | XIY → CGQ | Jun 8, 10:10 UTC | Jun 8, 13:50 UTC | 3h 40m |
| 2026-06-06 | CGN6005 | LLF → HAK | Jun 6, 23:35 UTC | Jun 7, 09:00 UTC | 9h 25m |
| 2026-06-06 | CGN6005 | LLF → HAK | Jun 6, 10:04 UTC | Jun 7, 09:00 UTC | 22h 55m |
| 2026-06-06 | CGN8455 | CSX → HRB | Jun 6, 05:35 UTC | Jun 6, 23:35 UTC | 18h 0m |
| 2026-06-05 | CGN8456 | HRB → CSX | Jun 5, 09:40 UTC | Jun 6, 05:50 UTC | 20h 10m |
| 2026-06-05 | CGN8455 | CSX → HRB | Jun 5, 05:30 UTC | Jun 5, 10:00 UTC | 4h 30m |
| 2026-06-03 | CGN8456 | HRB → CSX | Jun 3, 10:05 UTC | Jun 4, 04:50 UTC | 18h 45m |
| 2026-06-03 | CGN8456 | HRB → CSX | Jun 3, 09:55 UTC | Jun 4, 04:50 UTC | 18h 55m |
| 2026-06-03 | CGN8456 | HRB → CSX | Jun 3, 05:25 UTC | Jun 4, 02:10 UTC | 20h 45m |
| 2026-06-02 | CGN8325 | KJH → HAK | Jun 2, 02:05 UTC | Jun 2, 02:20 UTC | 15m |
| 2026-05-30 | CGN8418 | ZUH → JGS | May 30, 11:15 UTC | May 30, 11:30 UTC | 15m |
| 2026-05-28 | CGN8316 | BZX → XIY | May 28, 11:25 UTC | May 28, 11:40 UTC | 15m |
| 2026-05-28 | CGN8315 | BZX → HAK | May 28, 09:00 UTC | May 28, 09:10 UTC | 10m |
| 2026-05-20 | CGN8455 | CSX → HRB | May 20, 05:25 UTC | May 20, 09:50 UTC | 4h 25m |
| 2026-05-16 | CGN6002 | SZX → XIY | May 16, 11:16 UTC | May 16, 11:25 UTC | 10m |
| 2026-05-12 | CGN6002 | SZX → XIY | May 12, 11:25 UTC | May 12, 11:35 UTC | 10m |
| 2026-05-12 | CGN6001 | XIY → SZX | May 12, 09:40 UTC | May 12, 09:50 UTC | 10m |
| 2026-05-05 | CGN8349 | XIY → CGQ | May 5, 23:30 UTC | May 6, 09:25 UTC | 9h 55m |
| 2026-05-05 | CGN8495 | CSX → CGQ | May 5, 09:10 UTC | May 5, 23:45 UTC | 14h 35m |
| 2026-05-04 | CGN8349 | XIY → CGQ | May 4, 23:30 UTC | May 5, 09:30 UTC | 10h 0m |
| 2026-05-04 | CGN8349 | XIY → CGQ | May 4, 09:15 UTC | May 4, 23:55 UTC | 14h 41m |
| 2026-05-03 | CGN8495 | CSX → CGQ | May 3, 23:25 UTC | May 4, 09:35 UTC | 10h 10m |
| 2026-05-02 | CGN6023 | XIY → HRB | May 2, 09:35 UTC | May 2, 09:50 UTC | 15m |
| 2026-04-25 | CGN6002 | SZX → XIY | Apr 25, 11:30 UTC | Apr 25, 11:40 UTC | 10m |
| 2026-04-23 | CGN8464 | - | Apr 23, 11:01 UTC | Apr 23, 11:15 UTC | 15m |
| 2026-04-21 | CGN6001 | XIY → SZX | Apr 21, 10:00 UTC | Apr 21, 10:10 UTC | 10m |
| 2026-04-20 | CGN8349 | XIY → CGQ | Apr 20, 23:30 UTC | Apr 20, 23:45 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-1902 page for operator, model, and routing details .