sensors Mode-S transponder
78071B
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-2082 · BOEING 777-200LR
- Hex
- 78071B
- Octal
- 36003433
- Decimal
- 7,866,139
- Country
- CN
- Tail
- B-2082
- Type
- B77L
- Flights observed
- 181
- Distinct callsigns
- 6
- Country
- CN
- Last broadcast
- 12h ago
Last known position
Country allocation
The ICAO 24-bit address 78071B 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 6 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | HLF8832 | - | Jul 13, 14:55 UTC | Jul 13, 21:15 UTC | 6h 20m |
| 2026-07-12 | HLF9852 | - | Jul 12, 17:05 UTC | Jul 13, 11:55 UTC | 18h 50m |
| 2026-07-11 | HLF9858 | EMA → BRU | Jul 11, 19:25 UTC | Jul 12, 14:05 UTC | 18h 40m |
| 2026-07-11 | HLF9899 | - | Jul 11, 04:20 UTC | Jul 11, 14:05 UTC | 9h 45m |
| 2026-07-10 | HLF8832 | - | Jul 10, 10:10 UTC | Jul 10, 16:30 UTC | 6h 20m |
| 2026-07-10 | HLF9851 | - | Jul 10, 00:10 UTC | Jul 10, 06:30 UTC | 6h 20m |
| 2026-07-09 | HLF9851 | - | Jul 9, 08:50 UTC | Jul 10, 06:30 UTC | 21h 40m |
| 2026-07-09 | HLF9852 | - | Jul 9, 07:00 UTC | Jul 10, 06:30 UTC | 23h 30m |
| 2026-07-08 | HLF9851 | - | Jul 8, 04:55 UTC | Jul 8, 22:45 UTC | 17h 50m |
| 2026-07-08 | HLF9858 | - | Jul 8, 00:50 UTC | Jul 8, 22:45 UTC | 21h 55m |
| 2026-07-07 | HLF9858 | - | Jul 7, 22:50 UTC | Jul 8, 22:45 UTC | 23h 55m |
| 2026-07-07 | HLF9899 | - | Jul 7, 10:55 UTC | Jul 7, 20:40 UTC | 9h 45m |
| 2026-07-06 | HLF8832 | - | Jul 6, 14:50 UTC | Jul 6, 21:05 UTC | 6h 15m |
| 2026-07-05 | HLF9852 | - | Jul 5, 17:15 UTC | Jul 6, 12:45 UTC | 19h 30m |
| 2026-07-04 | HLF9858 | EMA → BRU | Jul 4, 19:20 UTC | Jul 5, 13:45 UTC | 18h 25m |
| 2026-07-04 | HLF9899 | - | Jul 4, 06:45 UTC | Jul 4, 16:50 UTC | 10h 5m |
| 2026-07-03 | HLF8832 | - | Jul 3, 11:20 UTC | Jul 3, 17:30 UTC | 6h 10m |
| 2026-07-02 | HLF9851 | - | Jul 2, 14:30 UTC | Jul 3, 07:00 UTC | 16h 30m |
| 2026-07-02 | HLF9851 | - | Jul 2, 10:50 UTC | Jul 3, 07:00 UTC | 20h 10m |
| 2026-07-02 | HLF9852 | - | Jul 2, 08:55 UTC | Jul 3, 07:00 UTC | 22h 5m |
| 2026-07-01 | HLF9851 | - | Jul 1, 04:55 UTC | Jul 2, 00:25 UTC | 19h 30m |
| 2026-07-01 | HLF9851 | - | Jul 1, 00:50 UTC | Jul 2, 00:25 UTC | 23h 35m |
| 2026-06-30 | HLF9858 | - | Jun 30, 22:40 UTC | Jul 1, 05:00 UTC | 6h 20m |
| 2026-06-30 | HLF9899 | - | Jun 30, 12:40 UTC | Jun 30, 13:20 UTC | 40m |
| 2026-06-30 | HLF9899 | - | Jun 30, 09:40 UTC | Jun 30, 09:50 UTC | 10m |
| 2026-06-29 | HLF8832 | - | Jun 29, 14:44 UTC | Jun 29, 21:09 UTC | 6h 25m |
| 2026-06-28 | HLF9852 | - | Jun 28, 17:10 UTC | Jun 29, 11:45 UTC | 18h 35m |
| 2026-06-27 | HLF9858 | EMA → BRU | Jun 27, 19:34 UTC | Jun 28, 14:09 UTC | 18h 35m |
| 2026-06-27 | HLF9899 | - | Jun 27, 05:35 UTC | Jun 27, 16:00 UTC | 10h 25m |
| 2026-06-26 | HLF8832 | - | Jun 26, 11:05 UTC | Jun 26, 17:15 UTC | 6h 10m |
| 2026-06-25 | HLF9851 | - | Jun 25, 23:49 UTC | Jun 26, 06:25 UTC | 6h 35m |
| 2026-06-25 | HLF9852 | - | Jun 25, 01:50 UTC | Jun 26, 00:15 UTC | 22h 25m |
| 2026-06-24 | HLF9852 | - | Jun 24, 20:09 UTC | Jun 25, 02:25 UTC | 6h 15m |
| 2026-06-23 | HLF9858 | - | Jun 23, 22:49 UTC | Jun 24, 18:15 UTC | 19h 25m |
| 2026-06-23 | HLF9858 | EMA → BRU | Jun 23, 22:25 UTC | Jun 24, 18:15 UTC | 19h 50m |
| 2026-06-23 | HLF9899 | - | Jun 23, 08:45 UTC | Jun 23, 18:45 UTC | 10h 0m |
| 2026-06-22 | HLF8832 | - | Jun 22, 14:45 UTC | Jun 22, 21:05 UTC | 6h 20m |
| 2026-06-21 | HLF9852 | - | Jun 21, 17:20 UTC | Jun 22, 11:19 UTC | 18h 0m |
| 2026-06-20 | HLF9851 | - | Jun 20, 19:09 UTC | Jun 21, 14:15 UTC | 19h 5m |
| 2026-06-20 | HLF9899 | - | Jun 20, 05:29 UTC | Jun 20, 15:34 UTC | 10h 5m |
| 2026-06-19 | HLF8832 | - | Jun 19, 11:49 UTC | Jun 19, 17:55 UTC | 6h 5m |
| 2026-06-19 | HLF9851 | - | Jun 19, 00:20 UTC | Jun 19, 07:04 UTC | 6h 45m |
| 2026-06-17 | HLF9852 | - | Jun 17, 20:15 UTC | Jun 17, 22:35 UTC | 2h 20m |
| 2026-06-16 | HLF9858 | EMA → BRU | Jun 16, 22:40 UTC | Jun 17, 16:45 UTC | 18h 5m |
| 2026-06-16 | HLF9899 | - | Jun 16, 13:00 UTC | Jun 16, 13:44 UTC | 45m |
| 2026-06-15 | HLF8832 | - | Jun 15, 14:40 UTC | Jun 15, 21:04 UTC | 6h 25m |
| 2026-06-14 | HLF9852 | - | Jun 14, 17:35 UTC | Jun 15, 05:20 UTC | 11h 45m |
| 2026-06-13 | HLF9858 | NRT → NRT | Jun 13, 19:15 UTC | Jun 14, 14:20 UTC | 19h 5m |
| 2026-06-13 | HLF9899 | - | Jun 13, 09:50 UTC | Jun 13, 10:30 UTC | 40m |
| 2026-06-13 | HLF9899 | - | Jun 13, 06:40 UTC | Jun 13, 06: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-2082 page for operator, model, and routing details .