sensors Mode-S transponder
780E5C
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-6985 · BOEING 737-800
- Hex
- 780E5C
- Octal
- 36007134
- Decimal
- 7,867,996
- Country
- CN
- Tail
- B-6985
- Type
- B738
- Flights observed
- 35
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 6d ago
Last known position
Country allocation
The ICAO 24-bit address 780E5C 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 |
|---|---|---|---|
| CDG4609 | - | 3 | 2026-06-16 |
| CDG4883 | - | 2 | 2026-06-27 |
| CDG4681 | - | 2 | 2026-07-08 |
| CDG4610 | - | 2 | 2026-06-16 |
| CDG8407 | - | 1 | 2026-06-28 |
| CDG8007 | - | 1 | 2026-04-13 |
| CDG4685 | Shandong Airlines | 1 | 2026-05-22 |
| CDG4682 | - | 1 | 2026-07-08 |
| CDG4652 | Shandong Airlines | 1 | 2026-06-19 |
| CDG4620 | - | 1 | 2026-06-27 |
| CDG4619 | - | 1 | 2026-06-27 |
| CDG4618 | Shandong Airlines | 1 | 2026-05-21 |
| CDG4617 | Shandong Airlines | 1 | 2026-05-21 |
| CDG4616 | Shandong Airlines | 1 | 2026-05-21 |
| CDG4615 | Shandong Airlines | 1 | 2026-05-21 |
| CDG4614 | Shandong Airlines | 1 | 2026-04-16 |
| CDG4613 | Shandong Airlines | 1 | 2026-04-16 |
| CDG4612 | Shandong Airlines | 1 | 2026-05-22 |
| CDG4611 | Shandong Airlines | 1 | 2026-05-22 |
| CDG4092 | - | 1 | 2026-06-23 |
Recent flights last 35
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-08 | CDG4682 | - | Jul 8, 05:35 UTC | Jul 8, 05:45 UTC | 10m |
| 2026-07-08 | CDG4681 | - | Jul 8, 04:00 UTC | Jul 8, 04:10 UTC | 10m |
| 2026-06-30 | CDG4086 | - | Jun 30, 08:55 UTC | Jun 30, 09:15 UTC | 20m |
| 2026-06-30 | CDG4085 | - | Jun 30, 07:10 UTC | Jun 30, 07:45 UTC | 35m |
| 2026-06-28 | CDG8407 | - | Jun 28, 09:39 UTC | Jun 28, 10:04 UTC | 25m |
| 2026-06-27 | CDG4620 | - | Jun 27, 14:05 UTC | Jun 27, 14:29 UTC | 25m |
| 2026-06-27 | CDG4619 | - | Jun 27, 12:15 UTC | Jun 27, 12:45 UTC | 30m |
| 2026-06-27 | CDG4883 | - | Jun 27, 03:40 UTC | Jun 27, 03:55 UTC | 15m |
| 2026-06-23 | CDG4092 | - | Jun 23, 03:39 UTC | Jun 23, 05:09 UTC | 1h 30m |
| 2026-06-23 | CDG4091 | - | Jun 23, 00:35 UTC | Jun 23, 01:59 UTC | 1h 25m |
| 2026-06-19 | CDG4652 | PEK → TAO | Jun 19, 16:04 UTC | Jun 19, 16:14 UTC | 10m |
| 2026-06-16 | CDG4610 | - | Jun 16, 04:00 UTC | Jun 16, 04:15 UTC | 15m |
| 2026-06-16 | CDG4609 | - | Jun 16, 01:55 UTC | Jun 16, 02:20 UTC | 25m |
| 2026-06-12 | CDG2209 | PEK → FOC | Jun 12, 02:15 UTC | Jun 12, 02:25 UTC | 10m |
| 2026-06-11 | CDG2205 | PEK → FOC | Jun 11, 07:20 UTC | Jun 11, 07:30 UTC | 10m |
| 2026-05-22 | CDG4685 | TAO → SZX | May 22, 10:25 UTC | May 22, 10:45 UTC | 20m |
| 2026-05-22 | CDG4612 | ICN → TAO | May 22, 05:30 UTC | May 22, 06:00 UTC | 30m |
| 2026-05-22 | CDG4611 | TAO → ICN | May 22, 03:15 UTC | May 22, 03:45 UTC | 30m |
| 2026-05-21 | CDG4618 | ICN → TAO | May 21, 12:55 UTC | May 21, 13:20 UTC | 25m |
| 2026-05-21 | CDG4617 | TAO → ICN | May 21, 11:30 UTC | May 21, 11:50 UTC | 20m |
| 2026-05-21 | CDG4616 | ICN → TAO | May 21, 07:50 UTC | May 21, 08:00 UTC | 10m |
| 2026-05-21 | CDG4615 | TAO → ICN | May 21, 06:20 UTC | May 21, 06:40 UTC | 20m |
| 2026-05-18 | CDG4883 | NGB → HAK | May 18, 05:15 UTC | May 18, 08:30 UTC | 3h 15m |
| 2026-05-15 | CDG4610 | ICN → TAO | May 15, 03:40 UTC | May 15, 04:05 UTC | 25m |
| 2026-05-15 | CDG4609 | TAO → ICN | May 15, 01:45 UTC | May 15, 02:10 UTC | 25m |
| 2026-05-03 | CDG2320 | SHE → TYN | May 3, 23:20 UTC | May 3, 23:30 UTC | 10m |
| 2026-04-22 | CDG4609 | TAO → ICN | Apr 22, 01:45 UTC | Apr 22, 02:00 UTC | 15m |
| 2026-04-19 | CDG1196 | ZUH → TNA | Apr 19, 10:40 UTC | Apr 19, 10:50 UTC | 10m |
| 2026-04-17 | CDG4681 | TAO → SZX | Apr 17, 03:25 UTC | Apr 17, 04:00 UTC | 35m |
| 2026-04-16 | CDG4614 | ICN → TAO | Apr 16, 06:45 UTC | Apr 16, 06:55 UTC | 10m |
| 2026-04-16 | CDG4613 | TAO → ICN | Apr 16, 04:54 UTC | Apr 16, 05:05 UTC | 10m |
| 2026-04-14 | CDG1200 | ZUH → KHN | Apr 14, 10:40 UTC | Apr 14, 10:50 UTC | 10m |
| 2026-04-13 | CDG8007 | - | Apr 13, 14:00 UTC | Apr 13, 14:25 UTC | 25m |
| 2026-04-13 | CDG1188 | - | Apr 13, 08:00 UTC | Apr 13, 08:10 UTC | 10m |
| 2026-04-13 | CDG1187 | TNA → SZX | Apr 13, 06:10 UTC | Apr 13, 06: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-6985 page for operator, model, and routing details .