sensors Mode-S transponder
781173
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-1443 · BOEING 737-800
- Hex
- 781173
- Octal
- 36010563
- Decimal
- 7,868,787
- Country
- CN
- Tail
- B-1443
- Type
- B738
- Flights observed
- 42
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address 781173 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 |
|---|---|---|---|
| CDG4080 | - | 4 | 2026-06-26 |
| CDG4079 | - | 3 | 2026-06-26 |
| CDG4682 | - | 2 | 2026-07-09 |
| CDG4681 | - | 2 | 2026-07-09 |
| CDG4631 | - | 2 | 2026-07-05 |
| CDG4617 | - | 2 | 2026-07-13 |
| CDG4612 | Shandong Airlines | 2 | 2026-05-17 |
| CDG4610 | Shandong Airlines | 2 | 2026-06-03 |
| CDG4609 | Shandong Airlines | 2 | 2026-06-03 |
| CDG7629 | Shandong Airlines | 1 | 2026-04-14 |
| CDG4998 | Shandong Airlines | 1 | 2026-04-24 |
| CDG4997 | Shandong Airlines | 1 | 2026-04-23 |
| CDG4925 | - | 1 | 2026-07-04 |
| CDG4912 | Shandong Airlines | 1 | 2026-06-04 |
| CDG4911 | Shandong Airlines | 1 | 2026-06-04 |
| CDG4650 | - | 1 | 2026-07-05 |
| CDG4642 | Shandong Airlines | 1 | 2026-06-04 |
| CDG4632 | - | 1 | 2026-07-05 |
| CDG4620 | Shandong Airlines | 1 | 2026-04-20 |
| CDG4619 | Shandong Airlines | 1 | 2026-04-20 |
Recent flights last 42
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | CDG4092 | - | Jul 14, 03:40 UTC | Jul 14, 05:05 UTC | 1h 25m |
| 2026-07-14 | CDG4091 | - | Jul 14, 00:45 UTC | Jul 14, 02:20 UTC | 1h 35m |
| 2026-07-13 | CDG4618 | - | Jul 13, 12:55 UTC | Jul 13, 13:15 UTC | 20m |
| 2026-07-13 | CDG4617 | - | Jul 13, 11:20 UTC | Jul 13, 11:45 UTC | 25m |
| 2026-07-11 | CDG2320 | - | Jul 11, 23:40 UTC | Jul 12, 00:01 UTC | 20m |
| 2026-07-09 | CDG4682 | - | Jul 9, 06:05 UTC | Jul 9, 06:15 UTC | 10m |
| 2026-07-09 | CDG4681 | - | Jul 9, 04:05 UTC | Jul 9, 04:45 UTC | 40m |
| 2026-07-05 | CDG4650 | - | Jul 5, 20:00 UTC | Jul 5, 20:15 UTC | 15m |
| 2026-07-05 | CDG4632 | - | Jul 5, 09:55 UTC | Jul 5, 11:15 UTC | 1h 20m |
| 2026-07-05 | CDG4631 | - | Jul 5, 07:30 UTC | Jul 5, 07:50 UTC | 20m |
| 2026-07-05 | CDG4631 | - | Jul 5, 06:30 UTC | Jul 5, 06:50 UTC | 20m |
| 2026-07-04 | CDG4925 | - | Jul 4, 01:15 UTC | Jul 4, 01:35 UTC | 20m |
| 2026-06-26 | CDG4080 | - | Jun 26, 21:50 UTC | Jun 26, 22:25 UTC | 35m |
| 2026-06-26 | CDG4080 | - | Jun 26, 20:50 UTC | Jun 26, 21:04 UTC | 15m |
| 2026-06-26 | CDG4079 | - | Jun 26, 17:54 UTC | Jun 26, 19:24 UTC | 1h 30m |
| 2026-06-15 | CDG4682 | - | Jun 15, 14:34 UTC | Jun 15, 14:45 UTC | 10m |
| 2026-06-15 | CDG4681 | - | Jun 15, 03:05 UTC | Jun 15, 04:45 UTC | 1h 40m |
| 2026-06-04 | CDG4912 | FOC → TAO | Jun 4, 10:50 UTC | Jun 4, 11:00 UTC | 10m |
| 2026-06-04 | CDG4911 | FOC → ZUH | Jun 4, 09:05 UTC | Jun 4, 09:25 UTC | 20m |
| 2026-06-04 | CDG4642 | PEK → TAO | Jun 4, 02:15 UTC | Jun 4, 02:25 UTC | 10m |
| 2026-06-03 | CDG4610 | ICN → TAO | Jun 3, 03:30 UTC | Jun 3, 03:55 UTC | 25m |
| 2026-06-03 | CDG4609 | TAO → ICN | Jun 3, 01:40 UTC | Jun 3, 02:15 UTC | 35m |
| 2026-06-02 | CDG4086 | TPE → TAO | Jun 2, 08:45 UTC | Jun 2, 09:05 UTC | 20m |
| 2026-06-02 | CDG4085 | TAO → TPE | Jun 2, 07:20 UTC | Jun 2, 07:40 UTC | 20m |
| 2026-05-23 | CDG4610 | ICN → TAO | May 23, 03:25 UTC | May 23, 03:55 UTC | 30m |
| 2026-05-23 | CDG4609 | TAO → ICN | May 23, 01:50 UTC | May 23, 02:15 UTC | 25m |
| 2026-05-17 | CDG4612 | ICN → TAO | May 17, 05:15 UTC | May 17, 05:40 UTC | 25m |
| 2026-05-17 | CDG4611 | TAO → ICN | May 17, 03:20 UTC | May 17, 03:40 UTC | 20m |
| 2026-05-02 | CDG2240 | - | May 2, 04:45 UTC | May 2, 05:00 UTC | 15m |
| 2026-04-25 | CDG4080 | BKK → TAO | Apr 25, 19:55 UTC | Apr 25, 20:15 UTC | 20m |
| 2026-04-25 | CDG4079 | TAO → BKK | Apr 25, 18:10 UTC | Apr 25, 18:35 UTC | 25m |
| 2026-04-24 | CDG4998 | HET → TAO | Apr 24, 02:35 UTC | Apr 24, 02:55 UTC | 20m |
| 2026-04-23 | CDG4997 | TAO → HET | Apr 23, 23:45 UTC | Apr 24, 00:15 UTC | 30m |
| 2026-04-22 | CDG4080 | BKK → TAO | Apr 22, 20:15 UTC | Apr 22, 21:05 UTC | 50m |
| 2026-04-22 | CDG4079 | TAO → BKK | Apr 22, 18:05 UTC | Apr 22, 19:00 UTC | 55m |
| 2026-04-21 | CDG4612 | ICN → TAO | Apr 21, 05:30 UTC | Apr 21, 05:40 UTC | 10m |
| 2026-04-20 | CDG4620 | ICN → TAO | Apr 20, 14:05 UTC | Apr 20, 14:20 UTC | 15m |
| 2026-04-20 | CDG4619 | TAO → ICN | Apr 20, 12:20 UTC | Apr 20, 12:35 UTC | 15m |
| 2026-04-16 | CDG4617 | TAO → ICN | Apr 16, 11:39 UTC | Apr 16, 11:54 UTC | 15m |
| 2026-04-16 | CDG4616 | ICN → TAO | Apr 16, 07:54 UTC | Apr 16, 08:04 UTC | 10m |
| 2026-04-16 | CDG4615 | TAO → ICN | Apr 16, 06:25 UTC | Apr 16, 06:40 UTC | 15m |
| 2026-04-14 | CDG7629 | YNT → SZX | Apr 14, 07:10 UTC | Apr 14, 07:30 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-1443 page for operator, model, and routing details .