sensors Mode-S transponder
782031
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-1592 · BOEING 737-800
- Hex
- 782031
- Octal
- 36020061
- Decimal
- 7,872,561
- Country
- CN
- Tail
- B-1592
- Type
- B738
- Flights observed
- 34
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 782031 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 |
|---|---|---|---|
| JYH1002 | - | 5 | 2026-07-14 |
| JYH1572 | 9 Air | 3 | 2026-05-08 |
| JYH1231 | 9 Air | 3 | 2026-04-18 |
| JYH1718 | - | 2 | 2026-07-17 |
| JYH1266 | 9 Air | 2 | 2026-05-18 |
| JYH1265 | 9 Air | 2 | 2026-05-18 |
| JYH1019 | - | 2 | 2026-07-13 |
| JYH1717 | - | 1 | 2026-07-10 |
| JYH1585 | 9 Air | 1 | 2026-05-03 |
| JYH1571 | 9 Air | 1 | 2026-05-04 |
| JYH1268 | 9 Air | 1 | 2026-05-27 |
| JYH1267 | 9 Air | 1 | 2026-05-27 |
| JYH1232 | 9 Air | 1 | 2026-04-18 |
| JYH1184 | - | 1 | 2026-07-11 |
| JYH1145 | 9 Air | 1 | 2026-05-11 |
| JYH1113 | 9 Air | 1 | 2026-04-21 |
| JYH1025 | 9 Air | 1 | 2026-06-19 |
| JYH1022 | - | 1 | 2026-06-24 |
| JYH1021 | - | 1 | 2026-06-24 |
| JYH1001 | 9 Air | 1 | 2026-07-07 |
Recent flights last 34
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | JYH1718 | - | Jul 17, 02:45 UTC | Jul 17, 13:00 UTC | 10h 15m |
| 2026-07-14 | JYH1002 | - | Jul 14, 13:30 UTC | Jul 14, 13:40 UTC | 10m |
| 2026-07-13 | JYH1019 | - | Jul 13, 23:55 UTC | Jul 14, 00:55 UTC | 1h 0m |
| 2026-07-11 | JYH1184 | - | Jul 11, 08:20 UTC | Jul 11, 08:30 UTC | 10m |
| 2026-07-10 | JYH1717 | - | Jul 10, 02:25 UTC | Jul 10, 13:05 UTC | 10h 40m |
| 2026-07-07 | JYH1002 | - | Jul 7, 15:55 UTC | Jul 7, 16:10 UTC | 15m |
| 2026-07-07 | JYH1001 | CAN → PKX | Jul 7, 13:55 UTC | Jul 7, 14:10 UTC | 15m |
| 2026-07-05 | JYH1002 | - | Jul 5, 13:30 UTC | Jul 5, 13:45 UTC | 15m |
| 2026-06-30 | JYH1002 | - | Jun 30, 13:30 UTC | Jun 30, 13:45 UTC | 15m |
| 2026-06-26 | - | - | Jun 26, 19:20 UTC | Jun 26, 19:30 UTC | 10m |
| 2026-06-25 | JYH1002 | PKX → CAN | Jun 25, 19:39 UTC | Jun 25, 19:49 UTC | 10m |
| 2026-06-24 | JYH1022 | - | Jun 24, 17:20 UTC | Jun 24, 17:29 UTC | 10m |
| 2026-06-24 | JYH1021 | - | Jun 24, 10:45 UTC | Jun 24, 10:55 UTC | 10m |
| 2026-06-22 | JYH1019 | - | Jun 22, 23:45 UTC | Jun 22, 23:55 UTC | 10m |
| 2026-06-19 | JYH1025 | CAN → HAK | Jun 19, 22:39 UTC | Jun 19, 22:49 UTC | 10m |
| 2026-05-27 | JYH1268 | BKK → CAN | May 27, 19:15 UTC | May 27, 20:50 UTC | 1h 35m |
| 2026-05-27 | JYH1267 | CAN → BKK | May 27, 15:30 UTC | May 27, 17:35 UTC | 2h 5m |
| 2026-05-18 | JYH1266 | BKK → CAN | May 18, 17:20 UTC | May 18, 17:50 UTC | 30m |
| 2026-05-18 | JYH1265 | CAN → BKK | May 18, 03:55 UTC | May 18, 15:15 UTC | 11h 20m |
| 2026-05-13 | JYH1718 | - | May 13, 02:55 UTC | May 13, 12:50 UTC | 9h 55m |
| 2026-05-11 | JYH1145 | CAN → BAR | May 11, 14:55 UTC | May 11, 15:05 UTC | 10m |
| 2026-05-08 | JYH1572 | YNJ → NGB | May 8, 04:19 UTC | May 8, 08:34 UTC | 4h 15m |
| 2026-05-04 | JYH1571 | NGB → YNJ | May 4, 04:20 UTC | May 4, 08:20 UTC | 4h 0m |
| 2026-05-03 | JYH1585 | NKG → CGQ | May 3, 09:35 UTC | May 4, 08:00 UTC | 22h 25m |
| 2026-04-23 | JYH1266 | BKK → CAN | Apr 23, 19:05 UTC | Apr 23, 19:40 UTC | 35m |
| 2026-04-23 | JYH1265 | CAN → BKK | Apr 23, 15:35 UTC | Apr 23, 17:50 UTC | 2h 15m |
| 2026-04-23 | - | - | Apr 23, 13:45 UTC | Apr 23, 13:55 UTC | 10m |
| 2026-04-21 | JYH1113 | CAN → SYX | Apr 21, 22:45 UTC | Apr 21, 23:00 UTC | 15m |
| 2026-04-19 | JYH1572 | YNJ → NGB | Apr 19, 01:05 UTC | Apr 19, 08:35 UTC | 7h 30m |
| 2026-04-18 | JYH1572 | YNJ → NGB | Apr 18, 10:20 UTC | Apr 19, 08:35 UTC | 22h 15m |
| 2026-04-18 | JYH1232 | VTE → NGB | Apr 18, 10:00 UTC | Apr 19, 08:00 UTC | 22h 0m |
| 2026-04-18 | JYH1231 | NGB → VTE | Apr 18, 05:25 UTC | Apr 18, 05:45 UTC | 20m |
| 2026-04-18 | JYH1231 | NGB → VTE | Apr 18, 04:50 UTC | Apr 19, 04:15 UTC | 23h 25m |
| 2026-04-18 | JYH1231 | NGB → VTE | Apr 18, 01:10 UTC | Apr 18, 11:10 UTC | 10h 0m |
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-1592 page for operator, model, and routing details .