sensors Mode-S transponder
780D4D
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-5830 · BOEING 737-700
- Hex
- 780D4D
- Octal
- 36006515
- Decimal
- 7,867,725
- Country
- CN
- Tail
- B-5830
- Type
- B737
- Flights observed
- 27
- Distinct callsigns
- 11
- Country
- CN
- Last broadcast
- 10h ago
Last known position
Country allocation
The ICAO 24-bit address 780D4D 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 11 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| RLH5051 | - | 9 | 2026-07-18 |
| RLH5038 | Ruili Airlines | 3 | 2026-07-22 |
| RLH6564 | Ruili Airlines | 2 | 2026-06-26 |
| RLH5302 | - | 2 | 2026-06-07 |
| RLH5052 | - | 2 | 2026-07-04 |
| RLH5042 | - | 2 | 2026-04-25 |
| RLH5041 | - | 2 | 2026-04-25 |
| RLH5037 | Ruili Airlines | 2 | 2026-07-21 |
| RLH5349 | Ruili Airlines | 1 | 2026-04-27 |
| RLH5040 | Ruili Airlines | 1 | 2026-05-16 |
| RLH5039 | Ruili Airlines | 1 | 2026-05-16 |
Recent flights last 27
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-22 | RLH5038 | MDL → LUM | Jul 22, 12:15 UTC | Jul 22, 12:40 UTC | 25m |
| 2026-07-21 | RLH5038 | MDL → LUM | Jul 21, 09:20 UTC | Jul 21, 09:45 UTC | 25m |
| 2026-07-21 | RLH5037 | LUM → MDL | Jul 21, 01:20 UTC | Jul 21, 08:05 UTC | 6h 45m |
| 2026-07-18 | RLH5051 | - | Jul 18, 03:40 UTC | Jul 18, 09:05 UTC | 5h 25m |
| 2026-07-16 | RLH5051 | - | Jul 16, 03:40 UTC | Jul 16, 08:50 UTC | 5h 10m |
| 2026-07-11 | RLH5051 | - | Jul 11, 03:30 UTC | Jul 11, 09:05 UTC | 5h 35m |
| 2026-07-09 | RLH5051 | - | Jul 9, 04:15 UTC | Jul 9, 08:45 UTC | 4h 30m |
| 2026-07-04 | RLH5052 | - | Jul 4, 03:50 UTC | Jul 4, 09:05 UTC | 5h 15m |
| 2026-06-29 | RLH5038 | - | Jun 29, 11:50 UTC | Jun 30, 05:20 UTC | 17h 31m |
| 2026-06-29 | RLH5037 | - | Jun 29, 10:34 UTC | Jun 29, 11:10 UTC | 35m |
| 2026-06-26 | RLH6564 | ZUH → KMG | Jun 26, 02:20 UTC | Jun 26, 02:40 UTC | 20m |
| 2026-06-18 | RLH6564 | ZUH → KMG | Jun 18, 14:40 UTC | Jun 18, 15:05 UTC | 25m |
| 2026-06-11 | RLH5051 | - | Jun 11, 04:00 UTC | Jun 11, 09:10 UTC | 5h 10m |
| 2026-06-09 | RLH5051 | - | Jun 9, 03:45 UTC | Jun 9, 08:50 UTC | 5h 5m |
| 2026-06-07 | RLH5302 | - | Jun 7, 13:00 UTC | Jun 7, 15:45 UTC | 2h 45m |
| 2026-06-06 | RLH5051 | - | Jun 6, 03:25 UTC | Jun 6, 09:09 UTC | 5h 45m |
| 2026-05-30 | RLH5052 | - | May 30, 03:45 UTC | May 30, 09:05 UTC | 5h 20m |
| 2026-05-28 | RLH5051 | - | May 28, 03:40 UTC | May 28, 08:35 UTC | 4h 55m |
| 2026-05-16 | RLH5040 | CJJ → KMG | May 16, 14:51 UTC | May 16, 15:10 UTC | 20m |
| 2026-05-16 | RLH5039 | KMG → CJJ | May 16, 13:11 UTC | May 16, 13:41 UTC | 30m |
| 2026-05-06 | RLH5302 | - | May 6, 06:25 UTC | May 6, 08:30 UTC | 2h 5m |
| 2026-04-27 | RLH5349 | LUM → FOC | Apr 27, 02:00 UTC | Apr 27, 02:10 UTC | 10m |
| 2026-04-25 | RLH5042 | - | Apr 25, 07:10 UTC | Apr 25, 07:45 UTC | 35m |
| 2026-04-25 | RLH5041 | - | Apr 25, 04:20 UTC | Apr 25, 05:20 UTC | 1h 0m |
| 2026-04-23 | RLH5051 | - | Apr 23, 05:40 UTC | Apr 23, 05:50 UTC | 10m |
| 2026-04-18 | RLH5042 | - | Apr 18, 07:05 UTC | Apr 18, 07:20 UTC | 15m |
| 2026-04-18 | RLH5041 | - | Apr 18, 04:55 UTC | Apr 18, 05:20 UTC | 25m |
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-5830 page for operator, model, and routing details .