sensors Mode-S transponder
781EC9
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-222F · BOEING 757-200
- Hex
- 781EC9
- Octal
- 36017311
- Decimal
- 7,872,201
- Country
- CN
- Tail
- B-222F
- Type
- B752
- Flights observed
- 116
- Distinct callsigns
- 4
- Country
- CN
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address 781EC9 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 4 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| HYT9051 | - | 50 | 2026-07-24 |
| HYT9052 | YTO Cargo Ltd | 30 | 2026-07-24 |
| HYT9053 | - | 19 | 2026-07-17 |
| HYT9054 | - | 16 | 2026-07-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-24 | HYT9052 | KUL → HGH | Jul 24, 03:40 UTC | Jul 24, 04:20 UTC | 40m |
| 2026-07-24 | HYT9051 | - | Jul 24, 01:10 UTC | Jul 24, 01:55 UTC | 45m |
| 2026-07-23 | HYT9052 | KUL → HGH | Jul 23, 04:10 UTC | Jul 23, 04:50 UTC | 40m |
| 2026-07-23 | HYT9051 | - | Jul 23, 01:00 UTC | Jul 23, 01:40 UTC | 40m |
| 2026-07-22 | HYT9051 | - | Jul 22, 01:15 UTC | Jul 22, 01:55 UTC | 40m |
| 2026-07-21 | HYT9051 | - | Jul 21, 04:20 UTC | Jul 22, 01:55 UTC | 21h 35m |
| 2026-07-21 | HYT9052 | KUL → HGH | Jul 21, 03:55 UTC | Jul 22, 01:55 UTC | 22h 0m |
| 2026-07-21 | HYT9051 | - | Jul 21, 01:10 UTC | Jul 21, 01:50 UTC | 40m |
| 2026-07-20 | HYT9051 | - | Jul 20, 04:20 UTC | Jul 21, 01:50 UTC | 21h 30m |
| 2026-07-20 | HYT9052 | ICN → ICN | Jul 20, 04:05 UTC | Jul 21, 01:50 UTC | 21h 45m |
| 2026-07-20 | HYT9051 | - | Jul 20, 01:00 UTC | Jul 20, 01:40 UTC | 40m |
| 2026-07-17 | HYT9054 | - | Jul 17, 21:34 UTC | Jul 17, 23:14 UTC | 1h 40m |
| 2026-07-17 | HYT9053 | ICN → MNL | Jul 17, 04:10 UTC | Jul 17, 19:55 UTC | 15h 45m |
| 2026-07-17 | HYT9051 | - | Jul 17, 01:20 UTC | Jul 17, 01:55 UTC | 35m |
| 2026-07-16 | HYT9052 | - | Jul 16, 04:05 UTC | Jul 16, 04:45 UTC | 40m |
| 2026-07-16 | HYT9051 | - | Jul 16, 01:45 UTC | Jul 16, 02:25 UTC | 40m |
| 2026-07-15 | HYT9054 | - | Jul 15, 20:00 UTC | Jul 15, 21:35 UTC | 1h 35m |
| 2026-07-15 | HYT9053 | - | Jul 15, 16:20 UTC | Jul 15, 18:10 UTC | 1h 50m |
| 2026-07-15 | HYT9052 | - | Jul 15, 03:25 UTC | Jul 15, 04:10 UTC | 45m |
| 2026-07-15 | HYT9051 | - | Jul 15, 01:00 UTC | Jul 15, 01:40 UTC | 40m |
| 2026-07-14 | HYT9051 | - | Jul 14, 04:20 UTC | Jul 15, 01:40 UTC | 21h 19m |
| 2026-07-14 | HYT9052 | ICN → ICN | Jul 14, 03:45 UTC | Jul 15, 01:40 UTC | 21h 54m |
| 2026-07-14 | HYT9051 | - | Jul 14, 01:15 UTC | Jul 14, 02:00 UTC | 45m |
| 2026-07-13 | HYT9054 | - | Jul 13, 19:40 UTC | Jul 13, 21:15 UTC | 1h 35m |
| 2026-07-13 | HYT9053 | - | Jul 13, 05:35 UTC | Jul 13, 17:40 UTC | 12h 5m |
| 2026-07-12 | HYT9051 | ICN → ICN | Jul 12, 09:05 UTC | Jul 13, 03:40 UTC | 18h 35m |
| 2026-07-10 | HYT9051 | - | Jul 10, 01:00 UTC | Jul 10, 01:40 UTC | 40m |
| 2026-07-09 | HYT9052 | - | Jul 9, 03:25 UTC | Jul 9, 04:05 UTC | 40m |
| 2026-07-09 | HYT9051 | - | Jul 9, 01:05 UTC | Jul 9, 01:50 UTC | 45m |
| 2026-07-08 | HYT9054 | - | Jul 8, 18:55 UTC | Jul 8, 19:25 UTC | 30m |
| 2026-07-08 | HYT9053 | - | Jul 8, 16:40 UTC | Jul 8, 17:15 UTC | 35m |
| 2026-07-08 | HYT9052 | - | Jul 8, 05:55 UTC | Jul 8, 06:35 UTC | 40m |
| 2026-07-08 | HYT9051 | - | Jul 8, 01:05 UTC | Jul 8, 01:55 UTC | 50m |
| 2026-07-07 | HYT9052 | ICN → ICN | Jul 7, 03:55 UTC | Jul 8, 01:55 UTC | 22h 0m |
| 2026-07-07 | HYT9051 | - | Jul 7, 01:10 UTC | Jul 7, 01:55 UTC | 45m |
| 2026-07-06 | HYT9054 | - | Jul 6, 18:55 UTC | Jul 6, 20:10 UTC | 1h 15m |
| 2026-07-06 | HYT9053 | ICN → MNL | Jul 6, 04:20 UTC | Jul 6, 17:15 UTC | 12h 55m |
| 2026-07-06 | HYT9051 | - | Jul 6, 01:35 UTC | Jul 6, 02:15 UTC | 40m |
| 2026-07-04 | HYT9054 | - | Jul 4, 19:20 UTC | Jul 4, 20:35 UTC | 1h 15m |
| 2026-07-04 | HYT9053 | - | Jul 4, 16:00 UTC | Jul 4, 17:25 UTC | 1h 25m |
| 2026-07-03 | HYT9053 | - | Jul 3, 20:20 UTC | Jul 4, 17:25 UTC | 21h 5m |
| 2026-07-03 | HYT9054 | - | Jul 3, 19:30 UTC | Jul 4, 17:25 UTC | 21h 55m |
| 2026-07-03 | HYT9053 | ICN → MNL | Jul 3, 03:40 UTC | Jul 3, 18:05 UTC | 14h 25m |
| 2026-07-03 | HYT9051 | - | Jul 3, 01:05 UTC | Jul 3, 01:55 UTC | 50m |
| 2026-07-02 | HYT9051 | - | Jul 2, 03:30 UTC | Jul 3, 01:55 UTC | 22h 25m |
| 2026-07-02 | HYT9051 | - | Jul 2, 01:10 UTC | Jul 2, 01:45 UTC | 35m |
| 2026-07-01 | HYT9054 | - | Jul 1, 19:00 UTC | Jul 1, 20:25 UTC | 1h 25m |
| 2026-07-01 | HYT9053 | - | Jul 1, 15:55 UTC | Jul 1, 17:20 UTC | 1h 25m |
| 2026-07-01 | HYT9052 | - | Jul 1, 03:50 UTC | Jul 1, 04:35 UTC | 45m |
| 2026-07-01 | HYT9051 | - | Jul 1, 01:00 UTC | Jul 1, 01:40 UTC | 40m |
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-222F page for operator, model, and routing details .