sensors Mode-S transponder
781496
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-1171 · BOEING 737-800
- Hex
- 781496
- Octal
- 36012226
- Decimal
- 7,869,590
- Country
- CN
- Tail
- B-1171
- Type
- B738
- Flights observed
- 39
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 14h ago
Last known position
Country allocation
The ICAO 24-bit address 781496 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 |
|---|---|---|---|
| HBH3268 | - | 4 | 2026-06-12 |
| HBH8059 | Hebei Airlines | 3 | 2026-06-25 |
| HBH8014 | - | 3 | 2026-06-27 |
| HBH3601 | - | 3 | 2026-07-18 |
| HBH3301 | - | 3 | 2026-07-22 |
| HBH8025 | - | 2 | 2026-07-05 |
| HBH3602 | - | 2 | 2026-07-03 |
| HBH3308 | - | 2 | 2026-07-13 |
| HBH3287 | Hebei Airlines | 2 | 2026-05-09 |
| HBH8070 | Hebei Airlines | 1 | 2026-06-10 |
| HBH8068 | - | 1 | 2026-07-06 |
| HBH8063 | - | 1 | 2026-07-04 |
| HBH8017 | Hebei Airlines | 1 | 2026-06-26 |
| HBH8013 | - | 1 | 2026-06-13 |
| HBH8002 | Hebei Airlines | 1 | 2026-06-12 |
| HBH3656 | - | 1 | 2026-07-17 |
| HBH3326 | Hebei Airlines | 1 | 2026-07-23 |
| HBH3325 | Hebei Airlines | 1 | 2026-07-22 |
| HBH330R | - | 1 | 2026-07-12 |
| HBH3300 | Hebei Airlines | 1 | 2026-07-19 |
Recent flights last 39
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-23 | HBH3326 | BAR → SJW | Jul 23, 04:25 UTC | Jul 23, 04:40 UTC | 15m |
| 2026-07-22 | HBH3325 | SJW → BAR | Jul 22, 23:50 UTC | Jul 23, 00:00 UTC | 10m |
| 2026-07-22 | HBH3301 | - | Jul 22, 01:40 UTC | Jul 23, 00:00 UTC | 22h 20m |
| 2026-07-19 | HBH3300 | HLD → SJW | Jul 19, 08:20 UTC | Jul 19, 08:35 UTC | 15m |
| 2026-07-19 | HBH3299 | - | Jul 19, 03:40 UTC | Jul 19, 03:55 UTC | 15m |
| 2026-07-18 | HBH3601 | - | Jul 18, 00:10 UTC | Jul 18, 00:29 UTC | 20m |
| 2026-07-17 | HBH3656 | - | Jul 17, 13:15 UTC | Jul 17, 13:25 UTC | 10m |
| 2026-07-14 | HBH3294 | - | Jul 14, 06:20 UTC | Jul 14, 06:30 UTC | 10m |
| 2026-07-13 | HBH3308 | - | Jul 13, 14:00 UTC | Jul 14, 04:55 UTC | 14h 55m |
| 2026-07-12 | HBH330R | - | Jul 12, 06:05 UTC | Jul 12, 06:55 UTC | 50m |
| 2026-07-10 | HBH3308 | - | Jul 10, 13:55 UTC | Jul 10, 14:40 UTC | 45m |
| 2026-07-06 | HBH8068 | - | Jul 6, 14:00 UTC | Jul 6, 14:10 UTC | 10m |
| 2026-07-05 | HBH8025 | - | Jul 5, 23:25 UTC | Jul 5, 23:35 UTC | 10m |
| 2026-07-04 | HBH8063 | - | Jul 4, 00:10 UTC | Jul 4, 00:25 UTC | 15m |
| 2026-07-03 | HBH3602 | - | Jul 3, 05:15 UTC | Jul 3, 05:30 UTC | 15m |
| 2026-07-03 | HBH3601 | - | Jul 3, 00:30 UTC | Jul 3, 00:45 UTC | 15m |
| 2026-07-02 | HBH3301 | - | Jul 2, 01:55 UTC | Jul 3, 00:45 UTC | 22h 50m |
| 2026-06-29 | HBH3602 | - | Jun 29, 05:04 UTC | Jun 29, 05:15 UTC | 10m |
| 2026-06-29 | HBH3601 | - | Jun 29, 00:10 UTC | Jun 29, 00:24 UTC | 15m |
| 2026-06-27 | HBH8014 | - | Jun 27, 04:19 UTC | Jun 27, 04:29 UTC | 10m |
| 2026-06-26 | HBH8017 | PKX → ZUH | Jun 26, 09:45 UTC | Jun 26, 09:59 UTC | 15m |
| 2026-06-25 | HBH8059 | PKX → HLD | Jun 25, 02:30 UTC | Jun 25, 02:45 UTC | 15m |
| 2026-06-24 | HBH8059 | PKX → HLD | Jun 24, 01:24 UTC | Jun 24, 01:39 UTC | 15m |
| 2026-06-13 | HBH8014 | - | Jun 13, 04:10 UTC | Jun 13, 04:20 UTC | 10m |
| 2026-06-13 | HBH8013 | - | Jun 13, 00:15 UTC | Jun 13, 00:25 UTC | 10m |
| 2026-06-12 | HBH8002 | TFU → PKX | Jun 12, 14:01 UTC | Jun 12, 14:15 UTC | 15m |
| 2026-06-12 | HBH3268 | - | Jun 12, 04:05 UTC | Jun 12, 04:15 UTC | 10m |
| 2026-06-10 | HBH8070 | JIC → PKX | Jun 10, 05:10 UTC | Jun 10, 05:20 UTC | 10m |
| 2026-06-08 | HBH8059 | PKX → HLD | Jun 8, 01:35 UTC | Jun 8, 01:50 UTC | 15m |
| 2026-06-06 | HBH8025 | PKX → NZL | Jun 6, 00:00 UTC | Jun 6, 00:10 UTC | 10m |
| 2026-06-05 | HBH8014 | - | Jun 5, 04:00 UTC | Jun 5, 04:15 UTC | 15m |
| 2026-06-01 | HBH3268 | SZX → SJW | Jun 1, 04:15 UTC | Jun 1, 04:30 UTC | 15m |
| 2026-05-28 | HBH3301 | SJW → SYX | May 28, 03:35 UTC | May 28, 04:20 UTC | 45m |
| 2026-05-09 | HBH3287 | SJW → HAK | May 9, 02:45 UTC | May 9, 03:00 UTC | 15m |
| 2026-05-04 | HBH3287 | SJW → HAK | May 4, 01:44 UTC | May 4, 02:00 UTC | 15m |
| 2026-05-02 | HBH3268 | SZX → SJW | May 2, 04:05 UTC | May 2, 04:15 UTC | 10m |
| 2026-04-28 | HBH3268 | SZX → SJW | Apr 28, 04:10 UTC | Apr 28, 04:25 UTC | 15m |
| 2026-04-24 | HBH3211 | HGH → SJW | Apr 24, 04:35 UTC | Apr 24, 05:05 UTC | 30m |
| 2026-04-21 | HBH3289 | SJW → HAK | Apr 21, 10:45 UTC | Apr 21, 10: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-1171 page for operator, model, and routing details .