sensors Mode-S transponder
7811B4
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-1470 · BOEING 737-800
- Hex
- 7811B4
- Octal
- 36010664
- Decimal
- 7,868,852
- Country
- CN
- Tail
- B-1470
- Type
- B738
- Flights observed
- 38
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 7811B4 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 |
|---|---|---|---|
| CUA5569 | - | 4 | 2026-07-11 |
| CUA5290 | - | 4 | 2026-07-08 |
| CUA5705 | China United Airlines | 3 | 2026-06-14 |
| CUA5802 | China United Airlines | 2 | 2026-06-05 |
| CUA5686 | China United Airlines | 2 | 2026-05-01 |
| CUA5685 | China United Airlines | 2 | 2026-05-01 |
| CUA5525 | - | 2 | 2026-07-15 |
| CUA5396 | China United Airlines | 2 | 2026-04-25 |
| CUA5307 | - | 2 | 2026-06-30 |
| CUA5119 | China United Airlines | 2 | 2026-05-28 |
| CUA877 | - | 1 | 2026-07-15 |
| CUA5852 | China United Airlines | 1 | 2026-06-10 |
| CUA5801 | China United Airlines | 1 | 2026-06-03 |
| CUA5692 | - | 1 | 2026-07-18 |
| CUA5630 | China United Airlines | 1 | 2026-05-19 |
| CUA5509 | China United Airlines | 1 | 2026-07-01 |
| CUA5252 | - | 1 | 2026-06-21 |
| CUA5251 | - | 1 | 2026-06-21 |
| CUA5009 | - | 1 | 2026-05-10 |
| CUA5001 | - | 1 | 2026-06-20 |
Recent flights last 38
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-18 | CUA5692 | - | Jul 18, 15:20 UTC | Jul 18, 15:35 UTC | 15m |
| 2026-07-15 | CUA877 | - | Jul 15, 05:50 UTC | Jul 15, 06:00 UTC | 10m |
| 2026-07-15 | CUA5525 | - | Jul 15, 00:30 UTC | Jul 15, 00:40 UTC | 10m |
| 2026-07-11 | CUA5569 | - | Jul 11, 01:50 UTC | Jul 11, 02:00 UTC | 10m |
| 2026-07-08 | CUA5290 | - | Jul 8, 23:25 UTC | Jul 9, 04:35 UTC | 5h 10m |
| 2026-07-01 | CUA5509 | PKX → JXA | Jul 1, 23:15 UTC | Jul 1, 23:30 UTC | 15m |
| 2026-06-30 | CUA5307 | - | Jun 30, 17:30 UTC | Jun 30, 17:40 UTC | 10m |
| 2026-06-30 | CUA5307 | - | Jun 30, 14:20 UTC | Jun 30, 14:35 UTC | 15m |
| 2026-06-21 | CUA5252 | - | Jun 21, 09:00 UTC | Jun 21, 09:10 UTC | 10m |
| 2026-06-21 | CUA5251 | - | Jun 21, 07:09 UTC | Jun 21, 07:34 UTC | 25m |
| 2026-06-20 | CUA5001 | - | Jun 20, 00:44 UTC | Jun 20, 02:04 UTC | 1h 20m |
| 2026-06-14 | CUA5705 | FUO → PVG | Jun 14, 08:15 UTC | Jun 14, 08:25 UTC | 10m |
| 2026-06-13 | CUA2319 | SJW → DBC | Jun 13, 07:15 UTC | Jun 13, 07:25 UTC | 10m |
| 2026-06-12 | CUA2930 | HLD → SJW | Jun 12, 08:55 UTC | Jun 12, 09:10 UTC | 15m |
| 2026-06-12 | CUA2929 | PVG → SJW | Jun 12, 04:30 UTC | Jun 12, 04:45 UTC | 15m |
| 2026-06-10 | CUA5852 | SZX → PKX | Jun 10, 10:15 UTC | Jun 10, 10:25 UTC | 10m |
| 2026-06-08 | CUA5569 | PKX → DQA | Jun 8, 05:10 UTC | Jun 8, 05:25 UTC | 15m |
| 2026-06-05 | CUA5802 | DSN → PKX | Jun 5, 05:35 UTC | Jun 5, 05:50 UTC | 15m |
| 2026-06-03 | CUA5801 | PKX → DSN | Jun 3, 08:25 UTC | Jun 3, 08:35 UTC | 10m |
| 2026-05-30 | CUA5290 | - | May 30, 04:10 UTC | May 30, 04:25 UTC | 15m |
| 2026-05-28 | CUA5119 | TFU → HUZ | May 28, 03:15 UTC | May 28, 03:25 UTC | 10m |
| 2026-05-26 | CUA5569 | PKX → DQA | May 26, 05:10 UTC | May 26, 05:25 UTC | 15m |
| 2026-05-24 | CUA5705 | FUO → PVG | May 24, 11:30 UTC | May 24, 12:00 UTC | 30m |
| 2026-05-23 | CUA5705 | FUO → PVG | May 23, 09:20 UTC | May 23, 09:30 UTC | 10m |
| 2026-05-19 | CUA5630 | XNN → PKX | May 19, 13:30 UTC | May 19, 13:45 UTC | 15m |
| 2026-05-14 | CUA5290 | - | May 14, 03:45 UTC | May 14, 04:30 UTC | 45m |
| 2026-05-10 | CUA5009 | - | May 10, 06:20 UTC | May 10, 06:40 UTC | 20m |
| 2026-05-09 | CUA5119 | TFU → HUZ | May 9, 03:05 UTC | May 9, 03:15 UTC | 10m |
| 2026-05-01 | CUA5686 | HMI → PKX | May 1, 14:10 UTC | May 1, 14:25 UTC | 15m |
| 2026-05-01 | CUA5685 | PKX → HMI | May 1, 08:00 UTC | May 1, 08:20 UTC | 20m |
| 2026-05-01 | CUA5802 | DSN → PKX | May 1, 05:35 UTC | May 1, 05:50 UTC | 15m |
| 2026-04-29 | CUA5569 | PKX → DQA | Apr 29, 05:09 UTC | Apr 29, 05:20 UTC | 10m |
| 2026-04-25 | CUA5396 | DSN → PKX | Apr 25, 14:40 UTC | Apr 25, 14:50 UTC | 10m |
| 2026-04-25 | CUA5396 | DSN → PKX | Apr 25, 10:10 UTC | Apr 25, 10:20 UTC | 10m |
| 2026-04-23 | CUA5290 | - | Apr 23, 04:05 UTC | Apr 23, 04:20 UTC | 15m |
| 2026-04-20 | CUA5525 | PKX → YSQ | Apr 20, 00:25 UTC | Apr 20, 00:40 UTC | 15m |
| 2026-04-19 | CUA5686 | - | Apr 19, 14:30 UTC | Apr 19, 14:45 UTC | 15m |
| 2026-04-19 | CUA5685 | PKX → HMI | Apr 19, 08:05 UTC | Apr 19, 08:20 UTC | 15m |
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-1470 page for operator, model, and routing details .