sensors Mode-S transponder
780823
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-5629 · BOEING 737-800
- Hex
- 780823
- Octal
- 36004043
- Decimal
- 7,866,403
- Country
- CN
- Tail
- B-5629
- Type
- B738
- Flights observed
- 70
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 18h ago
Last known position
Country allocation
The ICAO 24-bit address 780823 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 |
|---|---|---|---|
| CDG4910 | Shandong Airlines | 3 | 2026-05-26 |
| CDG4883 | - | 3 | 2026-06-29 |
| CDG4619 | - | 3 | 2026-06-13 |
| CDG2295 | - | 3 | 2026-06-20 |
| CDG1192 | - | 3 | 2026-06-22 |
| CDG8086 | Shandong Airlines | 2 | 2026-06-01 |
| CDG8085 | Shandong Airlines | 2 | 2026-06-01 |
| CDG8010 | Shandong Airlines | 2 | 2026-06-11 |
| CDG8009 | Shandong Airlines | 2 | 2026-06-11 |
| CDG4686 | Shandong Airlines | 2 | 2026-04-20 |
| CDG4685 | Shandong Airlines | 2 | 2026-04-20 |
| CDG4620 | Shandong Airlines | 2 | 2026-06-13 |
| CDG4616 | - | 2 | 2026-07-04 |
| CDG4615 | - | 2 | 2026-07-04 |
| CDG4612 | Shandong Airlines | 2 | 2026-04-20 |
| CDG4611 | Shandong Airlines | 2 | 2026-05-02 |
| CDG1198 | - | 2 | 2026-07-13 |
| CDG1188 | Shandong Airlines | 2 | 2026-05-30 |
| CDG8407 | - | 1 | 2026-06-30 |
| CDG8008 | Shandong Airlines | 1 | 2026-05-05 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | CDG1198 | - | Jul 13, 12:10 UTC | Jul 13, 12:25 UTC | 15m |
| 2026-07-13 | CDG1198 | - | Jul 13, 10:55 UTC | Jul 13, 11:05 UTC | 10m |
| 2026-07-13 | CDG1197 | - | Jul 13, 09:15 UTC | Jul 13, 09:30 UTC | 15m |
| 2026-07-12 | CDG1180 | - | Jul 12, 02:55 UTC | Jul 12, 03:05 UTC | 10m |
| 2026-07-12 | CDG4681 | - | Jul 12, 01:05 UTC | Jul 12, 01:25 UTC | 20m |
| 2026-07-11 | CDG4651 | - | Jul 11, 11:30 UTC | Jul 11, 11:45 UTC | 15m |
| 2026-07-05 | CDG1200 | - | Jul 5, 13:40 UTC | Jul 5, 13:55 UTC | 15m |
| 2026-07-04 | CDG4616 | - | Jul 4, 07:55 UTC | Jul 4, 08:20 UTC | 25m |
| 2026-07-04 | CDG4615 | - | Jul 4, 06:15 UTC | Jul 4, 06:55 UTC | 40m |
| 2026-07-03 | CDG4616 | - | Jul 3, 08:05 UTC | Jul 3, 08:20 UTC | 15m |
| 2026-07-03 | CDG4615 | - | Jul 3, 06:40 UTC | Jul 3, 07:10 UTC | 30m |
| 2026-07-03 | CDG4642 | - | Jul 3, 02:15 UTC | Jul 3, 02:25 UTC | 10m |
| 2026-06-30 | CDG8407 | - | Jun 30, 12:30 UTC | Jun 30, 12:50 UTC | 20m |
| 2026-06-29 | CDG4883 | - | Jun 29, 04:09 UTC | Jun 29, 04:25 UTC | 15m |
| 2026-06-26 | CDG2124 | - | Jun 26, 23:00 UTC | Jun 26, 23:09 UTC | 10m |
| 2026-06-26 | CDG2205 | - | Jun 26, 08:20 UTC | Jun 26, 08:34 UTC | 15m |
| 2026-06-25 | CDG2122 | - | Jun 25, 02:54 UTC | Jun 25, 03:04 UTC | 10m |
| 2026-06-24 | CDG1156 | - | Jun 24, 12:04 UTC | Jun 24, 12:20 UTC | 15m |
| 2026-06-24 | CDG1159 | - | Jun 24, 07:50 UTC | Jun 24, 07:59 UTC | 10m |
| 2026-06-24 | CDG1160 | - | Jun 24, 03:15 UTC | Jun 24, 03:24 UTC | 10m |
| 2026-06-23 | CDG7943 | - | Jun 23, 00:19 UTC | Jun 23, 00:35 UTC | 15m |
| 2026-06-22 | CDG1191 | TNA → ZUH | Jun 22, 12:40 UTC | Jun 22, 12:49 UTC | 10m |
| 2026-06-22 | CDG1192 | - | Jun 22, 00:24 UTC | Jun 22, 00:40 UTC | 15m |
| 2026-06-21 | CDG1192 | - | Jun 21, 00:25 UTC | Jun 21, 00:34 UTC | 10m |
| 2026-06-20 | CDG2295 | - | Jun 20, 08:55 UTC | Jun 20, 09:09 UTC | 15m |
| 2026-06-19 | CDG2295 | - | Jun 19, 09:09 UTC | Jun 19, 09:19 UTC | 10m |
| 2026-06-19 | CDG2294 | - | Jun 19, 05:09 UTC | Jun 19, 05:34 UTC | 25m |
| 2026-06-18 | CDG2293 | - | Jun 18, 23:35 UTC | Jun 18, 23:50 UTC | 15m |
| 2026-06-18 | CDG1192 | - | Jun 18, 00:20 UTC | Jun 18, 00:30 UTC | 10m |
| 2026-06-13 | CDG4620 | ICN → TAO | Jun 13, 14:00 UTC | Jun 13, 14:30 UTC | 30m |
| 2026-06-13 | CDG4619 | - | Jun 13, 12:05 UTC | Jun 13, 12:40 UTC | 35m |
| 2026-06-13 | CDG4883 | - | Jun 13, 03:25 UTC | Jun 13, 03:40 UTC | 15m |
| 2026-06-11 | CDG8010 | ICN → TNA | Jun 11, 13:35 UTC | Jun 11, 13:55 UTC | 20m |
| 2026-06-11 | CDG8009 | TNA → ICN | Jun 11, 11:30 UTC | Jun 11, 11:55 UTC | 25m |
| 2026-06-01 | CDG8086 | KIX → TNA | Jun 1, 07:20 UTC | Jun 1, 08:50 UTC | 1h 30m |
| 2026-06-01 | CDG8085 | TNA → KIX | Jun 1, 04:05 UTC | Jun 1, 05:40 UTC | 1h 35m |
| 2026-05-30 | CDG1188 | SZX → TNA | May 30, 07:30 UTC | May 30, 07:40 UTC | 10m |
| 2026-05-30 | CDG1187 | TNA → SZX | May 30, 05:45 UTC | May 30, 06:05 UTC | 20m |
| 2026-05-26 | CDG4910 | ZUH → KHN | May 26, 05:20 UTC | May 26, 05:30 UTC | 10m |
| 2026-05-24 | CDG4883 | NGB → HAK | May 24, 05:10 UTC | May 24, 08:20 UTC | 3h 10m |
| 2026-05-22 | CDG4910 | ZUH → KHN | May 22, 05:55 UTC | May 22, 06:05 UTC | 10m |
| 2026-05-20 | CDG4910 | ZUH → KHN | May 20, 04:50 UTC | May 20, 05:00 UTC | 10m |
| 2026-05-17 | CDG2128 | PEK → XMN | May 17, 13:55 UTC | May 17, 14:05 UTC | 10m |
| 2026-05-13 | CDG1162 | ZUH → PEK | May 13, 01:10 UTC | May 13, 01:20 UTC | 10m |
| 2026-05-10 | CDG2295 | ZUH → SHA | May 10, 10:10 UTC | May 10, 10:19 UTC | 10m |
| 2026-05-08 | CDG8002 | ICN → TNA | May 8, 03:35 UTC | May 8, 03:44 UTC | 10m |
| 2026-05-07 | CDG8010 | ICN → TNA | May 7, 13:35 UTC | May 7, 13:45 UTC | 10m |
| 2026-05-07 | CDG8009 | TNA → ICN | May 7, 11:25 UTC | May 7, 11:40 UTC | 15m |
| 2026-05-06 | CDG8004 | ICN → TNA | May 6, 18:10 UTC | May 7, 06:40 UTC | 12h 30m |
| 2026-05-06 | CDG8003 | TNA → ICN | May 6, 16:55 UTC | May 6, 17:05 UTC | 10m |
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-5629 page for operator, model, and routing details .