sensors Mode-S transponder
781F0C
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-223J · BOEING 737-800
- Hex
- 781F0C
- Octal
- 36017414
- Decimal
- 7,872,268
- Country
- CN
- Tail
- B-223J
- Type
- B738
- Flights observed
- 57
- Distinct callsigns
- 5
- Country
- CN
- Last broadcast
- 4h ago
Last known position
Country allocation
The ICAO 24-bit address 781F0C 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 5 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | HLF8864 | - | May 29, 20:05 UTC | May 29, 21:50 UTC | 1h 45m |
| 2026-05-29 | HLF8863 | - | May 29, 16:00 UTC | May 29, 17:35 UTC | 1h 35m |
| 2026-05-27 | HLF8864 | - | May 27, 19:10 UTC | May 27, 20:55 UTC | 1h 45m |
| 2026-05-27 | HLF8863 | - | May 27, 15:45 UTC | May 27, 17:35 UTC | 1h 50m |
| 2026-05-25 | HLF8864 | - | May 25, 20:04 UTC | May 25, 21:49 UTC | 1h 45m |
| 2026-05-25 | HLF8863 | - | May 25, 16:00 UTC | May 25, 17:55 UTC | 1h 55m |
| 2026-05-22 | HLF8864 | - | May 22, 20:00 UTC | May 22, 21:40 UTC | 1h 40m |
| 2026-05-22 | HLF8863 | - | May 22, 16:00 UTC | May 22, 17:40 UTC | 1h 40m |
| 2026-05-21 | HLF8856 | - | May 21, 05:55 UTC | May 21, 06:20 UTC | 25m |
| 2026-05-21 | HLF8855 | - | May 21, 03:35 UTC | May 21, 04:20 UTC | 45m |
| 2026-05-20 | HLF8856 | DAC → DAC | May 20, 06:10 UTC | May 21, 04:20 UTC | 22h 10m |
| 2026-05-20 | HLF8855 | - | May 20, 03:50 UTC | May 20, 04:35 UTC | 45m |
| 2026-05-18 | HLF8864 | - | May 18, 19:20 UTC | May 18, 21:05 UTC | 1h 45m |
| 2026-05-18 | HLF8863 | - | May 18, 15:50 UTC | May 18, 17:35 UTC | 1h 45m |
| 2026-05-16 | HLF8856 | - | May 16, 07:20 UTC | May 16, 08:05 UTC | 45m |
| 2026-05-16 | HLF8855 | - | May 16, 03:45 UTC | May 16, 04:30 UTC | 45m |
| 2026-05-15 | HLF8855 | - | May 15, 06:00 UTC | May 16, 04:30 UTC | 22h 29m |
| 2026-05-15 | HLF8855 | - | May 15, 03:10 UTC | May 15, 04:20 UTC | 1h 10m |
| 2026-05-14 | HLF8855 | - | May 14, 06:00 UTC | May 15, 04:20 UTC | 22h 20m |
| 2026-05-14 | HLF8855 | - | May 14, 03:40 UTC | May 14, 04:25 UTC | 45m |
| 2026-05-11 | HLF8864 | - | May 11, 19:55 UTC | May 11, 21:45 UTC | 1h 50m |
| 2026-05-11 | HLF8863 | - | May 11, 16:00 UTC | May 11, 17:45 UTC | 1h 45m |
| 2026-05-09 | HLF8864 | - | May 9, 19:10 UTC | May 9, 20:49 UTC | 1h 40m |
| 2026-05-09 | HLF8863 | - | May 9, 15:55 UTC | May 9, 17:35 UTC | 1h 40m |
| 2026-05-08 | HLF8863 | - | May 8, 21:05 UTC | May 9, 17:35 UTC | 20h 30m |
| 2026-05-08 | HLF8863 | - | May 8, 19:20 UTC | May 9, 17:35 UTC | 22h 15m |
| 2026-05-08 | HLF8863 | - | May 8, 16:00 UTC | May 8, 17:45 UTC | 1h 45m |
| 2026-05-06 | HLF8864 | - | May 6, 20:10 UTC | May 6, 21:55 UTC | 1h 45m |
| 2026-05-06 | HLF8863 | - | May 6, 15:55 UTC | May 6, 17:40 UTC | 1h 44m |
| 2026-04-30 | HLF8864 | - | Apr 30, 19:15 UTC | Apr 30, 20:55 UTC | 1h 40m |
| 2026-04-30 | HLF8863 | - | Apr 30, 15:55 UTC | Apr 30, 17:40 UTC | 1h 45m |
| 2026-04-29 | HLF8863 | - | Apr 29, 21:05 UTC | Apr 30, 17:40 UTC | 20h 34m |
| 2026-04-29 | HLF8863 | - | Apr 29, 20:50 UTC | Apr 30, 17:40 UTC | 20h 49m |
| 2026-04-29 | HLF8863 | - | Apr 29, 16:10 UTC | Apr 29, 17:50 UTC | 1h 40m |
| 2026-04-27 | HLF8864 | - | Apr 27, 19:10 UTC | Apr 27, 20:55 UTC | 1h 45m |
| 2026-04-27 | HLF8863 | - | Apr 27, 16:00 UTC | Apr 27, 17:45 UTC | 1h 45m |
| 2026-04-24 | HLF8864 | - | Apr 24, 19:15 UTC | Apr 24, 21:00 UTC | 1h 45m |
| 2026-04-24 | HLF8863 | - | Apr 24, 05:55 UTC | Apr 24, 17:45 UTC | 11h 50m |
| 2026-04-24 | HLF8855 | - | Apr 24, 03:40 UTC | Apr 24, 04:00 UTC | 20m |
| 2026-04-22 | HLF8864 | - | Apr 22, 19:30 UTC | Apr 22, 21:15 UTC | 1h 45m |
| 2026-04-22 | HLF8863 | - | Apr 22, 05:50 UTC | Apr 22, 17:40 UTC | 11h 50m |
| 2026-04-22 | HLF8855 | - | Apr 22, 03:35 UTC | Apr 22, 04:55 UTC | 1h 20m |
| 2026-04-19 | HLF8869 | - | Apr 19, 07:05 UTC | Apr 19, 20:50 UTC | 13h 45m |
| 2026-04-19 | HLF8855 | - | Apr 19, 03:35 UTC | Apr 19, 03:55 UTC | 20m |
| 2026-04-17 | HLF8864 | - | Apr 17, 19:25 UTC | Apr 17, 21:05 UTC | 1h 40m |
| 2026-04-17 | HLF8863 | - | Apr 17, 17:25 UTC | Apr 17, 17:40 UTC | 15m |
| 2026-04-17 | HLF8863 | - | Apr 17, 16:00 UTC | Apr 17, 17:15 UTC | 1h 15m |
| 2026-04-16 | HLF8864 | - | Apr 16, 21:14 UTC | Apr 16, 23:00 UTC | 1h 45m |
| 2026-04-16 | HLF8863 | - | Apr 16, 17:15 UTC | Apr 16, 17:40 UTC | 25m |
| 2026-04-16 | HLF8863 | - | Apr 16, 15:55 UTC | Apr 16, 17:10 UTC | 1h 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-223J page for operator, model, and routing details .