sensors Mode-S transponder
780687
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-5538 · BOEING 737-800
- Hex
- 780687
- Octal
- 36003207
- Decimal
- 7,865,991
- Country
- CN
- Tail
- B-5538
- Type
- B738
- Flights observed
- 44
- Distinct callsigns
- 8
- Country
- CN
- Last broadcast
- 12h ago
Last known position
Country allocation
The ICAO 24-bit address 780687 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 8 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| GDC7173 | Grand China Air | 8 | 2026-05-19 |
| GDC7159 | - | 7 | 2026-05-29 |
| GDC7127 | - | 7 | 2026-06-02 |
| GDC7174 | Grand China Air | 6 | 2026-05-17 |
| GDC7670 | - | 5 | 2026-05-30 |
| GDC7669 | - | 5 | 2026-05-30 |
| GDC7885 | Grand China Air | 4 | 2026-05-20 |
| GDC7139 | Grand China Air | 1 | 2026-04-24 |
Recent flights last 44
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | GDC7127 | - | Jun 2, 22:50 UTC | Jun 2, 23:00 UTC | 10m |
| 2026-05-30 | GDC7670 | - | May 30, 14:50 UTC | May 30, 15:10 UTC | 20m |
| 2026-05-30 | GDC7669 | - | May 30, 11:20 UTC | May 30, 11:35 UTC | 15m |
| 2026-05-29 | GDC7127 | - | May 29, 22:50 UTC | May 29, 23:00 UTC | 10m |
| 2026-05-29 | GDC7159 | - | May 29, 01:35 UTC | May 29, 01:45 UTC | 10m |
| 2026-05-26 | GDC7127 | - | May 26, 22:44 UTC | May 26, 22:54 UTC | 10m |
| 2026-05-25 | - | - | May 25, 11:35 UTC | May 25, 11:50 UTC | 15m |
| 2026-05-21 | GDC7670 | - | May 21, 14:45 UTC | May 21, 15:00 UTC | 15m |
| 2026-05-21 | GDC7669 | - | May 21, 11:20 UTC | May 21, 11:35 UTC | 15m |
| 2026-05-20 | GDC7127 | - | May 20, 22:45 UTC | May 20, 22:55 UTC | 10m |
| 2026-05-20 | GDC7885 | PEK → HLD | May 20, 11:55 UTC | May 20, 12:05 UTC | 10m |
| 2026-05-19 | GDC7173 | HRB → WUH | May 19, 04:30 UTC | May 19, 09:25 UTC | 4h 55m |
| 2026-05-18 | GDC7159 | - | May 18, 01:25 UTC | May 18, 01:35 UTC | 10m |
| 2026-05-17 | GDC7174 | WUH → HRB | May 17, 09:15 UTC | May 17, 09:25 UTC | 10m |
| 2026-05-09 | GDC7127 | - | May 9, 22:55 UTC | May 9, 23:05 UTC | 10m |
| 2026-05-09 | GDC7159 | - | May 9, 01:05 UTC | May 9, 01:15 UTC | 10m |
| 2026-05-08 | GDC7670 | - | May 8, 14:55 UTC | May 8, 15:10 UTC | 15m |
| 2026-05-08 | GDC7669 | - | May 8, 11:25 UTC | May 8, 11:44 UTC | 20m |
| 2026-05-07 | GDC7159 | - | May 7, 01:10 UTC | May 7, 01:20 UTC | 10m |
| 2026-05-06 | GDC7670 | - | May 6, 14:50 UTC | May 6, 15:05 UTC | 15m |
| 2026-05-06 | GDC7669 | - | May 6, 11:20 UTC | May 6, 11:40 UTC | 20m |
| 2026-05-06 | GDC7159 | - | May 6, 01:05 UTC | May 6, 01:15 UTC | 10m |
| 2026-05-05 | GDC7173 | HRB → WUH | May 5, 04:50 UTC | May 5, 09:20 UTC | 4h 30m |
| 2026-05-04 | GDC7885 | PEK → HLD | May 4, 11:55 UTC | May 4, 12:05 UTC | 10m |
| 2026-05-04 | GDC7159 | - | May 4, 01:05 UTC | May 4, 01:15 UTC | 10m |
| 2026-05-03 | GDC7885 | PEK → HLD | May 3, 11:40 UTC | May 3, 11:50 UTC | 10m |
| 2026-05-03 | GDC7159 | - | May 3, 01:10 UTC | May 3, 01:20 UTC | 10m |
| 2026-05-01 | GDC7127 | - | May 1, 22:55 UTC | May 1, 23:05 UTC | 10m |
| 2026-05-01 | GDC7670 | - | May 1, 14:50 UTC | May 1, 15:10 UTC | 20m |
| 2026-05-01 | GDC7669 | - | May 1, 11:25 UTC | May 1, 11:40 UTC | 15m |
| 2026-04-30 | GDC7127 | - | Apr 30, 22:55 UTC | Apr 30, 23:05 UTC | 10m |
| 2026-04-30 | GDC7174 | WUH → HRB | Apr 30, 04:15 UTC | Apr 30, 09:30 UTC | 5h 15m |
| 2026-04-29 | GDC7173 | HRB → WUH | Apr 29, 04:29 UTC | Apr 29, 09:15 UTC | 4h 46m |
| 2026-04-28 | GDC7174 | WUH → HRB | Apr 28, 04:35 UTC | Apr 28, 09:20 UTC | 4h 45m |
| 2026-04-27 | GDC7174 | WUH → HRB | Apr 27, 04:45 UTC | Apr 27, 09:10 UTC | 4h 25m |
| 2026-04-26 | GDC7885 | PEK → HLD | Apr 26, 12:05 UTC | Apr 26, 12:15 UTC | 10m |
| 2026-04-25 | GDC7173 | HRB → WUH | Apr 25, 04:30 UTC | Apr 25, 09:25 UTC | 4h 55m |
| 2026-04-24 | GDC7139 | PEK → HRB | Apr 24, 23:10 UTC | Apr 24, 23:20 UTC | 10m |
| 2026-04-24 | GDC7174 | WUH → HRB | Apr 24, 04:35 UTC | Apr 24, 09:25 UTC | 4h 50m |
| 2026-04-23 | GDC7173 | HRB → WUH | Apr 23, 04:35 UTC | Apr 23, 09:55 UTC | 5h 20m |
| 2026-04-21 | GDC7173 | HRB → WUH | Apr 21, 23:05 UTC | Apr 22, 09:05 UTC | 10h 0m |
| 2026-04-21 | GDC7173 | HRB → WUH | Apr 21, 04:40 UTC | Apr 21, 09:00 UTC | 4h 20m |
| 2026-04-20 | GDC7174 | WUH → HRB | Apr 20, 04:35 UTC | Apr 20, 09:30 UTC | 4h 55m |
| 2026-04-19 | GDC7173 | HRB → WUH | Apr 19, 04:35 UTC | Apr 19, 09:20 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-5538 page for operator, model, and routing details .