sensors Mode-S transponder
7812CB
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-1366 · BOEING 737-800
- Hex
- 7812CB
- Octal
- 36011313
- Decimal
- 7,869,131
- Country
- CN
- Tail
- B-1366
- Type
- B738
- Flights observed
- 32
- Distinct callsigns
- 18
- Country
- CN
- Last broadcast
- 20h ago
Last known position
Country allocation
The ICAO 24-bit address 7812CB 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 18 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| HBH8059 | Hebei Airlines | 5 | 2026-06-23 |
| HBH3301 | - | 4 | 2026-07-05 |
| HBH8025 | - | 3 | 2026-07-17 |
| HBH8070 | Hebei Airlines | 2 | 2026-05-20 |
| HBH3287 | - | 2 | 2026-07-04 |
| HBH3268 | - | 2 | 2026-06-13 |
| HBH8032 | Hebei Airlines | 1 | 2026-07-10 |
| HBH8026 | - | 1 | 2026-07-11 |
| HBH8014 | - | 1 | 2026-04-22 |
| HBH8001 | - | 1 | 2026-06-24 |
| HBH3656 | - | 1 | 2026-07-05 |
| HBH3655 | - | 1 | 2026-07-05 |
| HBH3611 | Hebei Airlines | 1 | 2026-05-30 |
| HBH3302 | Hebei Airlines | 1 | 2026-06-08 |
| HBH3294 | Hebei Airlines | 1 | 2026-05-07 |
| HBH3293 | Hebei Airlines | 1 | 2026-05-07 |
| HBH3267 | Hebei Airlines | 1 | 2026-06-06 |
| HBH3203 | Hebei Airlines | 1 | 2026-04-18 |
Recent flights last 32
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | HBH8025 | - | Jul 17, 23:20 UTC | Jul 17, 23:35 UTC | 15m |
| 2026-07-14 | - | - | Jul 14, 10:25 UTC | Jul 14, 12:40 UTC | 2h 15m |
| 2026-07-11 | HBH8026 | - | Jul 11, 03:20 UTC | Jul 11, 03:30 UTC | 10m |
| 2026-07-10 | HBH8025 | - | Jul 10, 23:40 UTC | Jul 10, 23:50 UTC | 10m |
| 2026-07-10 | HBH8032 | XIY → PKX | Jul 10, 13:25 UTC | Jul 10, 13:40 UTC | 15m |
| 2026-07-05 | HBH3656 | - | Jul 5, 16:10 UTC | Jul 5, 16:20 UTC | 10m |
| 2026-07-05 | HBH3655 | - | Jul 5, 14:30 UTC | Jul 5, 14:50 UTC | 20m |
| 2026-07-05 | HBH3301 | - | Jul 5, 01:35 UTC | Jul 5, 01:55 UTC | 20m |
| 2026-07-04 | HBH3287 | - | Jul 4, 01:55 UTC | Jul 4, 02:15 UTC | 20m |
| 2026-07-01 | HBH3301 | - | Jul 1, 01:30 UTC | Jul 1, 01:45 UTC | 15m |
| 2026-06-29 | HBH3301 | - | Jun 29, 01:44 UTC | Jun 29, 01:55 UTC | 10m |
| 2026-06-24 | HBH8001 | - | Jun 24, 08:30 UTC | Jun 24, 08:49 UTC | 20m |
| 2026-06-23 | HBH8059 | PKX → HLD | Jun 23, 01:25 UTC | Jun 23, 01:45 UTC | 20m |
| 2026-06-22 | HBH8059 | PKX → HLD | Jun 22, 01:29 UTC | Jun 22, 01:44 UTC | 15m |
| 2026-06-15 | - | - | Jun 15, 12:30 UTC | Jun 15, 12:39 UTC | 10m |
| 2026-06-13 | HBH3268 | - | Jun 13, 04:15 UTC | Jun 13, 04:25 UTC | 10m |
| 2026-06-08 | HBH3302 | SYX → SJW | Jun 8, 02:35 UTC | Jun 8, 06:35 UTC | 4h 0m |
| 2026-06-06 | HBH3268 | SZX → SJW | Jun 6, 07:05 UTC | Jun 6, 07:15 UTC | 10m |
| 2026-06-06 | HBH3267 | SJW → SZX | Jun 6, 03:20 UTC | Jun 6, 03:40 UTC | 20m |
| 2026-06-02 | HBH3301 | SJW → SYX | Jun 2, 03:10 UTC | Jun 2, 05:55 UTC | 2h 45m |
| 2026-05-30 | HBH3611 | HGH → SYX | May 30, 09:30 UTC | May 30, 13:05 UTC | 3h 35m |
| 2026-05-26 | HBH8059 | PKX → HLD | May 26, 01:30 UTC | May 26, 01:44 UTC | 15m |
| 2026-05-21 | HBH8059 | PKX → HLD | May 21, 01:25 UTC | May 21, 01:40 UTC | 15m |
| 2026-05-20 | HBH8070 | JIC → PKX | May 20, 05:05 UTC | May 20, 05:20 UTC | 15m |
| 2026-05-19 | HBH8059 | PKX → HLD | May 19, 01:30 UTC | May 19, 01:40 UTC | 10m |
| 2026-05-18 | HBH8025 | PKX → NZL | May 18, 00:45 UTC | May 18, 00:55 UTC | 10m |
| 2026-05-16 | HBH3287 | SJW → HAK | May 16, 02:50 UTC | May 16, 03:05 UTC | 15m |
| 2026-05-07 | HBH3294 | SJW → HGH | May 7, 06:05 UTC | May 7, 06:15 UTC | 10m |
| 2026-05-07 | HBH3293 | HGH → SJW | May 7, 04:20 UTC | May 7, 04:35 UTC | 15m |
| 2026-04-22 | HBH8014 | - | Apr 22, 03:55 UTC | Apr 22, 04:10 UTC | 15m |
| 2026-04-19 | HBH8070 | JIC → PKX | Apr 19, 05:40 UTC | Apr 19, 05:55 UTC | 15m |
| 2026-04-18 | HBH3203 | SJW → CAN | Apr 18, 02:40 UTC | Apr 18, 02: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-1366 page for operator, model, and routing details .