sensors Mode-S transponder
78116C
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-1436 · BOEING 737-800
- Hex
- 78116C
- Octal
- 36010554
- Decimal
- 7,868,780
- Country
- CN
- Tail
- B-1436
- Type
- B738
- Flights observed
- 58
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 78116C 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 |
|---|---|---|---|
| CDG4631 | Shandong Airlines | 4 | 2026-06-06 |
| CDG4632 | Shandong Airlines | 3 | 2026-06-06 |
| CDG4610 | - | 3 | 2026-06-22 |
| CDG4609 | - | 3 | 2026-06-22 |
| CDG4094 | Shandong Airlines | 3 | 2026-06-05 |
| CDG4080 | Shandong Airlines | 3 | 2026-06-01 |
| CDG4079 | Shandong Airlines | 3 | 2026-06-01 |
| CDG8857 | Shandong Airlines | 2 | 2026-04-28 |
| CDG4682 | - | 2 | 2026-06-26 |
| CDG4614 | Shandong Airlines | 2 | 2026-06-08 |
| CDG4612 | - | 2 | 2026-07-09 |
| CDG4611 | - | 2 | 2026-07-09 |
| CDG4093 | Shandong Airlines | 2 | 2026-06-04 |
| CDG8086 | Shandong Airlines | 1 | 2026-04-21 |
| CDG8085 | Shandong Airlines | 1 | 2026-04-21 |
| CDG8076 | Shandong Airlines | 1 | 2026-04-30 |
| CDG8075 | Shandong Airlines | 1 | 2026-04-30 |
| CDG8073 | - | 1 | 2026-04-19 |
| CDG8004 | - | 1 | 2026-04-18 |
| CDG8003 | - | 1 | 2026-04-18 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-16 | CDG1194 | ZUH → TNA | Jul 16, 13:00 UTC | Jul 16, 13:15 UTC | 15m |
| 2026-07-09 | CDG4685 | - | Jul 9, 11:10 UTC | Jul 9, 12:35 UTC | 1h 25m |
| 2026-07-09 | CDG4612 | - | Jul 9, 05:25 UTC | Jul 9, 05:40 UTC | 15m |
| 2026-07-09 | CDG4611 | - | Jul 9, 03:35 UTC | Jul 9, 03:55 UTC | 20m |
| 2026-07-08 | CDG4618 | - | Jul 8, 13:00 UTC | Jul 8, 13:30 UTC | 30m |
| 2026-07-08 | CDG4617 | - | Jul 8, 11:30 UTC | Jul 8, 11:50 UTC | 20m |
| 2026-07-08 | CDG4616 | - | Jul 8, 07:55 UTC | Jul 8, 08:25 UTC | 30m |
| 2026-07-08 | CDG4615 | - | Jul 8, 06:05 UTC | Jul 8, 06:40 UTC | 35m |
| 2026-06-26 | CDG4682 | - | Jun 26, 06:15 UTC | Jun 26, 06:29 UTC | 15m |
| 2026-06-22 | CDG4610 | - | Jun 22, 03:24 UTC | Jun 22, 03:40 UTC | 15m |
| 2026-06-22 | CDG4609 | - | Jun 22, 01:35 UTC | Jun 22, 02:04 UTC | 30m |
| 2026-06-14 | CDG4682 | - | Jun 14, 05:15 UTC | Jun 14, 05:25 UTC | 10m |
| 2026-06-14 | CDG4681 | - | Jun 14, 03:40 UTC | Jun 14, 03:55 UTC | 15m |
| 2026-06-11 | CDG4926 | - | Jun 11, 10:20 UTC | Jun 11, 10:30 UTC | 10m |
| 2026-06-08 | CDG4614 | ICN → TAO | Jun 8, 06:40 UTC | Jun 8, 06:55 UTC | 15m |
| 2026-06-08 | CDG4613 | TAO → ICN | Jun 8, 04:55 UTC | Jun 8, 05:15 UTC | 20m |
| 2026-06-06 | CDG4632 | HKG → TAO | Jun 6, 09:30 UTC | Jun 6, 10:39 UTC | 1h 10m |
| 2026-06-06 | CDG4632 | HKG → TAO | Jun 6, 09:15 UTC | Jun 6, 09:19 UTC | 5m |
| 2026-06-06 | CDG4631 | TAO → HKG | Jun 6, 07:55 UTC | Jun 6, 08:15 UTC | 20m |
| 2026-06-06 | CDG4631 | TAO → HKG | Jun 6, 06:40 UTC | Jun 6, 07:05 UTC | 25m |
| 2026-06-05 | CDG4094 | KIX → TNA | Jun 5, 09:30 UTC | Jun 6, 07:05 UTC | 21h 35m |
| 2026-06-05 | CDG4094 | KIX → TNA | Jun 5, 08:35 UTC | Jun 6, 06:55 UTC | 22h 20m |
| 2026-06-04 | CDG4093 | TNA → KIX | Jun 4, 11:05 UTC | Jun 5, 07:00 UTC | 19h 55m |
| 2026-06-04 | CDG4632 | HKG → TAO | Jun 4, 09:50 UTC | Jun 5, 07:00 UTC | 21h 10m |
| 2026-06-04 | CDG4631 | TAO → HKG | Jun 4, 06:35 UTC | Jun 4, 07:55 UTC | 1h 20m |
| 2026-06-03 | CDG4631 | TAO → HKG | Jun 3, 09:05 UTC | Jun 4, 07:55 UTC | 22h 50m |
| 2026-06-03 | CDG4092 | KIX → TAO | Jun 3, 07:40 UTC | Jun 4, 07:00 UTC | 23h 20m |
| 2026-06-03 | CDG4091 | TAO → KIX | Jun 3, 04:45 UTC | Jun 3, 06:20 UTC | 1h 35m |
| 2026-06-02 | CDG4612 | ICN → TAO | Jun 2, 06:05 UTC | Jun 3, 05:00 UTC | 22h 55m |
| 2026-06-02 | CDG4611 | TAO → ICN | Jun 2, 04:45 UTC | Jun 2, 05:15 UTC | 30m |
| 2026-06-01 | CDG4080 | BKK → TAO | Jun 1, 19:55 UTC | Jun 1, 21:35 UTC | 1h 40m |
| 2026-06-01 | CDG4079 | TAO → BKK | Jun 1, 16:50 UTC | Jun 1, 18:25 UTC | 1h 35m |
| 2026-05-29 | CDG4094 | KIX → TNA | May 29, 08:30 UTC | May 29, 10:20 UTC | 1h 50m |
| 2026-05-29 | CDG4093 | TNA → KIX | May 29, 06:10 UTC | May 29, 07:05 UTC | 55m |
| 2026-05-28 | CDG4080 | BKK → TAO | May 28, 20:10 UTC | May 29, 06:05 UTC | 9h 55m |
| 2026-05-28 | CDG4079 | TAO → BKK | May 28, 16:55 UTC | May 28, 18:40 UTC | 1h 45m |
| 2026-05-21 | CDG4610 | ICN → TAO | May 21, 03:40 UTC | May 21, 03:55 UTC | 15m |
| 2026-05-21 | CDG4609 | TAO → ICN | May 21, 01:35 UTC | May 21, 02:05 UTC | 30m |
| 2026-05-20 | CDG4610 | ICN → TAO | May 20, 03:40 UTC | May 20, 03:55 UTC | 15m |
| 2026-05-20 | CDG4609 | TAO → ICN | May 20, 01:30 UTC | May 20, 01:50 UTC | 20m |
| 2026-05-19 | CDG4086 | TPE → TAO | May 19, 08:50 UTC | May 19, 09:20 UTC | 30m |
| 2026-05-19 | CDG4085 | TAO → TPE | May 19, 07:20 UTC | May 19, 07:45 UTC | 25m |
| 2026-05-06 | CDG4614 | ICN → TAO | May 6, 06:45 UTC | May 6, 06:55 UTC | 10m |
| 2026-05-05 | CDG4080 | BKK → TAO | May 5, 19:50 UTC | May 5, 20:05 UTC | 15m |
| 2026-05-05 | CDG4079 | TAO → BKK | May 5, 18:10 UTC | May 5, 18:35 UTC | 25m |
| 2026-05-02 | CDG1185 | TNA → SZX | May 2, 12:20 UTC | May 2, 12:30 UTC | 10m |
| 2026-05-02 | CDG1184 | WUS → TNA | May 2, 04:05 UTC | May 2, 04:15 UTC | 10m |
| 2026-05-02 | CDG1183 | WUS → SZX | May 2, 02:10 UTC | May 2, 02:30 UTC | 20m |
| 2026-04-30 | CDG8076 | BKK → TNA | Apr 30, 19:40 UTC | Apr 30, 19:50 UTC | 10m |
| 2026-04-30 | CDG8075 | TNA → BKK | Apr 30, 17:45 UTC | Apr 30, 18:05 UTC | 20m |
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-1436 page for operator, model, and routing details .