sensors Mode-S transponder
780D02
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-1716 · BOEING 737-800
- Hex
- 780D02
- Octal
- 36006402
- Decimal
- 7,867,650
- Country
- CN
- Tail
- B-1716
- Type
- B738
- Flights observed
- 42
- Distinct callsigns
- 16
- Country
- CN
- Last broadcast
- Jul 26, 06:25 UTC
Last known position
Country allocation
The ICAO 24-bit address 780D02 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 16 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| JYH1697 | - | 13 | 2026-07-25 |
| JYH1266 | 9 Air | 6 | 2026-07-22 |
| JYH1265 | 9 Air | 5 | 2026-07-22 |
| JYH1574 | - | 3 | 2026-07-20 |
| JYH1680 | 9 Air | 2 | 2026-07-25 |
| JYH1571 | - | 2 | 2026-07-01 |
| JYH1268 | 9 Air | 2 | 2026-04-16 |
| JYH1717 | 9 Air | 1 | 2026-04-21 |
| JYH1573 | - | 1 | 2026-07-19 |
| JYH1572 | - | 1 | 2026-07-01 |
| JYH1564 | - | 1 | 2026-07-09 |
| JYH1412 | - | 1 | 2026-07-06 |
| JYH1411 | - | 1 | 2026-07-06 |
| JYH1313 | 9 Air | 1 | 2026-06-06 |
| JYH1025 | - | 1 | 2026-07-10 |
| JYH1024 | 9 Air | 1 | 2026-07-21 |
Recent flights last 42
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-25 | JYH1680 | CGO → HAK | Jul 25, 13:20 UTC | Jul 26, 06:25 UTC | 17h 5m |
| 2026-07-25 | JYH1697 | - | Jul 25, 06:35 UTC | Jul 26, 06:25 UTC | 23h 50m |
| 2026-07-22 | JYH1266 | BKK → CAN | Jul 22, 18:20 UTC | Jul 22, 18:45 UTC | 25m |
| 2026-07-22 | JYH1265 | CAN → BKK | Jul 22, 14:40 UTC | Jul 22, 16:55 UTC | 2h 15m |
| 2026-07-21 | JYH1024 | HAK → CAN | Jul 21, 06:50 UTC | Jul 21, 07:00 UTC | 10m |
| 2026-07-20 | JYH1574 | - | Jul 20, 11:25 UTC | Jul 20, 11:40 UTC | 15m |
| 2026-07-19 | JYH1573 | - | Jul 19, 03:00 UTC | Jul 19, 03:20 UTC | 20m |
| 2026-07-17 | JYH1697 | - | Jul 17, 06:15 UTC | Jul 17, 06:29 UTC | 15m |
| 2026-07-16 | JYH1697 | - | Jul 16, 06:15 UTC | Jul 16, 06:25 UTC | 10m |
| 2026-07-15 | JYH1697 | - | Jul 15, 06:35 UTC | Jul 16, 06:25 UTC | 23h 50m |
| 2026-07-14 | JYH1697 | - | Jul 14, 06:15 UTC | Jul 14, 06:30 UTC | 15m |
| 2026-07-13 | JYH1697 | - | Jul 13, 06:15 UTC | Jul 13, 06:30 UTC | 15m |
| 2026-07-12 | JYH1697 | - | Jul 12, 06:05 UTC | Jul 12, 06:15 UTC | 10m |
| 2026-07-11 | JYH1697 | - | Jul 11, 06:20 UTC | Jul 11, 06:30 UTC | 10m |
| 2026-07-10 | JYH1025 | - | Jul 10, 22:35 UTC | Jul 10, 22:45 UTC | 10m |
| 2026-07-09 | JYH1564 | - | Jul 9, 12:55 UTC | Jul 9, 13:10 UTC | 15m |
| 2026-07-06 | JYH1412 | - | Jul 6, 11:35 UTC | Jul 7, 07:55 UTC | 20h 20m |
| 2026-07-06 | JYH1411 | - | Jul 6, 07:15 UTC | Jul 6, 11:45 UTC | 4h 30m |
| 2026-07-01 | JYH1572 | - | Jul 1, 08:20 UTC | Jul 2, 01:35 UTC | 17h 15m |
| 2026-07-01 | JYH1571 | - | Jul 1, 04:15 UTC | Jul 2, 01:35 UTC | 21h 20m |
| 2026-06-25 | JYH1266 | - | Jun 25, 21:44 UTC | Jun 25, 23:24 UTC | 1h 40m |
| 2026-06-25 | JYH1265 | - | Jun 25, 17:54 UTC | Jun 25, 19:29 UTC | 1h 35m |
| 2026-06-24 | JYH1680 | - | Jun 24, 13:20 UTC | Jun 24, 13:30 UTC | 10m |
| 2026-06-24 | JYH1697 | - | Jun 24, 06:15 UTC | Jun 24, 06:25 UTC | 10m |
| 2026-06-22 | JYH1697 | - | Jun 22, 13:44 UTC | Jun 23, 06:24 UTC | 16h 40m |
| 2026-06-22 | JYH1697 | - | Jun 22, 06:05 UTC | Jun 23, 01:50 UTC | 19h 45m |
| 2026-06-15 | JYH1571 | - | Jun 15, 04:10 UTC | Jun 15, 09:00 UTC | 4h 50m |
| 2026-06-06 | JYH1313 | KWE → NGB | Jun 6, 00:40 UTC | Jun 6, 01:20 UTC | 40m |
| 2026-06-02 | JYH1266 | BKK → CAN | Jun 2, 18:55 UTC | Jun 3, 12:40 UTC | 17h 45m |
| 2026-06-02 | JYH1266 | BKK → CAN | Jun 2, 17:30 UTC | Jun 3, 12:40 UTC | 19h 10m |
| 2026-06-02 | JYH1265 | CAN → BKK | Jun 2, 13:45 UTC | Jun 2, 15:50 UTC | 2h 5m |
| 2026-05-07 | JYH1697 | - | May 7, 06:15 UTC | May 7, 06:30 UTC | 15m |
| 2026-05-06 | JYH1697 | - | May 6, 08:35 UTC | May 7, 06:30 UTC | 21h 54m |
| 2026-05-01 | JYH1574 | SHE → NGB | May 1, 11:40 UTC | May 1, 11:50 UTC | 10m |
| 2026-04-29 | JYH1574 | SHE → NGB | Apr 29, 13:30 UTC | Apr 30, 03:35 UTC | 14h 4m |
| 2026-04-21 | JYH1717 | CAN → SQD | Apr 21, 23:10 UTC | Apr 21, 23:20 UTC | 10m |
| 2026-04-21 | JYH1266 | BKK → CAN | Apr 21, 17:35 UTC | Apr 21, 18:10 UTC | 35m |
| 2026-04-21 | JYH1265 | CAN → BKK | Apr 21, 14:45 UTC | Apr 21, 15:31 UTC | 45m |
| 2026-04-18 | JYH1266 | BKK → CAN | Apr 18, 17:15 UTC | Apr 19, 13:10 UTC | 19h 55m |
| 2026-04-18 | JYH1265 | CAN → BKK | Apr 18, 15:35 UTC | Apr 18, 15:50 UTC | 15m |
| 2026-04-16 | JYH1268 | BKK → CAN | Apr 16, 22:10 UTC | Apr 16, 22:20 UTC | 10m |
| 2026-04-16 | JYH1268 | BKK → CAN | Apr 16, 19:25 UTC | Apr 16, 19:35 UTC | 10m |
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-1716 page for operator, model, and routing details .