sensors Mode-S transponder
781448
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-1186 · BOEING 737-800
- Hex
- 781448
- Octal
- 36012110
- Decimal
- 7,869,512
- Country
- CN
- Tail
- B-1186
- Type
- B738
- Flights observed
- 43
- Distinct callsigns
- 19
- Country
- CN
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address 781448 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 19 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| RLH6577 | - | 6 | 2026-06-29 |
| RLH5039 | - | 5 | 2026-06-23 |
| RLH5040 | Ruili Airlines | 4 | 2026-06-23 |
| RLH5004 | - | 4 | 2026-07-02 |
| RLH5003 | - | 4 | 2026-07-02 |
| RLH6564 | - | 3 | 2026-07-21 |
| RLH5043 | Ruili Airlines | 3 | 2026-07-16 |
| RLH5044 | - | 2 | 2026-07-16 |
| RLH5029 | Ruili Airlines | 2 | 2026-06-11 |
| RLH6578 | Ruili Airlines | 1 | 2026-05-29 |
| RLH6563 | - | 1 | 2026-07-11 |
| RLH6554 | Ruili Airlines | 1 | 2026-06-21 |
| RLH6553 | Ruili Airlines | 1 | 2026-06-21 |
| RLH6550 | - | 1 | 2026-07-22 |
| RLH6549 | - | 1 | 2026-07-22 |
| RLH5097 | - | 1 | 2026-07-09 |
| RLH5032 | Ruili Airlines | 1 | 2026-06-14 |
| RLH5030 | - | 1 | 2026-07-04 |
| RLH5011 | Ruili Airlines | 1 | 2026-05-07 |
Recent flights last 43
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-22 | RLH6550 | - | Jul 22, 15:20 UTC | Jul 22, 15:35 UTC | 15m |
| 2026-07-22 | RLH6549 | - | Jul 22, 12:55 UTC | Jul 22, 13:05 UTC | 10m |
| 2026-07-21 | RLH6564 | - | Jul 21, 14:55 UTC | Jul 21, 15:05 UTC | 10m |
| 2026-07-16 | RLH5044 | - | Jul 16, 14:35 UTC | Jul 16, 14:55 UTC | 20m |
| 2026-07-16 | RLH5043 | KMG → HPH | Jul 16, 13:05 UTC | Jul 16, 13:20 UTC | 15m |
| 2026-07-11 | RLH6563 | - | Jul 11, 13:55 UTC | Jul 11, 14:05 UTC | 10m |
| 2026-07-09 | RLH5097 | - | Jul 9, 01:25 UTC | Jul 9, 01:40 UTC | 15m |
| 2026-07-04 | RLH5030 | - | Jul 4, 10:55 UTC | Jul 4, 16:00 UTC | 5h 5m |
| 2026-07-02 | RLH5004 | - | Jul 2, 10:35 UTC | Jul 2, 10:50 UTC | 15m |
| 2026-07-02 | RLH5003 | - | Jul 2, 07:55 UTC | Jul 2, 08:40 UTC | 45m |
| 2026-06-29 | RLH6577 | - | Jun 29, 23:39 UTC | Jun 30, 01:09 UTC | 1h 30m |
| 2026-06-29 | RLH6577 | - | Jun 29, 02:30 UTC | Jun 30, 01:09 UTC | 22h 40m |
| 2026-06-27 | RLH6577 | - | Jun 27, 00:25 UTC | Jun 27, 00:39 UTC | 15m |
| 2026-06-24 | RLH6577 | - | Jun 24, 23:40 UTC | Jun 25, 00:29 UTC | 50m |
| 2026-06-23 | RLH5040 | CJJ → KMG | Jun 23, 12:35 UTC | Jun 23, 13:00 UTC | 25m |
| 2026-06-23 | RLH5039 | - | Jun 23, 10:39 UTC | Jun 23, 11:04 UTC | 25m |
| 2026-06-21 | RLH6554 | BAR → KMG | Jun 21, 14:50 UTC | Jun 21, 15:05 UTC | 15m |
| 2026-06-21 | RLH6553 | KMG → BAR | Jun 21, 13:04 UTC | Jun 21, 13:20 UTC | 15m |
| 2026-06-19 | RLH6577 | KMG → FOC | Jun 19, 23:44 UTC | Jun 20, 00:39 UTC | 55m |
| 2026-06-16 | RLH5004 | SZX → WUX | Jun 16, 11:55 UTC | Jun 16, 12:05 UTC | 10m |
| 2026-06-16 | RLH5003 | - | Jun 16, 09:34 UTC | Jun 16, 10:30 UTC | 55m |
| 2026-06-14 | RLH5032 | KOS → WUX | Jun 14, 08:30 UTC | Jun 14, 13:50 UTC | 5h 20m |
| 2026-06-11 | RLH5029 | KMG → KOS | Jun 11, 11:55 UTC | Jun 11, 16:55 UTC | 5h 0m |
| 2026-06-10 | RLH5029 | KMG → KOS | Jun 10, 13:55 UTC | Jun 11, 12:00 UTC | 22h 5m |
| 2026-06-10 | RLH6577 | KMG → FOC | Jun 10, 10:35 UTC | Jun 10, 13:55 UTC | 3h 20m |
| 2026-06-09 | RLH6564 | ZUH → KMG | Jun 9, 14:45 UTC | Jun 10, 13:55 UTC | 23h 10m |
| 2026-06-06 | RLH5040 | CJJ → KMG | Jun 6, 12:35 UTC | Jun 6, 12:54 UTC | 20m |
| 2026-06-06 | RLH5039 | KMG → CJJ | Jun 6, 11:09 UTC | Jun 6, 11:39 UTC | 30m |
| 2026-06-04 | RLH5040 | CJJ → KMG | Jun 4, 12:15 UTC | Jun 4, 12:35 UTC | 20m |
| 2026-06-04 | RLH5039 | KMG → CJJ | Jun 4, 10:35 UTC | Jun 4, 11:00 UTC | 25m |
| 2026-06-03 | RLH5039 | KMG → CJJ | Jun 3, 14:40 UTC | Jun 4, 11:00 UTC | 20h 20m |
| 2026-05-30 | RLH5044 | - | May 30, 14:25 UTC | May 30, 14:55 UTC | 30m |
| 2026-05-30 | RLH5043 | - | May 30, 12:45 UTC | May 30, 13:20 UTC | 35m |
| 2026-05-29 | RLH5043 | - | May 29, 14:05 UTC | May 30, 13:20 UTC | 23h 15m |
| 2026-05-29 | RLH6578 | FOC → KMG | May 29, 13:55 UTC | May 29, 14:05 UTC | 10m |
| 2026-05-28 | RLH6564 | ZUH → KMG | May 28, 14:10 UTC | May 28, 14:30 UTC | 20m |
| 2026-05-19 | RLH5004 | SZX → WUX | May 19, 11:35 UTC | May 19, 12:20 UTC | 45m |
| 2026-05-19 | RLH5003 | WUX → SZX | May 19, 09:25 UTC | May 19, 09:45 UTC | 20m |
| 2026-05-07 | RLH5011 | BAV → TSN | May 7, 02:50 UTC | May 7, 03:15 UTC | 25m |
| 2026-05-05 | RLH5004 | SZX → WUX | May 5, 10:00 UTC | May 5, 10:10 UTC | 10m |
| 2026-05-05 | RLH5003 | WUX → SZX | May 5, 08:10 UTC | May 5, 08:35 UTC | 25m |
| 2026-04-18 | RLH5040 | CJJ → KMG | Apr 18, 12:55 UTC | Apr 18, 13:35 UTC | 40m |
| 2026-04-18 | RLH5039 | KMG → CJJ | Apr 18, 10:50 UTC | Apr 18, 11:35 UTC | 45m |
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-1186 page for operator, model, and routing details .