sensors Mode-S transponder
78047D
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-5350 · BOEING 737-800
- Hex
- 78047D
- Octal
- 36002175
- Decimal
- 7,865,469
- Country
- CN
- Tail
- B-5350
- Type
- B738
- Flights observed
- 36
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 3d ago
Last known position
Country allocation
The ICAO 24-bit address 78047D 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 |
|---|---|---|---|
| CDG2295 | Shandong Airlines | 4 | 2026-06-12 |
| CDG8857 | Shandong Airlines | 3 | 2026-04-30 |
| CDG2203 | Shandong Airlines | 3 | 2026-06-13 |
| CDG2293 | Shandong Airlines | 2 | 2026-06-02 |
| CDG2289 | Shandong Airlines | 2 | 2026-06-03 |
| CDG8859 | Shandong Airlines | 1 | 2026-05-02 |
| CDG8007 | Shandong Airlines | 1 | 2026-05-02 |
| CDG7943 | Shandong Airlines | 1 | 2026-06-05 |
| CDG7941 | Shandong Airlines | 1 | 2026-06-04 |
| CDG4685 | Shandong Airlines | 1 | 2026-05-07 |
| CDG4620 | Shandong Airlines | 1 | 2026-05-02 |
| CDG4618 | Shandong Airlines | 1 | 2026-05-22 |
| CDG4617 | Shandong Airlines | 1 | 2026-05-22 |
| CDG4616 | Shandong Airlines | 1 | 2026-05-22 |
| CDG4615 | Shandong Airlines | 1 | 2026-05-22 |
| CDG4614 | Shandong Airlines | 1 | 2026-05-20 |
| CDG4613 | Shandong Airlines | 1 | 2026-05-20 |
| CDG4612 | Shandong Airlines | 1 | 2026-05-07 |
| CDG4611 | Shandong Airlines | 1 | 2026-05-07 |
| CDG4092 | Shandong Airlines | 1 | 2026-05-03 |
Recent flights last 36
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-13 | CDG2203 | PEK → FOC | Jun 13, 05:55 UTC | Jun 13, 06:05 UTC | 10m |
| 2026-06-12 | CDG2295 | ZUH → SHA | Jun 12, 09:00 UTC | Jun 12, 09:10 UTC | 10m |
| 2026-06-10 | CDG1155 | PEK → ZUH | Jun 10, 14:00 UTC | Jun 10, 14:15 UTC | 15m |
| 2026-06-07 | CDG2130 | PEK → XMN | Jun 7, 11:05 UTC | Jun 7, 11:15 UTC | 10m |
| 2026-06-06 | CDG2203 | PEK → FOC | Jun 6, 06:30 UTC | Jun 6, 06:40 UTC | 10m |
| 2026-06-05 | CDG7943 | ZUH → CGO | Jun 5, 00:25 UTC | Jun 5, 00:35 UTC | 10m |
| 2026-06-04 | CDG7941 | TSN → CGQ | Jun 4, 02:05 UTC | Jun 4, 02:20 UTC | 15m |
| 2026-06-03 | CDG2297 | ZUH → SHA | Jun 3, 12:15 UTC | Jun 3, 12:30 UTC | 15m |
| 2026-06-03 | CDG2289 | ZUH → HGH | Jun 3, 04:15 UTC | Jun 3, 04:25 UTC | 10m |
| 2026-06-02 | CDG2295 | ZUH → SHA | Jun 2, 08:55 UTC | Jun 2, 09:05 UTC | 10m |
| 2026-06-02 | CDG2293 | ZUH → SHA | Jun 2, 00:40 UTC | Jun 2, 00:55 UTC | 15m |
| 2026-05-29 | CDG2203 | PEK → FOC | May 29, 06:50 UTC | May 29, 07:00 UTC | 10m |
| 2026-05-29 | CDG1162 | ZUH → PEK | May 29, 01:05 UTC | May 29, 01:20 UTC | 15m |
| 2026-05-28 | CDG2295 | ZUH → SHA | May 28, 10:05 UTC | May 28, 10:20 UTC | 15m |
| 2026-05-27 | CDG2290 | HGH → ZUH | May 27, 08:40 UTC | May 27, 09:00 UTC | 20m |
| 2026-05-27 | CDG2289 | ZUH → HGH | May 27, 04:09 UTC | May 27, 04:24 UTC | 15m |
| 2026-05-26 | CDG2295 | ZUH → SHA | May 26, 08:54 UTC | May 26, 09:04 UTC | 10m |
| 2026-05-25 | CDG2293 | ZUH → SHA | May 25, 23:30 UTC | May 25, 23:45 UTC | 15m |
| 2026-05-22 | CDG4618 | ICN → TAO | May 22, 13:00 UTC | May 22, 13:15 UTC | 15m |
| 2026-05-22 | CDG4617 | TAO → ICN | May 22, 11:10 UTC | May 22, 11:40 UTC | 30m |
| 2026-05-22 | CDG4616 | ICN → TAO | May 22, 07:55 UTC | May 22, 08:25 UTC | 30m |
| 2026-05-22 | CDG4615 | TAO → ICN | May 22, 06:30 UTC | May 22, 06:50 UTC | 20m |
| 2026-05-20 | CDG4614 | ICN → TAO | May 20, 06:45 UTC | May 20, 07:15 UTC | 30m |
| 2026-05-20 | CDG4613 | TAO → ICN | May 20, 04:55 UTC | May 20, 05:10 UTC | 15m |
| 2026-05-07 | CDG4685 | TAO → SZX | May 7, 10:30 UTC | May 7, 10:40 UTC | 10m |
| 2026-05-07 | CDG4612 | ICN → TAO | May 7, 05:25 UTC | May 7, 05:35 UTC | 10m |
| 2026-05-07 | CDG4611 | TAO → ICN | May 7, 03:10 UTC | May 7, 03:35 UTC | 25m |
| 2026-05-03 | CDG4092 | KIX → TAO | May 3, 03:45 UTC | May 3, 05:20 UTC | 1h 35m |
| 2026-05-03 | CDG4091 | TAO → KIX | May 3, 00:45 UTC | May 3, 01:50 UTC | 1h 5m |
| 2026-05-02 | CDG4620 | ICN → TAO | May 2, 15:35 UTC | May 2, 15:45 UTC | 10m |
| 2026-05-02 | CDG8007 | TNA → ICN | May 2, 14:00 UTC | May 2, 14:10 UTC | 10m |
| 2026-05-02 | CDG8859 | TNA → SYX | May 2, 02:35 UTC | May 2, 06:10 UTC | 3h 35m |
| 2026-04-30 | CDG8857 | TNA → SYX | Apr 30, 02:55 UTC | Apr 30, 03:15 UTC | 20m |
| 2026-04-26 | CDG1186 | SZX → TNA | Apr 26, 14:15 UTC | Apr 26, 14:25 UTC | 10m |
| 2026-04-26 | CDG8857 | TNA → SYX | Apr 26, 02:55 UTC | Apr 26, 06:25 UTC | 3h 30m |
| 2026-04-22 | CDG8857 | TNA → SYX | Apr 22, 02:55 UTC | Apr 22, 06:40 UTC | 3h 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-5350 page for operator, model, and routing details .