sensors Mode-S transponder
7810F5
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-6868 · BOEING 737-800
- Hex
- 7810F5
- Octal
- 36010365
- Decimal
- 7,868,661
- Country
- CN
- Tail
- B-6868
- Type
- B738
- Flights observed
- 35
- Distinct callsigns
- 13
- Country
- CN
- Last broadcast
- 9h ago
Last known position
Country allocation
The ICAO 24-bit address 7810F5 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 13 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| HBH3287 | Hebei Airlines | 7 | 2026-06-09 |
| HBH3268 | - | 6 | 2026-07-10 |
| HBH3656 | - | 4 | 2026-07-06 |
| HBH3331 | - | 4 | 2026-07-02 |
| HBH3301 | - | 4 | 2026-07-19 |
| HBH3655 | - | 2 | 2026-07-06 |
| HBH3267 | - | 2 | 2026-07-03 |
| HBH3611 | Hebei Airlines | 1 | 2026-05-03 |
| HBH3609 | Hebei Airlines | 1 | 2026-05-17 |
| HBH3602 | - | 1 | 2026-07-08 |
| HBH3601 | - | 1 | 2026-07-08 |
| HBH3289 | - | 1 | 2026-07-14 |
| HBH3212 | - | 1 | 2026-06-28 |
Recent flights last 35
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-19 | HBH3301 | - | Jul 19, 01:35 UTC | Jul 19, 01:45 UTC | 10m |
| 2026-07-14 | HBH3289 | - | Jul 14, 02:15 UTC | Jul 14, 11:20 UTC | 9h 5m |
| 2026-07-10 | HBH3268 | - | Jul 10, 04:15 UTC | Jul 10, 04:25 UTC | 10m |
| 2026-07-08 | HBH3602 | - | Jul 8, 15:40 UTC | Jul 8, 15:55 UTC | 15m |
| 2026-07-08 | HBH3601 | - | Jul 8, 11:35 UTC | Jul 8, 11:50 UTC | 15m |
| 2026-07-06 | HBH3656 | - | Jul 6, 17:20 UTC | Jul 6, 17:30 UTC | 10m |
| 2026-07-06 | HBH3655 | - | Jul 6, 15:55 UTC | Jul 6, 16:05 UTC | 10m |
| 2026-07-03 | HBH3268 | - | Jul 3, 04:15 UTC | Jul 3, 04:30 UTC | 15m |
| 2026-07-03 | HBH3267 | - | Jul 3, 02:30 UTC | Jul 3, 02:50 UTC | 20m |
| 2026-07-02 | HBH3331 | - | Jul 2, 10:45 UTC | Jul 2, 11:00 UTC | 15m |
| 2026-07-02 | HBH3268 | - | Jul 2, 04:15 UTC | Jul 2, 04:25 UTC | 10m |
| 2026-06-30 | HBH3331 | - | Jun 30, 11:50 UTC | Jul 1, 10:55 UTC | 23h 5m |
| 2026-06-28 | HBH3212 | - | Jun 28, 05:55 UTC | Jun 28, 06:05 UTC | 10m |
| 2026-06-24 | HBH3301 | - | Jun 24, 10:10 UTC | Jun 25, 01:50 UTC | 15h 40m |
| 2026-06-23 | HBH3301 | - | Jun 23, 01:45 UTC | Jun 23, 02:04 UTC | 20m |
| 2026-06-21 | HBH3331 | - | Jun 21, 10:04 UTC | Jun 21, 13:20 UTC | 3h 15m |
| 2026-06-14 | HBH3656 | SZX → SJW | Jun 14, 12:25 UTC | Jun 14, 12:35 UTC | 10m |
| 2026-06-09 | HBH3287 | SJW → HAK | Jun 9, 03:40 UTC | Jun 9, 03:55 UTC | 15m |
| 2026-06-08 | HBH3287 | SJW → HAK | Jun 8, 06:40 UTC | Jun 9, 03:55 UTC | 21h 15m |
| 2026-06-08 | HBH3287 | SJW → HAK | Jun 8, 03:45 UTC | Jun 8, 06:50 UTC | 3h 5m |
| 2026-05-29 | HBH3301 | SJW → SYX | May 29, 03:45 UTC | May 29, 04:00 UTC | 15m |
| 2026-05-26 | HBH3287 | SJW → HAK | May 26, 03:40 UTC | May 26, 03:55 UTC | 15m |
| 2026-05-25 | HBH3656 | SZX → SJW | May 25, 13:15 UTC | May 25, 13:30 UTC | 15m |
| 2026-05-17 | HBH3609 | SJW → SYX | May 17, 01:35 UTC | May 17, 01:50 UTC | 15m |
| 2026-05-08 | HBH3287 | SJW → HAK | May 8, 01:45 UTC | May 8, 01:55 UTC | 10m |
| 2026-05-06 | HBH3331 | SJW → SYX | May 6, 09:45 UTC | May 6, 10:05 UTC | 20m |
| 2026-05-03 | HBH3611 | HGH → SYX | May 3, 03:05 UTC | May 3, 07:45 UTC | 4h 39m |
| 2026-04-27 | HBH3268 | SZX → SJW | Apr 27, 04:50 UTC | Apr 27, 05:00 UTC | 10m |
| 2026-04-25 | HBH3268 | SZX → SJW | Apr 25, 04:20 UTC | Apr 25, 04:30 UTC | 10m |
| 2026-04-22 | HBH3287 | SJW → HAK | Apr 22, 01:50 UTC | Apr 22, 02:05 UTC | 15m |
| 2026-04-20 | HBH3287 | SJW → HAK | Apr 20, 01:45 UTC | Apr 20, 02:10 UTC | 25m |
| 2026-04-19 | HBH3656 | SZX → SJW | Apr 19, 12:35 UTC | Apr 19, 12:45 UTC | 10m |
| 2026-04-19 | HBH3655 | SJW → SZX | Apr 19, 10:45 UTC | Apr 19, 11:00 UTC | 15m |
| 2026-04-19 | HBH3268 | SZX → SJW | Apr 19, 04:15 UTC | Apr 19, 04:25 UTC | 10m |
| 2026-04-19 | HBH3267 | SJW → SZX | Apr 19, 02:25 UTC | Apr 19, 02: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-6868 page for operator, model, and routing details .