sensors Mode-S transponder
78138C
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-1258 · BOEING 737-800
- Hex
- 78138C
- Octal
- 36011614
- Decimal
- 7,869,324
- Country
- CN
- Tail
- B-1258
- Type
- B738
- Flights observed
- 41
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 9d ago
Last known position
Country allocation
The ICAO 24-bit address 78138C 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 |
|---|---|---|---|
| HBH3308 | - | 11 | 2026-07-25 |
| HBH8016 | - | 2 | 2026-07-03 |
| HBH8014 | - | 2 | 2026-07-09 |
| HBH8002 | Hebei Airlines | 2 | 2026-07-11 |
| HBH3611 | Hebei Airlines | 2 | 2026-06-02 |
| HBH3602 | - | 2 | 2026-07-12 |
| HBH3601 | - | 2 | 2026-07-12 |
| HBH3294 | - | 2 | 2026-06-25 |
| HBH3293 | Hebei Airlines | 2 | 2026-06-25 |
| HBH3268 | Hebei Airlines | 2 | 2026-06-09 |
| HBH8070 | Hebei Airlines | 1 | 2026-05-27 |
| HBH8063 | - | 1 | 2026-07-08 |
| HBH8061 | Hebei Airlines | 1 | 2026-05-17 |
| HBH8059 | Hebei Airlines | 1 | 2026-05-18 |
| HBH8022 | Hebei Airlines | 1 | 2026-05-03 |
| HBH8007 | - | 1 | 2026-07-08 |
| HBH3656 | Hebei Airlines | 1 | 2026-04-24 |
| HBH3612 | - | 1 | 2026-06-02 |
| HBH3331 | Hebei Airlines | 1 | 2026-04-27 |
| HBH3303 | Hebei Airlines | 1 | 2026-05-06 |
Recent flights last 41
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-25 | HBH3308 | - | Jul 25, 13:50 UTC | Jul 25, 14:35 UTC | 45m |
| 2026-07-24 | HBH3308 | - | Jul 24, 09:35 UTC | Jul 24, 14:30 UTC | 4h 55m |
| 2026-07-23 | HBH3308 | - | Jul 23, 13:55 UTC | Jul 24, 09:40 UTC | 19h 45m |
| 2026-07-21 | HBH3308 | - | Jul 21, 10:10 UTC | Jul 21, 14:55 UTC | 4h 45m |
| 2026-07-20 | HBH3308 | - | Jul 20, 15:05 UTC | Jul 21, 14:55 UTC | 23h 50m |
| 2026-07-20 | HBH3308 | - | Jul 20, 14:30 UTC | Jul 21, 10:15 UTC | 19h 44m |
| 2026-07-19 | HBH3308 | - | Jul 19, 15:05 UTC | Jul 20, 15:00 UTC | 23h 55m |
| 2026-07-19 | HBH3308 | - | Jul 19, 14:45 UTC | Jul 19, 15:25 UTC | 40m |
| 2026-07-18 | HBH3308 | - | Jul 18, 15:05 UTC | Jul 19, 15:00 UTC | 23h 55m |
| 2026-07-18 | HBH3308 | - | Jul 18, 10:35 UTC | Jul 18, 15:45 UTC | 5h 10m |
| 2026-07-16 | HBH3308 | - | Jul 16, 13:54 UTC | Jul 16, 14:45 UTC | 50m |
| 2026-07-12 | HBH3602 | - | Jul 12, 15:40 UTC | Jul 12, 15:50 UTC | 10m |
| 2026-07-12 | HBH3601 | - | Jul 12, 11:30 UTC | Jul 12, 11:45 UTC | 15m |
| 2026-07-11 | HBH8002 | TFU → PKX | Jul 11, 14:10 UTC | Jul 11, 14:25 UTC | 15m |
| 2026-07-11 | HBH3287 | - | Jul 11, 01:50 UTC | Jul 11, 02:05 UTC | 15m |
| 2026-07-09 | HBH8014 | - | Jul 9, 12:40 UTC | Jul 9, 12:50 UTC | 10m |
| 2026-07-08 | HBH8007 | - | Jul 8, 09:55 UTC | Jul 8, 10:20 UTC | 25m |
| 2026-07-08 | HBH8063 | - | Jul 8, 00:05 UTC | Jul 8, 00:20 UTC | 15m |
| 2026-07-07 | HBH8002 | TFU → PKX | Jul 7, 14:10 UTC | Jul 7, 14:25 UTC | 15m |
| 2026-07-03 | HBH8016 | - | Jul 3, 14:50 UTC | Jul 3, 15:20 UTC | 30m |
| 2026-07-02 | HBH8016 | - | Jul 2, 11:00 UTC | Jul 2, 11:15 UTC | 15m |
| 2026-07-01 | HBH3602 | - | Jul 1, 04:25 UTC | Jul 1, 04:35 UTC | 10m |
| 2026-07-01 | HBH3601 | - | Jul 1, 00:10 UTC | Jul 1, 00:25 UTC | 15m |
| 2026-06-25 | HBH3294 | - | Jun 25, 06:20 UTC | Jun 25, 06:30 UTC | 10m |
| 2026-06-25 | HBH3293 | HGH → SJW | Jun 25, 04:45 UTC | Jun 25, 05:00 UTC | 15m |
| 2026-06-20 | HBH8014 | - | Jun 20, 03:54 UTC | Jun 20, 04:04 UTC | 10m |
| 2026-06-09 | HBH3268 | SZX → SJW | Jun 9, 04:25 UTC | Jun 9, 04:35 UTC | 10m |
| 2026-06-09 | HBH3267 | SJW → SZX | Jun 9, 02:35 UTC | Jun 9, 02:50 UTC | 15m |
| 2026-06-06 | HBH3294 | SJW → HGH | Jun 6, 09:24 UTC | Jun 6, 09:45 UTC | 20m |
| 2026-06-06 | HBH3293 | HGH → SJW | Jun 6, 07:40 UTC | Jun 6, 07:50 UTC | 10m |
| 2026-06-05 | HBH3268 | SZX → SJW | Jun 5, 04:10 UTC | Jun 5, 04:25 UTC | 15m |
| 2026-06-02 | HBH3612 | - | Jun 2, 13:10 UTC | Jun 2, 13:25 UTC | 15m |
| 2026-06-02 | HBH3611 | HGH → SYX | Jun 2, 09:15 UTC | Jun 2, 10:10 UTC | 55m |
| 2026-05-27 | HBH8070 | JIC → PKX | May 27, 05:24 UTC | May 27, 05:35 UTC | 10m |
| 2026-05-18 | HBH8059 | PKX → HLD | May 18, 01:30 UTC | May 18, 01:40 UTC | 10m |
| 2026-05-17 | HBH8061 | PKX → CSX | May 17, 09:10 UTC | May 17, 09:20 UTC | 10m |
| 2026-05-06 | HBH3303 | SJW → KHN | May 6, 03:30 UTC | May 6, 03:55 UTC | 25m |
| 2026-05-03 | HBH8022 | ZYI → PKX | May 3, 06:15 UTC | May 3, 06:25 UTC | 10m |
| 2026-04-30 | HBH3611 | HGH → SYX | Apr 30, 03:40 UTC | Apr 30, 07:20 UTC | 3h 40m |
| 2026-04-27 | HBH3331 | SJW → SYX | Apr 27, 10:00 UTC | Apr 27, 10:20 UTC | 20m |
| 2026-04-24 | HBH3656 | SZX → SJW | Apr 24, 14:45 UTC | Apr 24, 14:55 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-1258 page for operator, model, and routing details .