sensors Mode-S transponder
78057D
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-5459 · BOEING 737-800
- Hex
- 78057D
- Octal
- 36002575
- Decimal
- 7,865,725
- Country
- CN
- Tail
- B-5459
- Type
- B738
- Flights observed
- 37
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 8d ago
Last known position
Country allocation
The ICAO 24-bit address 78057D 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 |
|---|---|---|---|
| HBH3656 | - | 4 | 2026-07-15 |
| HBH3655 | - | 4 | 2026-07-15 |
| HBH3242 | - | 4 | 2026-07-23 |
| HBH8025 | - | 3 | 2026-06-29 |
| HBH8072 | - | 2 | 2026-07-08 |
| HBH8040 | - | 2 | 2026-07-07 |
| HBH8017 | Hebei Airlines | 2 | 2026-07-03 |
| HBH3327 | Hebei Airlines | 2 | 2026-05-05 |
| HBH8018 | - | 1 | 2026-07-03 |
| HBH8016 | - | 1 | 2026-05-20 |
| HBH3690 | Hebei Airlines | 1 | 2026-06-13 |
| HBH3689 | Hebei Airlines | 1 | 2026-06-13 |
| HBH3328 | Hebei Airlines | 1 | 2026-05-05 |
| HBH3326 | Hebei Airlines | 1 | 2026-07-24 |
| HBH3325 | Hebei Airlines | 1 | 2026-07-23 |
| HBH3318 | Hebei Airlines | 1 | 2026-07-24 |
| HBH3294 | Hebei Airlines | 1 | 2026-06-09 |
| HBH3289 | Hebei Airlines | 1 | 2026-04-24 |
| HBH3268 | - | 1 | 2026-07-17 |
| HBH3245 | Hebei Airlines | 1 | 2026-07-24 |
Recent flights last 37
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-24 | HBH3245 | SJW → KHN | Jul 24, 23:05 UTC | Jul 24, 23:25 UTC | 20m |
| 2026-07-24 | HBH3318 | NKG → SJW | Jul 24, 16:15 UTC | Jul 24, 16:35 UTC | 20m |
| 2026-07-24 | HBH3206 | - | Jul 24, 11:15 UTC | Jul 24, 11:45 UTC | 30m |
| 2026-07-24 | HBH3205 | - | Jul 24, 06:35 UTC | Jul 24, 06:50 UTC | 15m |
| 2026-07-24 | HBH3326 | BAR → SJW | Jul 24, 04:25 UTC | Jul 24, 04:35 UTC | 10m |
| 2026-07-23 | HBH3325 | SJW → BAR | Jul 23, 23:25 UTC | Jul 23, 23:40 UTC | 15m |
| 2026-07-23 | HBH3242 | - | Jul 23, 09:25 UTC | Jul 23, 09:45 UTC | 20m |
| 2026-07-22 | HBH3242 | - | Jul 22, 11:45 UTC | Jul 22, 12:25 UTC | 40m |
| 2026-07-17 | HBH3268 | - | Jul 17, 04:29 UTC | Jul 17, 04:39 UTC | 10m |
| 2026-07-15 | HBH3656 | - | Jul 15, 13:10 UTC | Jul 15, 13:20 UTC | 10m |
| 2026-07-15 | HBH3655 | - | Jul 15, 11:40 UTC | Jul 15, 11:50 UTC | 10m |
| 2026-07-08 | HBH8072 | - | Jul 8, 05:15 UTC | Jul 8, 05:25 UTC | 10m |
| 2026-07-07 | HBH8040 | - | Jul 7, 13:45 UTC | Jul 7, 14:00 UTC | 15m |
| 2026-07-04 | HBH8072 | - | Jul 4, 05:05 UTC | Jul 4, 05:20 UTC | 15m |
| 2026-07-03 | HBH8018 | - | Jul 3, 13:20 UTC | Jul 3, 14:10 UTC | 50m |
| 2026-07-03 | HBH8017 | PKX → ZUH | Jul 3, 08:50 UTC | Jul 3, 09:05 UTC | 15m |
| 2026-07-02 | HBH8017 | PKX → ZUH | Jul 2, 09:05 UTC | Jul 2, 09:20 UTC | 15m |
| 2026-06-29 | HBH8025 | - | Jun 29, 00:39 UTC | Jun 29, 00:49 UTC | 10m |
| 2026-06-28 | HBH8040 | KWE → PKX | Jun 28, 13:25 UTC | Jun 28, 13:45 UTC | 20m |
| 2026-06-22 | HBH3655 | - | Jun 22, 10:49 UTC | Jun 22, 11:00 UTC | 10m |
| 2026-06-21 | HBH3656 | SZX → SJW | Jun 21, 12:49 UTC | Jun 21, 13:00 UTC | 10m |
| 2026-06-13 | HBH3690 | HKG → SJW | Jun 13, 05:20 UTC | Jun 13, 05:35 UTC | 15m |
| 2026-06-13 | HBH3689 | SJW → HKG | Jun 13, 03:20 UTC | Jun 13, 03:55 UTC | 35m |
| 2026-06-09 | HBH3294 | SJW → HGH | Jun 9, 09:40 UTC | Jun 9, 09:50 UTC | 10m |
| 2026-05-21 | HBH8025 | PKX → NZL | May 21, 00:35 UTC | May 21, 00:45 UTC | 10m |
| 2026-05-20 | HBH8016 | - | May 20, 11:50 UTC | May 20, 12:00 UTC | 10m |
| 2026-05-15 | HBH3656 | SZX → SJW | May 15, 12:30 UTC | May 15, 12:40 UTC | 10m |
| 2026-05-10 | HBH8025 | PKX → NZL | May 10, 00:39 UTC | May 10, 00:49 UTC | 10m |
| 2026-05-06 | HBH3242 | SHE → SJW | May 6, 09:30 UTC | May 6, 09:40 UTC | 10m |
| 2026-05-05 | HBH3328 | BAR → SJW | May 5, 16:40 UTC | May 6, 05:55 UTC | 13h 14m |
| 2026-05-05 | HBH3327 | SJW → BAR | May 5, 09:55 UTC | May 6, 05:55 UTC | 20h 0m |
| 2026-05-05 | HBH3327 | SJW → BAR | May 5, 06:25 UTC | May 5, 16:45 UTC | 10h 20m |
| 2026-05-04 | HBH3655 | SJW → SZX | May 4, 11:00 UTC | May 4, 11:10 UTC | 10m |
| 2026-05-03 | HBH3656 | SZX → SJW | May 3, 14:05 UTC | May 3, 14:15 UTC | 10m |
| 2026-05-03 | HBH3655 | SJW → SZX | May 3, 11:50 UTC | May 3, 12:05 UTC | 15m |
| 2026-04-28 | HBH3242 | SHE → SJW | Apr 28, 09:10 UTC | Apr 28, 09:20 UTC | 10m |
| 2026-04-24 | HBH3289 | SJW → HAK | Apr 24, 10:45 UTC | Apr 24, 11:05 UTC | 20m |
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-5459 page for operator, model, and routing details .