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
- 48
- Distinct callsigns
- 7
- Country
- CN
- Last broadcast
- 17h 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 7 distinct
Recent flights last 48
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | HYT9086 | - | Jun 2, 12:45 UTC | Jun 2, 13:00 UTC | 15m |
| 2026-06-02 | HYT9057 | - | Jun 2, 10:30 UTC | Jun 2, 11:25 UTC | 55m |
| 2026-06-01 | HYT9058 | - | Jun 1, 08:40 UTC | Jun 1, 08:55 UTC | 15m |
| 2026-06-01 | HYT9085 | - | Jun 1, 04:50 UTC | Jun 1, 05:40 UTC | 50m |
| 2026-05-30 | HYT9088 | - | May 30, 07:40 UTC | May 30, 08:35 UTC | 55m |
| 2026-05-30 | HYT9087 | - | May 30, 04:55 UTC | May 30, 05:55 UTC | 1h 0m |
| 2026-05-22 | HYT9088 | - | May 22, 08:15 UTC | May 22, 09:15 UTC | 1h 0m |
| 2026-05-22 | HYT9057 | - | May 22, 06:05 UTC | May 22, 06:50 UTC | 45m |
| 2026-05-21 | HYT9057 | - | May 21, 09:35 UTC | May 22, 06:50 UTC | 21h 15m |
| 2026-05-21 | HYT9058 | DAC → DAC | May 21, 08:45 UTC | May 22, 06:50 UTC | 22h 5m |
| 2026-05-21 | HYT9087 | - | May 21, 07:00 UTC | May 21, 07:25 UTC | 25m |
| 2026-05-20 | HYT9087 | - | May 20, 09:35 UTC | May 21, 07:25 UTC | 21h 50m |
| 2026-05-20 | HYT9088 | DAC → DAC | May 20, 09:25 UTC | May 21, 07:25 UTC | 22h 0m |
| 2026-05-20 | HYT9087 | - | May 20, 05:05 UTC | May 20, 05:50 UTC | 45m |
| 2026-05-19 | HYT9087 | - | May 19, 07:35 UTC | May 20, 05:50 UTC | 22h 16m |
| 2026-05-19 | HYT9087 | - | May 19, 05:05 UTC | May 19, 05:50 UTC | 45m |
| 2026-05-18 | HYT9087 | DAC → DAC | May 18, 08:01 UTC | May 19, 05:50 UTC | 21h 49m |
| 2026-05-18 | HYT9087 | - | May 18, 05:30 UTC | May 18, 06:10 UTC | 40m |
| 2026-05-17 | HYT9087 | - | May 17, 08:15 UTC | May 18, 06:10 UTC | 21h 55m |
| 2026-05-17 | HYT9087 | - | May 17, 05:30 UTC | May 17, 05:55 UTC | 25m |
| 2026-05-16 | HYT9088 | - | May 16, 11:16 UTC | May 16, 11:46 UTC | 30m |
| 2026-05-15 | HYT9087 | - | May 15, 15:35 UTC | May 16, 09:45 UTC | 18h 11m |
| 2026-05-15 | HYT9087 | - | May 15, 14:55 UTC | May 16, 09:45 UTC | 18h 51m |
| 2026-05-15 | HYT9087 | - | May 15, 12:05 UTC | May 15, 13:00 UTC | 55m |
| 2026-05-13 | HYT9088 | - | May 13, 07:30 UTC | May 13, 08:10 UTC | 40m |
| 2026-05-13 | HYT9087 | - | May 13, 05:20 UTC | May 13, 06:00 UTC | 40m |
| 2026-05-11 | HYT9088 | - | May 11, 09:25 UTC | May 11, 10:00 UTC | 35m |
| 2026-05-11 | HYT9087 | - | May 11, 06:40 UTC | May 11, 07:35 UTC | 55m |
| 2026-05-10 | HYT9087 | - | May 10, 12:30 UTC | May 11, 07:35 UTC | 19h 5m |
| 2026-05-10 | HYT9087 | - | May 10, 09:50 UTC | May 10, 11:10 UTC | 1h 20m |
| 2026-05-09 | HYT9087 | - | May 9, 14:10 UTC | May 10, 11:10 UTC | 21h 0m |
| 2026-05-09 | HYT9087 | - | May 9, 11:10 UTC | May 9, 12:15 UTC | 1h 5m |
| 2026-05-06 | HYT9088 | - | May 6, 08:30 UTC | May 6, 09:15 UTC | 45m |
| 2026-05-06 | HYT9087 | - | May 6, 06:25 UTC | May 6, 07:05 UTC | 40m |
| 2026-05-04 | HYT9088 | - | May 4, 08:55 UTC | May 4, 09:25 UTC | 30m |
| 2026-05-04 | HYT9087 | - | May 4, 06:35 UTC | May 4, 07:20 UTC | 45m |
| 2026-05-03 | HYT9088 | DAC → DAC | May 3, 08:05 UTC | May 4, 07:20 UTC | 23h 15m |
| 2026-05-03 | HYT9087 | - | May 3, 05:40 UTC | May 3, 06:35 UTC | 55m |
| 2026-05-01 | HYT9088 | - | May 1, 12:50 UTC | May 1, 13:20 UTC | 30m |
| 2026-05-01 | HYT9087 | - | May 1, 10:45 UTC | May 1, 11:35 UTC | 50m |
| 2026-04-30 | HYT9088 | - | Apr 30, 09:30 UTC | Apr 30, 10:00 UTC | 30m |
| 2026-04-30 | HYT9087 | - | Apr 30, 07:05 UTC | Apr 30, 08:00 UTC | 55m |
| 2026-04-22 | HYT9088 | - | Apr 22, 08:10 UTC | Apr 22, 08:50 UTC | 40m |
| 2026-04-22 | HYT9087 | - | Apr 22, 04:55 UTC | Apr 22, 06:10 UTC | 1h 15m |
| 2026-04-20 | HYT9088 | - | Apr 20, 21:30 UTC | Apr 20, 22:15 UTC | 45m |
| 2026-04-20 | HYT9087 | - | Apr 20, 18:50 UTC | Apr 20, 20:00 UTC | 1h 10m |
| 2026-04-15 | HYT9084 | - | Apr 15, 11:10 UTC | Apr 15, 11:55 UTC | 45m |
| 2026-04-15 | HYT9057 | - | Apr 15, 07:01 UTC | Apr 15, 08:15 UTC | 1h 15m |
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 .