sensors Mode-S transponder
780D03
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-1719 · BOEING 737-800
- Hex
- 780D03
- Octal
- 36006403
- Decimal
- 7,867,651
- Country
- CN
- Tail
- B-1719
- Type
- B738
- Flights observed
- 44
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address 780D03 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 |
|---|---|---|---|
| JYH1574 | - | 6 | 2026-07-01 |
| JYH1572 | 9 Air | 4 | 2026-07-24 |
| JYH1564 | - | 4 | 2026-07-14 |
| JYH1266 | 9 Air | 4 | 2026-05-19 |
| JYH1265 | 9 Air | 4 | 2026-05-19 |
| JYH1268 | - | 2 | 2026-06-18 |
| JYH1267 | - | 2 | 2026-06-18 |
| JYH1697 | - | 1 | 2026-04-19 |
| JYH1573 | - | 1 | 2026-06-22 |
| JYH1318 | - | 1 | 2026-07-13 |
| JYH1280 | 9 Air | 1 | 2026-06-21 |
| JYH1279 | 9 Air | 1 | 2026-06-21 |
| JYH1278 | 9 Air | 1 | 2026-06-21 |
| JYH1272 | - | 1 | 2026-07-16 |
| JYH1271 | - | 1 | 2026-07-16 |
| JYH1138 | - | 1 | 2026-07-03 |
| JYH1111 | 9 Air | 1 | 2026-05-11 |
| JYH1072 | 9 Air | 1 | 2026-05-30 |
| JYH1035 | 9 Air | 1 | 2026-06-23 |
| JYH1029 | 9 Air | 1 | 2026-07-20 |
Recent flights last 44
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-24 | JYH1572 | YNJ → NGB | Jul 24, 01:25 UTC | Jul 24, 09:00 UTC | 7h 35m |
| 2026-07-20 | JYH1029 | CAN → NKG | Jul 20, 00:30 UTC | Jul 20, 00:40 UTC | 10m |
| 2026-07-16 | JYH1272 | - | Jul 16, 18:05 UTC | Jul 16, 18:19 UTC | 15m |
| 2026-07-16 | JYH1271 | - | Jul 16, 13:00 UTC | Jul 16, 16:35 UTC | 3h 35m |
| 2026-07-14 | JYH1564 | - | Jul 14, 00:50 UTC | Jul 14, 12:30 UTC | 11h 40m |
| 2026-07-13 | JYH1318 | - | Jul 13, 03:40 UTC | Jul 14, 00:50 UTC | 21h 10m |
| 2026-07-11 | - | - | Jul 11, 22:50 UTC | Jul 11, 23:00 UTC | 10m |
| 2026-07-06 | JYH1572 | - | Jul 6, 04:25 UTC | Jul 6, 08:50 UTC | 4h 25m |
| 2026-07-05 | JYH1572 | - | Jul 5, 07:50 UTC | Jul 6, 04:35 UTC | 20h 45m |
| 2026-07-05 | JYH1572 | - | Jul 5, 04:05 UTC | Jul 5, 08:40 UTC | 4h 35m |
| 2026-07-03 | JYH1138 | - | Jul 3, 05:15 UTC | Jul 3, 09:50 UTC | 4h 35m |
| 2026-07-01 | JYH1574 | - | Jul 1, 11:50 UTC | Jul 1, 12:00 UTC | 10m |
| 2026-06-27 | JYH1564 | - | Jun 27, 11:59 UTC | Jun 27, 12:09 UTC | 10m |
| 2026-06-23 | JYH1035 | CAN → NKG | Jun 23, 22:49 UTC | Jun 23, 23:00 UTC | 10m |
| 2026-06-23 | JYH1564 | - | Jun 23, 11:49 UTC | Jun 23, 11:59 UTC | 10m |
| 2026-06-22 | JYH1573 | - | Jun 22, 03:30 UTC | Jun 22, 03:40 UTC | 10m |
| 2026-06-21 | JYH1278 | VTE → CAN | Jun 21, 13:50 UTC | Jun 21, 17:24 UTC | 3h 35m |
| 2026-06-21 | JYH1280 | DMK → CAN | Jun 21, 08:35 UTC | Jun 21, 10:09 UTC | 1h 35m |
| 2026-06-21 | JYH1279 | CAN → DMK | Jun 21, 02:20 UTC | Jun 21, 04:30 UTC | 2h 10m |
| 2026-06-19 | - | - | Jun 19, 02:29 UTC | Jun 19, 02:39 UTC | 10m |
| 2026-06-18 | JYH1268 | - | Jun 18, 22:20 UTC | Jun 18, 23:50 UTC | 1h 30m |
| 2026-06-18 | JYH1267 | - | Jun 18, 18:40 UTC | Jun 18, 20:45 UTC | 2h 5m |
| 2026-06-12 | JYH1574 | SHE → NGB | Jun 12, 12:25 UTC | Jun 12, 12:35 UTC | 10m |
| 2026-06-09 | - | - | Jun 9, 23:00 UTC | Jun 9, 23:30 UTC | 30m |
| 2026-06-07 | JYH1574 | SHE → NGB | Jun 7, 11:40 UTC | Jun 7, 11:55 UTC | 15m |
| 2026-06-05 | JYH1574 | SHE → NGB | Jun 5, 11:45 UTC | Jun 5, 11:55 UTC | 10m |
| 2026-06-03 | JYH1574 | SHE → NGB | Jun 3, 11:45 UTC | Jun 3, 12:05 UTC | 20m |
| 2026-05-30 | JYH1072 | HGH → CAN | May 30, 10:05 UTC | May 30, 10:45 UTC | 40m |
| 2026-05-26 | - | - | May 26, 05:15 UTC | May 26, 05:25 UTC | 10m |
| 2026-05-21 | JYH1268 | BKK → CAN | May 21, 20:50 UTC | May 21, 21:15 UTC | 25m |
| 2026-05-21 | JYH1267 | CAN → BKK | May 21, 18:55 UTC | May 21, 19:25 UTC | 30m |
| 2026-05-19 | JYH1266 | BKK → CAN | May 19, 17:30 UTC | May 19, 18:00 UTC | 30m |
| 2026-05-19 | JYH1265 | CAN → BKK | May 19, 13:50 UTC | May 19, 15:55 UTC | 2h 5m |
| 2026-05-11 | JYH1111 | CAN → SYX | May 11, 12:30 UTC | May 11, 12:40 UTC | 10m |
| 2026-05-10 | JYH1266 | BKK → CAN | May 10, 17:45 UTC | May 10, 18:29 UTC | 45m |
| 2026-05-10 | JYH1265 | CAN → BKK | May 10, 13:44 UTC | May 10, 16:00 UTC | 2h 15m |
| 2026-05-07 | JYH1266 | BKK → CAN | May 7, 18:00 UTC | May 8, 09:04 UTC | 15h 4m |
| 2026-05-07 | JYH1265 | CAN → BKK | May 7, 14:10 UTC | May 7, 16:25 UTC | 2h 15m |
| 2026-05-03 | JYH1574 | SHE → NGB | May 3, 11:40 UTC | May 3, 11:50 UTC | 10m |
| 2026-04-30 | JYH1564 | SHE → JUH | Apr 30, 11:30 UTC | Apr 30, 11:40 UTC | 10m |
| 2026-04-25 | JYH1266 | BKK → CAN | Apr 25, 17:20 UTC | Apr 25, 17:45 UTC | 25m |
| 2026-04-25 | JYH1265 | CAN → BKK | Apr 25, 13:45 UTC | Apr 25, 15:50 UTC | 2h 5m |
| 2026-04-19 | JYH1697 | - | Apr 19, 06:30 UTC | Apr 19, 06:45 UTC | 15m |
| 2026-04-15 | JYH1025 | CAN → HAK | Apr 15, 22:40 UTC | Apr 15, 22:50 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-1719 page for operator, model, and routing details .