sensors Mode-S transponder
7810CD
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-1595 · BOEING 737-800
- Hex
- 7810CD
- Octal
- 36010315
- Decimal
- 7,868,621
- Country
- CN
- Tail
- B-1595
- Type
- B738
- Flights observed
- 40
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 3d ago
Last known position
Country allocation
The ICAO 24-bit address 7810CD 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 |
|---|---|---|---|
| RLH6564 | Ruili Airlines | 5 | 2026-06-28 |
| RLH6538 | - | 4 | 2026-07-08 |
| RLH5044 | - | 4 | 2026-07-11 |
| RLH5043 | Ruili Airlines | 4 | 2026-07-11 |
| RLH5011 | - | 3 | 2026-07-11 |
| RLH6594 | Ruili Airlines | 2 | 2026-05-05 |
| RLH6549 | - | 2 | 2026-07-11 |
| RLH6531 | - | 2 | 2026-07-07 |
| RLH5302 | - | 2 | 2026-05-13 |
| RLH5301 | - | 2 | 2026-05-13 |
| RLH6563 | - | 1 | 2026-06-14 |
| RLH6562 | - | 1 | 2026-04-23 |
| RLH6561 | - | 1 | 2026-04-23 |
| RLH6554 | Ruili Airlines | 1 | 2026-06-01 |
| RLH6548 | - | 1 | 2026-05-20 |
| RLH6537 | - | 1 | 2026-07-06 |
| RLH5308 | Ruili Airlines | 1 | 2026-05-13 |
| RLH5307 | Ruili Airlines | 1 | 2026-05-13 |
| RLH5038 | - | 1 | 2026-07-14 |
| RLH5037 | - | 1 | 2026-07-14 |
Recent flights last 40
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | RLH5038 | - | Jul 14, 09:10 UTC | Jul 14, 09:30 UTC | 20m |
| 2026-07-14 | RLH5037 | - | Jul 14, 07:40 UTC | Jul 14, 08:00 UTC | 20m |
| 2026-07-11 | RLH6549 | - | Jul 11, 15:20 UTC | Jul 12, 10:55 UTC | 19h 35m |
| 2026-07-11 | RLH5044 | - | Jul 11, 14:50 UTC | Jul 12, 10:55 UTC | 20h 5m |
| 2026-07-11 | RLH5043 | KMG → HPH | Jul 11, 13:30 UTC | Jul 11, 13:45 UTC | 15m |
| 2026-07-11 | RLH5011 | - | Jul 11, 03:35 UTC | Jul 11, 03:55 UTC | 20m |
| 2026-07-08 | RLH6538 | - | Jul 8, 10:00 UTC | Jul 8, 10:45 UTC | 45m |
| 2026-07-07 | RLH6531 | - | Jul 7, 06:15 UTC | Jul 7, 06:30 UTC | 15m |
| 2026-07-06 | RLH6531 | - | Jul 6, 10:40 UTC | Jul 7, 06:30 UTC | 19h 50m |
| 2026-07-06 | RLH6537 | - | Jul 6, 05:40 UTC | Jul 6, 10:40 UTC | 5h 0m |
| 2026-07-05 | RLH6538 | - | Jul 5, 10:00 UTC | Jul 6, 05:55 UTC | 19h 55m |
| 2026-07-05 | RLH6538 | - | Jul 5, 04:35 UTC | Jul 5, 10:35 UTC | 6h 0m |
| 2026-06-30 | RLH5044 | HPH → KMG | Jun 30, 15:30 UTC | Jun 30, 15:50 UTC | 20m |
| 2026-06-30 | RLH5043 | KMG → HPH | Jun 30, 14:00 UTC | Jun 30, 14:20 UTC | 20m |
| 2026-06-30 | RLH5011 | - | Jun 30, 03:15 UTC | Jun 30, 03:40 UTC | 25m |
| 2026-06-28 | RLH6564 | ZUH → KMG | Jun 28, 02:20 UTC | Jun 28, 02:34 UTC | 15m |
| 2026-06-20 | RLH5044 | HPH → KMG | Jun 20, 14:39 UTC | Jun 20, 15:14 UTC | 35m |
| 2026-06-20 | RLH5043 | KMG → HPH | Jun 20, 12:54 UTC | Jun 20, 13:29 UTC | 35m |
| 2026-06-20 | RLH5011 | - | Jun 20, 03:09 UTC | Jun 20, 03:34 UTC | 25m |
| 2026-06-19 | RLH6564 | ZUH → KMG | Jun 19, 02:35 UTC | Jun 19, 11:04 UTC | 8h 30m |
| 2026-06-15 | RLH6564 | ZUH → KMG | Jun 15, 02:30 UTC | Jun 15, 02:55 UTC | 25m |
| 2026-06-14 | RLH6564 | ZUH → KMG | Jun 14, 02:50 UTC | Jun 14, 03:05 UTC | 15m |
| 2026-06-14 | RLH6563 | - | Jun 14, 00:05 UTC | Jun 14, 00:15 UTC | 10m |
| 2026-06-06 | RLH6564 | ZUH → KMG | Jun 6, 14:04 UTC | Jun 7, 00:39 UTC | 10h 35m |
| 2026-06-04 | RLH5044 | HPH → KMG | Jun 4, 14:15 UTC | Jun 4, 14:45 UTC | 30m |
| 2026-06-04 | RLH5043 | - | Jun 4, 12:40 UTC | Jun 4, 13:05 UTC | 25m |
| 2026-06-01 | RLH6554 | BAR → KMG | Jun 1, 14:40 UTC | Jun 1, 14:50 UTC | 10m |
| 2026-05-22 | RLH6549 | - | May 22, 00:25 UTC | May 22, 00:35 UTC | 10m |
| 2026-05-20 | RLH6548 | - | May 20, 05:30 UTC | May 20, 09:05 UTC | 3h 35m |
| 2026-05-13 | RLH5308 | HUZ → LUM | May 13, 14:30 UTC | May 14, 01:20 UTC | 10h 50m |
| 2026-05-13 | RLH5307 | LUM → HUZ | May 13, 13:10 UTC | May 13, 13:20 UTC | 10m |
| 2026-05-13 | RLH5302 | - | May 13, 07:30 UTC | May 13, 07:55 UTC | 25m |
| 2026-05-13 | RLH5301 | - | May 13, 03:55 UTC | May 13, 04:15 UTC | 20m |
| 2026-05-05 | RLH6594 | CGO → SHE | May 5, 08:30 UTC | May 5, 15:40 UTC | 7h 10m |
| 2026-04-25 | RLH6594 | CGO → SHE | Apr 25, 15:30 UTC | Apr 25, 15:40 UTC | 10m |
| 2026-04-23 | RLH6562 | - | Apr 23, 14:25 UTC | Apr 23, 14:50 UTC | 25m |
| 2026-04-23 | RLH6561 | - | Apr 23, 05:55 UTC | Apr 23, 06:05 UTC | 10m |
| 2026-04-17 | RLH6538 | YNT → KMG | Apr 17, 10:00 UTC | Apr 17, 10:10 UTC | 10m |
| 2026-04-15 | RLH5302 | - | Apr 15, 07:01 UTC | Apr 15, 07:25 UTC | 25m |
| 2026-04-15 | RLH5301 | - | Apr 15, 03:50 UTC | Apr 15, 04:00 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-1595 page for operator, model, and routing details .