sensors Mode-S transponder
781CDE
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-221F · BOEING 767-300
- Hex
- 781CDE
- Octal
- 36016336
- Decimal
- 7,871,710
- Country
- CN
- Tail
- B-221F
- Type
- B763
- Flights observed
- 126
- Distinct callsigns
- 13
- Country
- CN
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address 781CDE 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 13 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| HYT9087 | - | 33 | 2026-06-14 |
| HYT9091 | - | 20 | 2026-07-18 |
| HYT9057 | - | 17 | 2026-07-10 |
| HYT9088 | - | 16 | 2026-06-07 |
| HYT9092 | YTO Cargo Ltd | 12 | 2026-07-18 |
| HYT9085 | - | 8 | 2026-06-29 |
| HYT9058 | - | 6 | 2026-07-02 |
| HYT9086 | - | 4 | 2026-06-19 |
| HYT9026 | - | 3 | 2026-06-26 |
| HYT9025 | - | 2 | 2026-06-25 |
| HYT9008 | - | 2 | 2026-06-24 |
| HYT9007 | - | 2 | 2026-06-26 |
| HYT9084 | - | 1 | 2026-04-15 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-18 | HYT9092 | LHE → KMG | Jul 18, 07:40 UTC | Jul 18, 08:50 UTC | 1h 10m |
| 2026-07-18 | HYT9091 | - | Jul 18, 04:45 UTC | Jul 18, 05:50 UTC | 1h 5m |
| 2026-07-15 | HYT9092 | - | Jul 15, 08:40 UTC | Jul 15, 09:55 UTC | 1h 15m |
| 2026-07-15 | HYT9091 | - | Jul 15, 05:00 UTC | Jul 15, 06:15 UTC | 1h 15m |
| 2026-07-12 | HYT9092 | - | Jul 12, 13:55 UTC | Jul 12, 15:10 UTC | 1h 15m |
| 2026-07-12 | HYT9091 | - | Jul 12, 10:45 UTC | Jul 12, 12:01 UTC | 1h 15m |
| 2026-07-11 | HYT9092 | - | Jul 11, 08:15 UTC | Jul 11, 09:00 UTC | 45m |
| 2026-07-11 | HYT9091 | - | Jul 11, 04:25 UTC | Jul 11, 05:40 UTC | 1h 15m |
| 2026-07-10 | HYT9091 | - | Jul 10, 09:35 UTC | Jul 11, 05:40 UTC | 20h 5m |
| 2026-07-10 | HYT9091 | - | Jul 10, 08:35 UTC | Jul 11, 05:40 UTC | 21h 5m |
| 2026-07-10 | HYT9057 | - | Jul 10, 05:20 UTC | Jul 10, 06:35 UTC | 1h 15m |
| 2026-07-09 | HYT9057 | - | Jul 9, 09:35 UTC | Jul 10, 06:35 UTC | 21h 0m |
| 2026-07-09 | HYT9057 | - | Jul 9, 08:45 UTC | Jul 10, 06:35 UTC | 21h 50m |
| 2026-07-08 | HYT9092 | DAC → DAC | Jul 8, 12:05 UTC | Jul 9, 06:20 UTC | 18h 15m |
| 2026-07-08 | HYT9091 | - | Jul 8, 09:25 UTC | Jul 8, 10:30 UTC | 1h 5m |
| 2026-07-07 | HYT9092 | - | Jul 7, 08:00 UTC | Jul 7, 09:10 UTC | 1h 10m |
| 2026-07-07 | HYT9091 | - | Jul 7, 04:20 UTC | Jul 7, 05:55 UTC | 1h 35m |
| 2026-07-06 | HYT9091 | - | Jul 6, 07:35 UTC | Jul 7, 05:55 UTC | 22h 20m |
| 2026-07-06 | HYT9091 | - | Jul 6, 04:45 UTC | Jul 6, 05:45 UTC | 1h 0m |
| 2026-07-05 | HYT9092 | DAC → DAC | Jul 5, 08:05 UTC | Jul 6, 05:45 UTC | 21h 40m |
| 2026-07-05 | HYT9091 | - | Jul 5, 05:05 UTC | Jul 5, 06:25 UTC | 1h 20m |
| 2026-07-04 | HYT9092 | - | Jul 4, 07:50 UTC | Jul 5, 05:30 UTC | 21h 40m |
| 2026-07-04 | HYT9091 | - | Jul 4, 04:45 UTC | Jul 4, 06:00 UTC | 1h 15m |
| 2026-07-03 | HYT9091 | - | Jul 3, 09:35 UTC | Jul 4, 06:00 UTC | 20h 25m |
| 2026-07-03 | HYT9057 | - | Jul 3, 05:50 UTC | Jul 3, 07:05 UTC | 1h 15m |
| 2026-07-02 | HYT9057 | - | Jul 2, 09:35 UTC | Jul 3, 07:05 UTC | 21h 30m |
| 2026-07-02 | HYT9058 | DAC → DAC | Jul 2, 08:55 UTC | Jul 3, 07:05 UTC | 22h 10m |
| 2026-07-01 | HYT9092 | DAC → DAC | Jul 1, 11:50 UTC | Jul 2, 06:51 UTC | 19h 1m |
| 2026-07-01 | HYT9091 | - | Jul 1, 04:35 UTC | Jul 1, 05:50 UTC | 1h 15m |
| 2026-06-30 | HYT9091 | - | Jun 30, 09:35 UTC | Jul 1, 05:50 UTC | 20h 15m |
| 2026-06-30 | HYT9091 | DAC → DAC | Jun 30, 08:55 UTC | Jul 1, 05:50 UTC | 20h 55m |
| 2026-06-30 | HYT9057 | - | Jun 30, 05:20 UTC | Jun 30, 06:35 UTC | 1h 15m |
| 2026-06-29 | HYT9058 | DAC → DAC | Jun 29, 07:44 UTC | Jun 30, 06:35 UTC | 22h 51m |
| 2026-06-29 | HYT9085 | - | Jun 29, 04:45 UTC | Jun 29, 06:05 UTC | 1h 20m |
| 2026-06-28 | HYT9085 | DAC → DAC | Jun 28, 10:35 UTC | Jun 29, 06:05 UTC | 19h 30m |
| 2026-06-28 | HYT9091 | - | Jun 28, 07:40 UTC | Jun 28, 08:34 UTC | 55m |
| 2026-06-27 | HYT9092 | - | Jun 27, 08:05 UTC | Jun 27, 08:49 UTC | 45m |
| 2026-06-26 | HYT9007 | - | Jun 26, 11:34 UTC | Jun 27, 06:50 UTC | 19h 15m |
| 2026-06-26 | HYT9026 | - | Jun 26, 09:35 UTC | Jun 27, 06:50 UTC | 21h 15m |
| 2026-06-26 | HYT9026 | - | Jun 26, 08:50 UTC | Jun 26, 12:00 UTC | 3h 10m |
| 2026-06-25 | HYT9025 | - | Jun 25, 22:29 UTC | Jun 26, 06:25 UTC | 7h 55m |
| 2026-06-24 | HYT9008 | - | Jun 24, 08:45 UTC | Jun 24, 09:15 UTC | 30m |
| 2026-06-24 | HYT9007 | - | Jun 24, 06:15 UTC | Jun 24, 06:55 UTC | 40m |
| 2026-06-22 | HYT9026 | - | Jun 22, 10:40 UTC | Jun 22, 13:49 UTC | 3h 10m |
| 2026-06-22 | HYT9025 | - | Jun 22, 06:25 UTC | Jun 22, 06:39 UTC | 15m |
| 2026-06-21 | HYT9008 | - | Jun 21, 08:35 UTC | Jun 21, 23:30 UTC | 14h 55m |
| 2026-06-21 | HYT9091 | - | Jun 21, 06:10 UTC | Jun 21, 06:50 UTC | 40m |
| 2026-06-20 | HYT9092 | DAC → DAC | Jun 20, 08:44 UTC | Jun 21, 06:50 UTC | 22h 5m |
| 2026-06-20 | HYT9091 | - | Jun 20, 04:54 UTC | Jun 20, 05:44 UTC | 50m |
| 2026-06-19 | HYT9086 | DAC → DAC | Jun 19, 10:24 UTC | Jun 20, 05:44 UTC | 19h 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-221F page for operator, model, and routing details .