sensors Mode-S transponder
7802DD
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-1328 · BOEING 737-800
- Hex
- 7802DD
- Octal
- 36001335
- Decimal
- 7,865,053
- Country
- CN
- Tail
- B-1328
- Type
- B738
- Flights observed
- 39
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- Jul 26, 14:40 UTC
Last known position
Country allocation
The ICAO 24-bit address 7802DD 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 |
|---|---|---|---|
| HBH3287 | - | 5 | 2026-07-20 |
| HBH8059 | Hebei Airlines | 4 | 2026-06-21 |
| HBH3308 | - | 4 | 2026-07-05 |
| HBH8070 | Hebei Airlines | 3 | 2026-07-26 |
| HBH8014 | - | 2 | 2026-06-25 |
| HBH3300 | - | 2 | 2026-07-15 |
| HBH3299 | - | 2 | 2026-07-15 |
| HBH3294 | - | 2 | 2026-06-30 |
| HBH3268 | - | 2 | 2026-06-29 |
| HBH8079 | Hebei Airlines | 1 | 2026-07-25 |
| HBH8036 | Hebei Airlines | 1 | 2026-06-03 |
| HBH8031 | Hebei Airlines | 1 | 2026-06-07 |
| HBH8030 | Hebei Airlines | 1 | 2026-07-24 |
| HBH8029 | Hebei Airlines | 1 | 2026-07-24 |
| HBH8025 | Hebei Airlines | 1 | 2026-04-29 |
| HBH8017 | Hebei Airlines | 1 | 2026-06-24 |
| HBH8008 | Hebei Airlines | 1 | 2026-06-04 |
| HBH8007 | Hebei Airlines | 1 | 2026-06-06 |
| HBH3601 | - | 1 | 2026-07-14 |
| HBH3293 | - | 1 | 2026-06-30 |
Recent flights last 39
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | HBH8070 | JIC → PKX | Jul 26, 14:25 UTC | Jul 26, 14:40 UTC | 15m |
| 2026-07-25 | HBH8079 | PKX → ZHA | Jul 25, 00:05 UTC | Jul 25, 00:40 UTC | 35m |
| 2026-07-24 | HBH8030 | KWL → PKX | Jul 24, 14:20 UTC | Jul 24, 14:45 UTC | 25m |
| 2026-07-24 | HBH8029 | PKX → KWL | Jul 24, 08:35 UTC | Jul 24, 09:00 UTC | 25m |
| 2026-07-20 | HBH3287 | - | Jul 20, 02:05 UTC | Jul 20, 02:20 UTC | 15m |
| 2026-07-18 | HBH3242 | - | Jul 18, 09:10 UTC | Jul 18, 09:20 UTC | 10m |
| 2026-07-15 | HBH3300 | - | Jul 15, 09:15 UTC | Jul 15, 09:25 UTC | 10m |
| 2026-07-15 | HBH3299 | - | Jul 15, 04:05 UTC | Jul 15, 04:15 UTC | 10m |
| 2026-07-14 | HBH3601 | - | Jul 14, 00:20 UTC | Jul 14, 00:30 UTC | 10m |
| 2026-07-13 | HBH3300 | - | Jul 13, 08:10 UTC | Jul 13, 08:20 UTC | 10m |
| 2026-07-13 | HBH3299 | - | Jul 13, 03:50 UTC | Jul 13, 04:05 UTC | 15m |
| 2026-07-11 | HBH3289 | - | Jul 11, 01:35 UTC | Jul 11, 11:30 UTC | 9h 55m |
| 2026-07-05 | HBH3308 | - | Jul 5, 15:45 UTC | Jul 6, 14:25 UTC | 22h 40m |
| 2026-07-03 | HBH3308 | - | Jul 3, 13:55 UTC | Jul 3, 14:05 UTC | 10m |
| 2026-07-02 | HBH3308 | - | Jul 2, 13:45 UTC | Jul 2, 14:20 UTC | 35m |
| 2026-07-01 | HBH3308 | - | Jul 1, 15:40 UTC | Jul 2, 14:20 UTC | 22h 40m |
| 2026-06-30 | HBH3294 | - | Jun 30, 12:20 UTC | Jun 30, 12:30 UTC | 10m |
| 2026-06-30 | HBH3293 | - | Jun 30, 10:40 UTC | Jun 30, 10:55 UTC | 15m |
| 2026-06-30 | HBH3287 | - | Jun 30, 01:50 UTC | Jun 30, 02:05 UTC | 15m |
| 2026-06-29 | HBH3268 | - | Jun 29, 04:14 UTC | Jun 29, 04:25 UTC | 10m |
| 2026-06-25 | HBH8014 | - | Jun 25, 04:10 UTC | Jun 25, 04:25 UTC | 15m |
| 2026-06-24 | HBH8017 | PKX → ZUH | Jun 24, 09:39 UTC | Jun 24, 09:55 UTC | 15m |
| 2026-06-21 | HBH8059 | PKX → HLD | Jun 21, 01:25 UTC | Jun 21, 01:39 UTC | 15m |
| 2026-06-20 | HBH8059 | PKX → HLD | Jun 20, 01:29 UTC | Jun 20, 01:39 UTC | 10m |
| 2026-06-12 | HBH3287 | SJW → HAK | Jun 12, 01:35 UTC | Jun 12, 01:50 UTC | 15m |
| 2026-06-11 | HBH3287 | SJW → HAK | Jun 11, 02:55 UTC | Jun 11, 03:05 UTC | 10m |
| 2026-06-10 | HBH3287 | SJW → HAK | Jun 10, 03:40 UTC | Jun 11, 03:05 UTC | 23h 25m |
| 2026-06-07 | HBH8031 | PKX → XIY | Jun 7, 09:05 UTC | Jun 7, 09:15 UTC | 10m |
| 2026-06-07 | HBH8059 | PKX → HLD | Jun 7, 01:24 UTC | Jun 7, 01:35 UTC | 10m |
| 2026-06-06 | HBH8007 | PKX → URC | Jun 6, 07:00 UTC | Jun 6, 09:45 UTC | 2h 45m |
| 2026-06-04 | HBH8008 | URC → PKX | Jun 4, 09:20 UTC | Jun 4, 09:45 UTC | 25m |
| 2026-06-03 | HBH8036 | CKG → PKX | Jun 3, 13:45 UTC | Jun 3, 14:00 UTC | 15m |
| 2026-06-03 | HBH8070 | JIC → PKX | Jun 3, 04:50 UTC | Jun 3, 05:05 UTC | 15m |
| 2026-06-02 | HBH3268 | SZX → SJW | Jun 2, 04:25 UTC | Jun 2, 04:35 UTC | 10m |
| 2026-05-22 | HBH8059 | PKX → HLD | May 22, 01:35 UTC | May 22, 01:45 UTC | 10m |
| 2026-05-18 | HBH8070 | JIC → PKX | May 18, 05:10 UTC | May 18, 05:20 UTC | 10m |
| 2026-04-29 | HBH8025 | PKX → NZL | Apr 29, 00:00 UTC | Apr 29, 00:10 UTC | 10m |
| 2026-04-25 | HBH8014 | - | Apr 25, 04:05 UTC | Apr 25, 04:20 UTC | 15m |
| 2026-04-21 | HBH3294 | SJW → HGH | Apr 21, 06:25 UTC | Apr 21, 06:35 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-1328 page for operator, model, and routing details .