sensors Mode-S transponder
781BD3
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-220W · BOEING 737-800
- Hex
- 781BD3
- Octal
- 36015723
- Decimal
- 7,871,443
- Country
- CN
- Tail
- B-220W
- Type
- B738
- Flights observed
- 34
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 4d ago
Last known position
Country allocation
The ICAO 24-bit address 781BD3 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 | 10 | 2026-05-25 |
| CDG4632 | Shandong Airlines | 5 | 2026-05-25 |
| CDG4092 | - | 2 | 2026-04-13 |
| CDG4912 | Shandong Airlines | 1 | 2026-05-19 |
| CDG4911 | Shandong Airlines | 1 | 2026-05-19 |
| CDG4682 | Shandong Airlines | 1 | 2026-05-22 |
| CDG4681 | Shandong Airlines | 1 | 2026-05-22 |
| CDG4642 | Shandong Airlines | 1 | 2026-04-30 |
| CDG4620 | Shandong Airlines | 1 | 2026-05-03 |
| CDG4619 | Shandong Airlines | 1 | 2026-05-03 |
| CDG4618 | Shandong Airlines | 1 | 2026-04-29 |
| CDG4617 | Shandong Airlines | 1 | 2026-04-29 |
| CDG4616 | Shandong Airlines | 1 | 2026-04-29 |
| CDG4615 | Shandong Airlines | 1 | 2026-04-29 |
| CDG4610 | Shandong Airlines | 1 | 2026-04-16 |
| CDG4609 | Shandong Airlines | 1 | 2026-04-16 |
| CDG4091 | Shandong Airlines | 1 | 2026-04-13 |
| CDG2320 | Shandong Airlines | 1 | 2026-05-05 |
| CDG2319 | Shandong Airlines | 1 | 2026-05-06 |
| CDG1196 | Shandong Airlines | 1 | 2026-05-02 |
Recent flights last 34
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-25 | CDG4632 | HKG → TAO | May 25, 09:50 UTC | May 25, 11:00 UTC | 1h 10m |
| 2026-05-25 | CDG4631 | TAO → HKG | May 25, 07:30 UTC | May 25, 07:45 UTC | 15m |
| 2026-05-25 | CDG4631 | TAO → HKG | May 25, 06:25 UTC | May 25, 06:40 UTC | 15m |
| 2026-05-22 | CDG4682 | SZX → TAO | May 22, 07:20 UTC | May 22, 07:30 UTC | 10m |
| 2026-05-22 | CDG4681 | TAO → SZX | May 22, 03:30 UTC | May 22, 03:50 UTC | 20m |
| 2026-05-19 | CDG4912 | FOC → TAO | May 19, 13:55 UTC | May 19, 14:05 UTC | 10m |
| 2026-05-19 | CDG4911 | FOC → ZUH | May 19, 12:10 UTC | May 19, 12:30 UTC | 20m |
| 2026-05-06 | CDG2319 | TYN → SHE | May 6, 08:45 UTC | May 6, 08:55 UTC | 10m |
| 2026-05-05 | CDG2320 | SHE → TYN | May 5, 23:30 UTC | May 5, 23:40 UTC | 10m |
| 2026-05-03 | CDG4620 | ICN → TAO | May 3, 14:05 UTC | May 3, 14:35 UTC | 30m |
| 2026-05-03 | CDG4619 | TAO → ICN | May 3, 12:30 UTC | May 3, 13:00 UTC | 30m |
| 2026-05-02 | CDG1196 | ZUH → TNA | May 2, 08:15 UTC | May 2, 08:25 UTC | 10m |
| 2026-04-30 | CDG4632 | HKG → TAO | Apr 30, 10:00 UTC | Apr 30, 10:15 UTC | 15m |
| 2026-04-30 | CDG4631 | TAO → HKG | Apr 30, 07:45 UTC | Apr 30, 08:10 UTC | 25m |
| 2026-04-30 | CDG4631 | TAO → HKG | Apr 30, 06:35 UTC | Apr 30, 07:05 UTC | 30m |
| 2026-04-30 | CDG4642 | PEK → TAO | Apr 30, 02:00 UTC | Apr 30, 02:10 UTC | 10m |
| 2026-04-29 | CDG4618 | ICN → TAO | Apr 29, 13:05 UTC | Apr 29, 13:35 UTC | 30m |
| 2026-04-29 | CDG4617 | TAO → ICN | Apr 29, 11:40 UTC | Apr 29, 11:55 UTC | 15m |
| 2026-04-29 | CDG4616 | ICN → TAO | Apr 29, 08:15 UTC | Apr 29, 08:40 UTC | 25m |
| 2026-04-29 | CDG4615 | TAO → ICN | Apr 29, 06:45 UTC | Apr 29, 06:55 UTC | 10m |
| 2026-04-27 | CDG4632 | HKG → TAO | Apr 27, 10:05 UTC | Apr 27, 10:25 UTC | 20m |
| 2026-04-27 | CDG4631 | TAO → HKG | Apr 27, 07:50 UTC | Apr 27, 08:15 UTC | 25m |
| 2026-04-27 | CDG4631 | TAO → HKG | Apr 27, 06:50 UTC | Apr 27, 07:05 UTC | 15m |
| 2026-04-26 | CDG4631 | TAO → HKG | Apr 26, 11:00 UTC | Apr 27, 07:05 UTC | 20h 5m |
| 2026-04-26 | CDG4632 | HKG → TAO | Apr 26, 10:00 UTC | Apr 27, 07:05 UTC | 21h 5m |
| 2026-04-26 | CDG4631 | TAO → HKG | Apr 26, 06:30 UTC | Apr 26, 07:55 UTC | 1h 25m |
| 2026-04-16 | CDG4610 | ICN → TAO | Apr 16, 03:30 UTC | Apr 16, 03:45 UTC | 15m |
| 2026-04-16 | CDG4609 | TAO → ICN | Apr 16, 02:00 UTC | Apr 16, 02:09 UTC | 10m |
| 2026-04-15 | CDG4632 | HKG → TAO | Apr 15, 09:50 UTC | Apr 15, 10:55 UTC | 1h 5m |
| 2026-04-15 | CDG4631 | TAO → HKG | Apr 15, 07:35 UTC | Apr 15, 07:50 UTC | 15m |
| 2026-04-15 | CDG4631 | TAO → HKG | Apr 15, 06:30 UTC | Apr 15, 06:55 UTC | 25m |
| 2026-04-13 | CDG4092 | - | Apr 13, 04:20 UTC | Apr 13, 05:20 UTC | 1h 0m |
| 2026-04-13 | CDG4092 | - | Apr 13, 04:00 UTC | Apr 13, 04:15 UTC | 15m |
| 2026-04-13 | CDG4091 | TAO → KIX | Apr 13, 00:40 UTC | Apr 13, 02:00 UTC | 1h 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-220W page for operator, model, and routing details .