sensors Mode-S transponder
780031
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-2830 · BOEING 757-200
- Hex
- 780031
- Octal
- 36000061
- Decimal
- 7,864,369
- Country
- CN
- Tail
- B-2830
- Type
- B752
- Flights observed
- 57
- Distinct callsigns
- 5
- Country
- CN
- Last broadcast
- 8d ago
Last known position
Country allocation
The ICAO 24-bit address 780031 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 5 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-21 | HYT9054 | - | May 21, 18:45 UTC | May 21, 19:55 UTC | 1h 10m |
| 2026-05-21 | HYT9053 | - | May 21, 03:30 UTC | May 21, 17:10 UTC | 13h 40m |
| 2026-05-21 | HYT9051 | - | May 21, 01:00 UTC | May 21, 01:35 UTC | 35m |
| 2026-05-20 | HYT9051 | ICN → ICN | May 20, 03:50 UTC | May 21, 01:35 UTC | 21h 46m |
| 2026-05-20 | HYT9051 | - | May 20, 01:10 UTC | May 20, 01:45 UTC | 35m |
| 2026-05-15 | HYT9054 | - | May 15, 19:25 UTC | May 15, 20:30 UTC | 1h 5m |
| 2026-05-15 | HYT9053 | ICN → MNL | May 15, 04:20 UTC | May 15, 17:55 UTC | 13h 34m |
| 2026-05-14 | HYT9054 | - | May 14, 18:45 UTC | May 15, 01:55 UTC | 7h 10m |
| 2026-05-14 | HYT9053 | - | May 14, 15:45 UTC | May 14, 17:05 UTC | 1h 20m |
| 2026-05-12 | HYT9052 | KUL → HGH | May 12, 03:40 UTC | May 12, 04:20 UTC | 40m |
| 2026-05-11 | HYT9054 | - | May 11, 19:25 UTC | May 11, 20:40 UTC | 1h 15m |
| 2026-05-11 | HYT9053 | - | May 11, 16:00 UTC | May 11, 17:15 UTC | 1h 16m |
| 2026-05-09 | HYT9054 | - | May 9, 19:00 UTC | May 9, 20:25 UTC | 1h 25m |
| 2026-05-09 | HYT9053 | - | May 9, 15:50 UTC | May 9, 17:15 UTC | 1h 25m |
| 2026-05-08 | HYT9054 | - | May 8, 18:40 UTC | May 8, 20:05 UTC | 1h 25m |
| 2026-05-08 | HYT9053 | - | May 8, 03:49 UTC | May 8, 17:20 UTC | 13h 30m |
| 2026-05-08 | 0000000 | - | May 8, 01:45 UTC | May 8, 02:04 UTC | 20m |
| 2026-05-08 | HYT9051 | - | May 8, 01:00 UTC | May 8, 01:40 UTC | 40m |
| 2026-05-07 | HYT9054 | - | May 7, 18:40 UTC | May 7, 20:05 UTC | 1h 25m |
| 2026-05-07 | HYT9053 | - | May 7, 15:50 UTC | May 7, 17:15 UTC | 1h 25m |
| 2026-05-06 | HYT9053 | - | May 6, 18:35 UTC | May 7, 17:15 UTC | 22h 40m |
| 2026-05-06 | HYT9053 | - | May 6, 03:50 UTC | May 6, 17:15 UTC | 13h 25m |
| 2026-05-06 | HYT9051 | - | May 6, 00:50 UTC | May 6, 01:30 UTC | 40m |
| 2026-05-02 | HYT9054 | - | May 2, 18:55 UTC | May 2, 20:05 UTC | 1h 10m |
| 2026-05-02 | HYT9053 | - | May 2, 16:00 UTC | May 2, 17:25 UTC | 1h 25m |
| 2026-05-01 | HYT9052 | KUL → HGH | May 1, 03:45 UTC | May 1, 04:25 UTC | 40m |
| 2026-04-30 | HYT9054 | - | Apr 30, 18:50 UTC | May 1, 01:50 UTC | 7h 0m |
| 2026-04-30 | HYT9053 | - | Apr 30, 15:50 UTC | Apr 30, 17:25 UTC | 1h 35m |
| 2026-04-29 | HYT9054 | - | Apr 29, 18:50 UTC | Apr 29, 20:00 UTC | 1h 10m |
| 2026-04-29 | HYT9053 | - | Apr 29, 15:25 UTC | Apr 29, 17:15 UTC | 1h 50m |
| 2026-04-28 | HYT9052 | KUL → HGH | Apr 28, 03:45 UTC | Apr 28, 04:30 UTC | 45m |
| 2026-04-28 | HYT9051 | - | Apr 28, 01:15 UTC | Apr 28, 01:50 UTC | 35m |
| 2026-04-24 | HYT9052 | KUL → HGH | Apr 24, 03:45 UTC | Apr 24, 04:30 UTC | 45m |
| 2026-04-24 | HYT9051 | - | Apr 24, 00:45 UTC | Apr 24, 01:30 UTC | 45m |
| 2026-04-23 | HYT9054 | - | Apr 23, 18:50 UTC | Apr 23, 20:05 UTC | 1h 15m |
| 2026-04-23 | HYT9053 | - | Apr 23, 03:50 UTC | Apr 23, 17:20 UTC | 13h 30m |
| 2026-04-23 | HYT9051 | - | Apr 23, 01:00 UTC | Apr 23, 01:35 UTC | 35m |
| 2026-04-22 | HYT9054 | - | Apr 22, 19:15 UTC | Apr 22, 20:30 UTC | 1h 15m |
| 2026-04-22 | HYT9053 | - | Apr 22, 15:25 UTC | Apr 22, 17:20 UTC | 1h 55m |
| 2026-04-21 | HYT9052 | KUL → HGH | Apr 21, 03:45 UTC | Apr 21, 04:25 UTC | 40m |
| 2026-04-20 | HYT9054 | - | Apr 20, 18:30 UTC | Apr 21, 01:30 UTC | 7h 0m |
| 2026-04-20 | HYT9053 | - | Apr 20, 15:15 UTC | Apr 20, 17:15 UTC | 2h 0m |
| 2026-04-17 | HYT9054 | - | Apr 17, 19:30 UTC | Apr 17, 20:40 UTC | 1h 10m |
| 2026-04-17 | HYT9054 | - | Apr 17, 18:45 UTC | Apr 17, 19:10 UTC | 25m |
| 2026-04-17 | HYT9053 | - | Apr 17, 15:20 UTC | Apr 17, 17:15 UTC | 1h 55m |
| 2026-04-16 | HYT9052 | KUL → HGH | Apr 16, 03:55 UTC | Apr 16, 04:29 UTC | 35m |
| 2026-04-16 | HYT9051 | - | Apr 16, 01:10 UTC | Apr 16, 01:55 UTC | 45m |
| 2026-04-15 | HYT9054 | - | Apr 15, 19:10 UTC | Apr 15, 20:50 UTC | 1h 40m |
| 2026-04-15 | HYT9053 | - | Apr 15, 17:05 UTC | Apr 15, 17:25 UTC | 20m |
| 2026-04-15 | HYT9052 | KUL → HGH | Apr 15, 03:25 UTC | Apr 15, 04:05 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-2830 page for operator, model, and routing details .