sensors Mode-S transponder
780630
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-2079 · BOEING 777-200LR
- Hex
- 780630
- Octal
- 36003060
- Decimal
- 7,865,904
- Country
- CN
- Tail
- B-2079
- Type
- B77L
- Flights observed
- 191
- Distinct callsigns
- 8
- Country
- CN
- Last broadcast
- 4h ago
Last known position
Country allocation
The ICAO 24-bit address 780630 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 8 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | HLF9815 | - | Jul 13, 22:35 UTC | Jul 13, 23:15 UTC | 40m |
| 2026-07-12 | HLF9816 | - | Jul 12, 13:15 UTC | Jul 12, 19:40 UTC | 6h 25m |
| 2026-07-11 | HLF9815 | - | Jul 11, 14:30 UTC | Jul 12, 09:15 UTC | 18h 45m |
| 2026-07-11 | HLF9818 | - | Jul 11, 12:30 UTC | Jul 12, 09:15 UTC | 20h 45m |
| 2026-07-11 | HLF9818 | - | Jul 11, 10:05 UTC | Jul 12, 09:15 UTC | 23h 10m |
| 2026-07-11 | HLF9818 | - | Jul 11, 00:15 UTC | Jul 11, 16:20 UTC | 16h 5m |
| 2026-07-09 | HLF9816 | - | Jul 9, 14:05 UTC | Jul 9, 20:40 UTC | 6h 35m |
| 2026-07-08 | HLF9815 | - | Jul 8, 15:05 UTC | Jul 9, 10:00 UTC | 18h 55m |
| 2026-07-08 | HLF9818 | - | Jul 8, 13:05 UTC | Jul 9, 10:00 UTC | 20h 55m |
| 2026-07-08 | HLF9818 | - | Jul 8, 10:45 UTC | Jul 9, 10:00 UTC | 23h 15m |
| 2026-07-08 | HLF9818 | - | Jul 8, 04:05 UTC | Jul 9, 04:00 UTC | 23h 55m |
| 2026-07-08 | HLF9818 | - | Jul 8, 01:15 UTC | Jul 8, 17:05 UTC | 15h 50m |
| 2026-07-07 | HLF9817 | - | Jul 7, 14:40 UTC | Jul 8, 13:50 UTC | 23h 10m |
| 2026-07-07 | HLF9817 | - | Jul 7, 10:05 UTC | Jul 8, 04:25 UTC | 18h 20m |
| 2026-07-07 | HLF8834 | - | Jul 7, 08:50 UTC | Jul 8, 04:25 UTC | 19h 35m |
| 2026-07-06 | HLF8833 | - | Jul 6, 22:25 UTC | Jul 7, 04:55 UTC | 6h 30m |
| 2026-07-05 | HLF8834 | - | Jul 5, 13:15 UTC | Jul 5, 19:40 UTC | 6h 25m |
| 2026-07-04 | HLF8833 | - | Jul 4, 15:15 UTC | Jul 5, 09:00 UTC | 17h 45m |
| 2026-07-04 | HLF8833 | - | Jul 4, 10:50 UTC | Jul 5, 09:00 UTC | 22h 10m |
| 2026-07-04 | HLF9818 | - | Jul 4, 04:30 UTC | Jul 5, 03:10 UTC | 22h 40m |
| 2026-07-04 | HLF9818 | - | Jul 4, 01:40 UTC | Jul 4, 17:00 UTC | 15h 20m |
| 2026-07-02 | HLF8834 | - | Jul 2, 14:20 UTC | Jul 2, 20:20 UTC | 6h 0m |
| 2026-07-01 | HLF8833 | - | Jul 1, 16:05 UTC | Jul 2, 10:55 UTC | 18h 50m |
| 2026-07-01 | HLF8833 | - | Jul 1, 14:05 UTC | Jul 2, 10:55 UTC | 20h 50m |
| 2026-07-01 | HLF8833 | - | Jul 1, 13:25 UTC | Jul 2, 10:55 UTC | 21h 30m |
| 2026-07-01 | HLF9818 | - | Jul 1, 11:00 UTC | Jul 2, 10:00 UTC | 23h 0m |
| 2026-07-01 | HLF9818 | - | Jul 1, 00:50 UTC | Jul 1, 17:10 UTC | 16h 20m |
| 2026-06-30 | HLF9817 | - | Jun 30, 14:45 UTC | Jul 1, 14:00 UTC | 23h 15m |
| 2026-06-30 | HLF9817 | - | Jun 30, 10:05 UTC | Jul 1, 04:05 UTC | 18h 0m |
| 2026-06-30 | HLF8834 | - | Jun 30, 08:55 UTC | Jul 1, 04:05 UTC | 19h 10m |
| 2026-06-29 | HLF8833 | - | Jun 29, 22:19 UTC | Jun 30, 05:00 UTC | 6h 41m |
| 2026-06-27 | HLF8834 | - | Jun 27, 17:20 UTC | Jun 27, 23:39 UTC | 6h 20m |
| 2026-06-27 | HLF8833 | - | Jun 27, 07:34 UTC | Jun 27, 08:14 UTC | 40m |
| 2026-06-25 | HLF8834 | - | Jun 25, 17:20 UTC | Jun 25, 23:30 UTC | 6h 10m |
| 2026-06-25 | HLF8833 | - | Jun 25, 07:39 UTC | Jun 25, 14:14 UTC | 6h 35m |
| 2026-06-24 | HLF8833 | - | Jun 24, 19:29 UTC | Jun 25, 14:14 UTC | 18h 45m |
| 2026-06-24 | HLF8833 | - | Jun 24, 16:05 UTC | Jun 25, 14:14 UTC | 22h 10m |
| 2026-06-24 | HLF9806 | - | Jun 24, 14:24 UTC | Jun 25, 13:59 UTC | 23h 35m |
| 2026-06-24 | HLF9805 | - | Jun 24, 04:50 UTC | Jun 24, 10:59 UTC | 6h 10m |
| 2026-06-23 | HLF9805 | - | Jun 23, 10:04 UTC | Jun 24, 09:59 UTC | 23h 55m |
| 2026-06-23 | HLF8834 | - | Jun 23, 08:59 UTC | Jun 24, 05:05 UTC | 20h 5m |
| 2026-06-22 | HLF9806 | - | Jun 22, 06:05 UTC | Jun 22, 23:05 UTC | 17h 0m |
| 2026-06-21 | HLF9805 | - | Jun 21, 23:44 UTC | Jun 22, 02:45 UTC | 3h 0m |
| 2026-06-21 | HLF8834 | - | Jun 21, 00:04 UTC | Jun 21, 23:59 UTC | 23h 55m |
| 2026-06-20 | HLF8834 | - | Jun 20, 18:19 UTC | Jun 21, 00:25 UTC | 6h 5m |
| 2026-06-20 | HLF8833 | - | Jun 20, 06:54 UTC | Jun 20, 13:29 UTC | 6h 35m |
| 2026-06-18 | HLF8834 | - | Jun 18, 18:20 UTC | Jun 19, 00:29 UTC | 6h 9m |
| 2026-06-18 | HLF8833 | - | Jun 18, 07:45 UTC | Jun 18, 14:20 UTC | 6h 35m |
| 2026-06-17 | HLF8833 | - | Jun 17, 19:55 UTC | Jun 18, 14:20 UTC | 18h 25m |
| 2026-06-17 | HLF8833 | - | Jun 17, 16:05 UTC | Jun 18, 14:20 UTC | 22h 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-2079 page for operator, model, and routing details .