sensors Mode-S transponder
78133F
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-1233 · BOEING 737-800
- Hex
- 78133F
- Octal
- 36011477
- Decimal
- 7,869,247
- Country
- CN
- Tail
- B-1233
- Type
- B738
- Flights observed
- 45
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 20h ago
Last known position
Country allocation
The ICAO 24-bit address 78133F 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 |
|---|---|---|---|
| JYH1266 | - | 8 | 2026-07-02 |
| JYH1697 | - | 6 | 2026-06-29 |
| JYH1265 | - | 6 | 2026-07-02 |
| JYH1574 | 9 Air | 5 | 2026-06-10 |
| JYH1580 | - | 3 | 2026-07-12 |
| JYH1114 | - | 2 | 2026-07-05 |
| JYH1717 | - | 1 | 2026-06-23 |
| JYH1625 | - | 1 | 2026-07-04 |
| JYH1572 | - | 1 | 2026-07-13 |
| JYH1564 | - | 1 | 2026-07-07 |
| JYH1563 | - | 1 | 2026-07-09 |
| JYH1343 | - | 1 | 2026-04-16 |
| JYH1278 | 9 Air | 1 | 2026-06-14 |
| JYH1233 | 9 Air | 1 | 2026-04-26 |
| JYH1111 | - | 1 | 2026-06-30 |
| JYH1072 | 9 Air | 1 | 2026-05-23 |
| JYH1071 | 9 Air | 1 | 2026-05-14 |
| JYH1041 | - | 1 | 2026-07-03 |
| JYH1025 | - | 1 | 2026-06-24 |
| JYH1024 | 9 Air | 1 | 2026-06-13 |
Recent flights last 45
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | JYH1572 | - | Jul 13, 06:05 UTC | Jul 13, 10:35 UTC | 4h 30m |
| 2026-07-12 | JYH1580 | - | Jul 12, 11:25 UTC | Jul 13, 06:50 UTC | 19h 25m |
| 2026-07-12 | JYH1580 | - | Jul 12, 06:25 UTC | Jul 12, 11:45 UTC | 5h 20m |
| 2026-07-10 | JYH1580 | - | Jul 10, 12:00 UTC | Jul 10, 12:40 UTC | 40m |
| 2026-07-09 | JYH1563 | - | Jul 9, 03:35 UTC | Jul 9, 03:50 UTC | 15m |
| 2026-07-07 | JYH1564 | - | Jul 7, 13:10 UTC | Jul 7, 13:20 UTC | 10m |
| 2026-07-05 | JYH1114 | - | Jul 5, 03:55 UTC | Jul 5, 04:05 UTC | 10m |
| 2026-07-04 | JYH1625 | - | Jul 4, 03:05 UTC | Jul 4, 23:05 UTC | 20h 0m |
| 2026-07-03 | JYH1041 | - | Jul 3, 23:40 UTC | Jul 4, 00:35 UTC | 55m |
| 2026-07-02 | JYH1266 | - | Jul 2, 17:30 UTC | Jul 2, 17:50 UTC | 20m |
| 2026-07-02 | JYH1265 | - | Jul 2, 13:15 UTC | Jul 2, 15:25 UTC | 2h 10m |
| 2026-06-30 | JYH1111 | - | Jun 30, 13:55 UTC | Jun 30, 14:05 UTC | 10m |
| 2026-06-29 | JYH1697 | - | Jun 29, 06:09 UTC | Jun 29, 08:44 UTC | 2h 35m |
| 2026-06-28 | JYH1697 | - | Jun 28, 06:15 UTC | Jun 28, 06:24 UTC | 10m |
| 2026-06-26 | JYH1697 | - | Jun 26, 13:34 UTC | Jun 27, 06:30 UTC | 16h 55m |
| 2026-06-26 | JYH1697 | - | Jun 26, 06:09 UTC | Jun 26, 13:34 UTC | 7h 25m |
| 2026-06-25 | JYH1697 | - | Jun 25, 01:50 UTC | Jun 25, 06:30 UTC | 4h 40m |
| 2026-06-24 | JYH1025 | - | Jun 24, 23:04 UTC | Jun 24, 23:14 UTC | 10m |
| 2026-06-23 | JYH1717 | - | Jun 23, 22:44 UTC | Jun 23, 22:55 UTC | 10m |
| 2026-06-23 | JYH1266 | - | Jun 23, 17:34 UTC | Jun 23, 19:10 UTC | 1h 35m |
| 2026-06-23 | JYH1265 | - | Jun 23, 14:35 UTC | Jun 23, 16:20 UTC | 1h 45m |
| 2026-06-14 | JYH1278 | VTE → CAN | Jun 14, 14:50 UTC | Jun 14, 18:20 UTC | 3h 30m |
| 2026-06-13 | JYH1024 | HAK → CAN | Jun 13, 05:15 UTC | Jun 13, 05:35 UTC | 20m |
| 2026-06-11 | JYH1266 | BKK → CAN | Jun 11, 17:20 UTC | Jun 11, 18:55 UTC | 1h 35m |
| 2026-06-11 | JYH1265 | CAN → BKK | Jun 11, 13:30 UTC | Jun 11, 15:45 UTC | 2h 15m |
| 2026-06-10 | JYH1574 | SHE → NGB | Jun 10, 12:30 UTC | Jun 10, 12:40 UTC | 10m |
| 2026-05-29 | JYH1574 | SHE → NGB | May 29, 11:55 UTC | May 29, 12:05 UTC | 10m |
| 2026-05-27 | JYH1574 | SHE → NGB | May 27, 12:10 UTC | May 27, 12:20 UTC | 10m |
| 2026-05-23 | JYH1266 | BKK → CAN | May 23, 18:50 UTC | May 23, 19:25 UTC | 35m |
| 2026-05-23 | JYH1265 | CAN → BKK | May 23, 16:50 UTC | May 23, 17:30 UTC | 40m |
| 2026-05-23 | JYH1072 | HGH → CAN | May 23, 12:55 UTC | May 23, 13:05 UTC | 10m |
| 2026-05-20 | JYH1574 | SHE → NGB | May 20, 11:40 UTC | May 20, 11:50 UTC | 10m |
| 2026-05-15 | JYH1266 | BKK → CAN | May 15, 17:35 UTC | May 15, 18:15 UTC | 40m |
| 2026-05-15 | JYH1265 | CAN → BKK | May 15, 15:05 UTC | May 15, 15:40 UTC | 35m |
| 2026-05-14 | JYH1071 | CAN → HGH | May 14, 05:10 UTC | May 14, 05:20 UTC | 10m |
| 2026-05-08 | JYH1574 | SHE → NGB | May 8, 11:40 UTC | May 8, 11:55 UTC | 15m |
| 2026-05-05 | JYH1266 | BKK → CAN | May 5, 17:50 UTC | May 5, 18:15 UTC | 25m |
| 2026-05-05 | JYH1265 | CAN → BKK | May 5, 15:20 UTC | May 5, 15:50 UTC | 30m |
| 2026-05-02 | JYH1266 | BKK → CAN | May 2, 17:30 UTC | May 2, 17:55 UTC | 25m |
| 2026-05-02 | JYH1266 | BKK → CAN | May 2, 15:15 UTC | May 2, 16:05 UTC | 50m |
| 2026-04-30 | JYH1697 | - | Apr 30, 06:25 UTC | Apr 30, 06:35 UTC | 10m |
| 2026-04-26 | JYH1233 | WUX → VTE | Apr 26, 04:55 UTC | Apr 26, 10:00 UTC | 5h 5m |
| 2026-04-22 | JYH1021 | CAN → TAO | Apr 22, 10:25 UTC | Apr 22, 10:35 UTC | 10m |
| 2026-04-16 | JYH1343 | - | Apr 16, 06:05 UTC | Apr 16, 06:15 UTC | 10m |
| 2026-04-13 | JYH1114 | SYX → CAN | Apr 13, 02:40 UTC | Apr 13, 02:55 UTC | 15m |
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-1233 page for operator, model, and routing details .