sensors Mode-S transponder
781E8C
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-222P · BOEING 737-800
- Hex
- 781E8C
- Octal
- 36017214
- Decimal
- 7,872,140
- Country
- CN
- Tail
- B-222P
- Type
- B738
- Flights observed
- 97
- Distinct callsigns
- 9
- Country
- CN
- Last broadcast
- 25d ago
Last known position
Country allocation
The ICAO 24-bit address 781E8C 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 9 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-19 | HLF9864 | TAO → ONT | Jun 19, 09:30 UTC | Jun 19, 09:40 UTC | 10m |
| 2026-06-19 | HLF9863 | - | Jun 19, 07:45 UTC | Jun 19, 08:04 UTC | 20m |
| 2026-06-17 | HLF9864 | TAO → ONT | Jun 17, 22:10 UTC | Jun 17, 22:20 UTC | 10m |
| 2026-06-17 | HLF9863 | - | Jun 17, 20:10 UTC | Jun 17, 20:20 UTC | 10m |
| 2026-06-16 | HLF9864 | TAO → ONT | Jun 16, 22:15 UTC | Jun 16, 22:25 UTC | 10m |
| 2026-06-16 | HLF9863 | - | Jun 16, 19:50 UTC | Jun 16, 20:05 UTC | 15m |
| 2026-06-16 | HLF9864 | TAO → ONT | Jun 16, 11:05 UTC | Jun 16, 11:15 UTC | 10m |
| 2026-06-16 | HLF9863 | - | Jun 16, 05:30 UTC | Jun 16, 05:40 UTC | 10m |
| 2026-06-14 | HLF9864 | TAO → ONT | Jun 14, 21:55 UTC | Jun 14, 22:05 UTC | 10m |
| 2026-06-14 | HLF9863 | - | Jun 14, 19:25 UTC | Jun 14, 19:40 UTC | 15m |
| 2026-06-13 | HLF9864 | TAO → ONT | Jun 13, 21:50 UTC | Jun 13, 22:00 UTC | 10m |
| 2026-06-13 | HLF9863 | - | Jun 13, 20:00 UTC | Jun 13, 20:10 UTC | 10m |
| 2026-06-12 | HLF9864 | TAO → ONT | Jun 12, 22:00 UTC | Jun 12, 22:10 UTC | 10m |
| 2026-06-12 | HLF9863 | - | Jun 12, 19:40 UTC | Jun 12, 20:05 UTC | 25m |
| 2026-06-11 | HLF9864 | TAO → ONT | Jun 11, 21:55 UTC | Jun 11, 22:05 UTC | 10m |
| 2026-06-11 | HLF9863 | - | Jun 11, 19:40 UTC | Jun 11, 20:05 UTC | 25m |
| 2026-06-10 | HLF9864 | TAO → ONT | Jun 10, 21:50 UTC | Jun 10, 22:05 UTC | 15m |
| 2026-06-10 | HLF9863 | - | Jun 10, 20:00 UTC | Jun 10, 20:10 UTC | 10m |
| 2026-06-09 | HLF9863 | - | Jun 9, 20:15 UTC | Jun 9, 20:50 UTC | 35m |
| 2026-06-08 | HLF9863 | - | Jun 8, 20:10 UTC | Jun 8, 20:25 UTC | 15m |
| 2026-06-07 | HLF9864 | TAO → ONT | Jun 7, 21:50 UTC | Jun 7, 22:00 UTC | 10m |
| 2026-06-06 | HLF9864 | TAO → ONT | Jun 6, 22:10 UTC | Jun 6, 22:20 UTC | 10m |
| 2026-06-06 | HLF9863 | - | Jun 6, 19:40 UTC | Jun 6, 20:00 UTC | 20m |
| 2026-06-05 | HLF9864 | TAO → ONT | Jun 5, 22:00 UTC | Jun 5, 22:10 UTC | 10m |
| 2026-06-05 | HLF9863 | - | Jun 5, 19:45 UTC | Jun 5, 20:05 UTC | 20m |
| 2026-06-04 | HLF9864 | TAO → ONT | Jun 4, 22:00 UTC | Jun 4, 22:10 UTC | 10m |
| 2026-06-04 | HLF9863 | - | Jun 4, 19:40 UTC | Jun 4, 20:05 UTC | 25m |
| 2026-06-03 | HLF9864 | TAO → ONT | Jun 3, 22:20 UTC | Jun 3, 22:30 UTC | 10m |
| 2026-06-03 | HLF9863 | - | Jun 3, 20:20 UTC | Jun 3, 20:45 UTC | 25m |
| 2026-06-02 | HLF9864 | TAO → ONT | Jun 2, 22:05 UTC | Jun 2, 22:15 UTC | 10m |
| 2026-06-02 | HLF9863 | - | Jun 2, 19:15 UTC | Jun 2, 20:25 UTC | 1h 10m |
| 2026-06-01 | HLF9864 | TAO → ONT | Jun 1, 21:55 UTC | Jun 1, 22:05 UTC | 10m |
| 2026-06-01 | HLF9863 | - | Jun 1, 20:00 UTC | Jun 1, 20:20 UTC | 20m |
| 2026-05-31 | HLF9864 | TAO → ONT | May 31, 22:00 UTC | May 31, 22:10 UTC | 10m |
| 2026-05-31 | HLF9863 | - | May 31, 19:15 UTC | May 31, 19:50 UTC | 35m |
| 2026-05-31 | HLF9863 | - | May 31, 00:10 UTC | May 31, 00:40 UTC | 30m |
| 2026-05-30 | HLF9863 | - | May 30, 19:25 UTC | May 30, 19:55 UTC | 30m |
| 2026-05-29 | HLF9864 | TAO → ONT | May 29, 21:55 UTC | May 29, 22:05 UTC | 10m |
| 2026-05-29 | HLF9863 | - | May 29, 19:40 UTC | May 29, 20:00 UTC | 20m |
| 2026-05-27 | HLF9864 | TAO → ONT | May 27, 21:45 UTC | May 27, 21:55 UTC | 10m |
| 2026-05-27 | HLF9863 | - | May 27, 19:35 UTC | May 27, 20:00 UTC | 25m |
| 2026-05-26 | HLF9864 | TAO → ONT | May 26, 21:44 UTC | May 26, 21:55 UTC | 10m |
| 2026-05-26 | HLF9863 | - | May 26, 19:05 UTC | May 26, 20:20 UTC | 1h 15m |
| 2026-05-25 | HLF9864 | TAO → ONT | May 25, 21:54 UTC | May 25, 22:05 UTC | 10m |
| 2026-05-25 | HLF9863 | - | May 25, 19:59 UTC | May 25, 20:24 UTC | 25m |
| 2026-05-21 | HLF8864 | - | May 21, 19:30 UTC | May 21, 21:10 UTC | 1h 40m |
| 2026-05-21 | HLF8863 | - | May 21, 16:10 UTC | May 21, 17:50 UTC | 1h 40m |
| 2026-05-20 | HLF8863 | - | May 20, 21:05 UTC | May 21, 17:50 UTC | 20h 45m |
| 2026-05-20 | HLF8863 | - | May 20, 19:35 UTC | May 21, 17:50 UTC | 22h 15m |
| 2026-05-20 | HLF8863 | - | May 20, 16:05 UTC | May 20, 17:50 UTC | 1h 45m |
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-222P page for operator, model, and routing details .