sensors Mode-S transponder
780D5C
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-1966 · BOEING 737-800
- Hex
- 780D5C
- Octal
- 36006534
- Decimal
- 7,867,740
- Country
- CN
- Tail
- B-1966
- Type
- B738
- Flights observed
- 49
- Distinct callsigns
- 10
- Country
- CN
- Last broadcast
- 5d ago
Last known position
Country allocation
The ICAO 24-bit address 780D5C 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 10 distinct
Recent flights last 49
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-28 | CJX6608 | - | May 28, 08:45 UTC | May 28, 12:20 UTC | 3h 35m |
| 2026-05-28 | CJX6607 | - | May 28, 06:10 UTC | May 28, 06:35 UTC | 25m |
| 2026-05-28 | CJX6607 | - | May 28, 03:05 UTC | May 28, 03:20 UTC | 15m |
| 2026-05-25 | CJX6608 | - | May 25, 08:20 UTC | May 25, 11:45 UTC | 3h 25m |
| 2026-05-25 | CJX6607 | - | May 25, 03:00 UTC | May 25, 06:30 UTC | 3h 30m |
| 2026-05-23 | CJX6608 | - | May 23, 09:50 UTC | May 23, 13:20 UTC | 3h 30m |
| 2026-05-23 | CJX6607 | - | May 23, 03:10 UTC | May 23, 08:00 UTC | 4h 50m |
| 2026-05-21 | CJX8876 | - | May 21, 06:55 UTC | May 21, 07:05 UTC | 10m |
| 2026-05-20 | CJX8927 | - | May 20, 01:00 UTC | May 20, 01:10 UTC | 10m |
| 2026-05-19 | CJX8928 | - | May 19, 07:45 UTC | May 19, 07:55 UTC | 10m |
| 2026-05-19 | CJX8927 | - | May 19, 03:25 UTC | May 19, 03:40 UTC | 15m |
| 2026-05-18 | CJX8904 | - | May 18, 13:35 UTC | May 18, 13:50 UTC | 15m |
| 2026-05-18 | CJX8903 | - | May 18, 08:45 UTC | May 18, 09:00 UTC | 15m |
| 2026-05-17 | CJX8904 | - | May 17, 13:35 UTC | May 17, 13:45 UTC | 10m |
| 2026-05-17 | CJX8903 | - | May 17, 08:55 UTC | May 17, 09:05 UTC | 10m |
| 2026-05-13 | CJX6608 | - | May 13, 08:40 UTC | May 13, 12:10 UTC | 3h 30m |
| 2026-05-13 | CJX6607 | - | May 13, 03:05 UTC | May 13, 06:40 UTC | 3h 35m |
| 2026-05-11 | CJX8913 | - | May 11, 11:25 UTC | May 11, 15:10 UTC | 3h 45m |
| 2026-05-09 | CJX6608 | - | May 9, 08:50 UTC | May 9, 12:25 UTC | 3h 35m |
| 2026-05-08 | CJX6607 | - | May 8, 11:44 UTC | May 9, 06:45 UTC | 19h 0m |
| 2026-05-08 | CJX8927 | - | May 8, 01:04 UTC | May 8, 15:40 UTC | 14h 35m |
| 2026-05-07 | CJX8904 | - | May 7, 12:50 UTC | May 7, 13:00 UTC | 10m |
| 2026-05-07 | CJX8903 | - | May 7, 08:40 UTC | May 7, 08:55 UTC | 15m |
| 2026-05-06 | CJX8883 | - | May 6, 03:25 UTC | May 6, 03:40 UTC | 15m |
| 2026-05-04 | CJX8913 | - | May 4, 11:30 UTC | May 5, 00:50 UTC | 13h 21m |
| 2026-05-04 | CJX8913 | - | May 4, 01:05 UTC | May 5, 00:50 UTC | 23h 46m |
| 2026-05-03 | CJX8928 | - | May 3, 07:20 UTC | May 3, 07:30 UTC | 10m |
| 2026-05-02 | CJX6608 | - | May 2, 09:05 UTC | May 3, 03:35 UTC | 18h 29m |
| 2026-05-02 | CJX6608 | - | May 2, 08:35 UTC | May 3, 03:35 UTC | 18h 59m |
| 2026-05-01 | CJX6607 | - | May 1, 11:25 UTC | May 2, 06:40 UTC | 19h 15m |
| 2026-05-01 | CJX8915 | - | May 1, 00:35 UTC | May 1, 15:20 UTC | 14h 45m |
| 2026-04-30 | CJX8915 | - | Apr 30, 14:40 UTC | May 1, 11:40 UTC | 21h 0m |
| 2026-04-30 | CJX8915 | - | Apr 30, 01:10 UTC | Apr 30, 12:00 UTC | 10h 50m |
| 2026-04-29 | CJX8928 | - | Apr 29, 07:40 UTC | Apr 29, 07:50 UTC | 10m |
| 2026-04-27 | CJX6608 | - | Apr 27, 09:15 UTC | Apr 28, 00:50 UTC | 15h 35m |
| 2026-04-27 | CJX6607 | - | Apr 27, 03:05 UTC | Apr 27, 06:40 UTC | 3h 35m |
| 2026-04-25 | CJX6608 | - | Apr 25, 08:35 UTC | Apr 25, 11:55 UTC | 3h 20m |
| 2026-04-25 | CJX6607 | - | Apr 25, 03:25 UTC | Apr 25, 07:00 UTC | 3h 35m |
| 2026-04-24 | CJX8927 | - | Apr 24, 01:10 UTC | Apr 24, 01:25 UTC | 15m |
| 2026-04-22 | CJX6608 | - | Apr 22, 09:50 UTC | Apr 23, 03:40 UTC | 17h 50m |
| 2026-04-22 | CJX6608 | - | Apr 22, 08:30 UTC | Apr 23, 03:40 UTC | 19h 10m |
| 2026-04-22 | CJX6607 | - | Apr 22, 03:15 UTC | Apr 22, 06:45 UTC | 3h 30m |
| 2026-04-20 | CJX6608 | - | Apr 20, 08:55 UTC | Apr 20, 12:20 UTC | 3h 25m |
| 2026-04-20 | CJX6607 | - | Apr 20, 03:15 UTC | Apr 20, 07:00 UTC | 3h 45m |
| 2026-04-19 | CJX8927 | - | Apr 19, 01:10 UTC | Apr 19, 01:20 UTC | 10m |
| 2026-04-13 | CJX6608 | - | Apr 13, 12:20 UTC | Apr 13, 12:35 UTC | 15m |
| 2026-04-13 | CJX6608 | - | Apr 13, 08:55 UTC | Apr 13, 12:15 UTC | 3h 20m |
| 2026-04-13 | CJX6607 | - | Apr 13, 06:10 UTC | Apr 13, 06:50 UTC | 40m |
| 2026-04-13 | CJX6607 | - | Apr 13, 03:10 UTC | Apr 13, 03:25 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-1966 page for operator, model, and routing details .