sensors Mode-S transponder
780FA2
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-7865 · BOEING 737-800
- Hex
- 780FA2
- Octal
- 36007642
- Decimal
- 7,868,322
- Country
- CN
- Tail
- B-7865
- Type
- B738
- Flights observed
- 36
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 19h ago
Last known position
Country allocation
The ICAO 24-bit address 780FA2 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 |
|---|---|---|---|
| RLH5308 | - | 3 | 2026-07-13 |
| RLH5040 | - | 3 | 2026-07-04 |
| RLH5039 | - | 3 | 2026-07-04 |
| RLH5004 | Ruili Airlines | 3 | 2026-04-25 |
| RLH5003 | Ruili Airlines | 3 | 2026-04-25 |
| RLH6594 | - | 2 | 2026-07-16 |
| RLH6582 | Ruili Airlines | 2 | 2026-05-30 |
| RLH6577 | - | 2 | 2026-07-21 |
| RLH6531 | Ruili Airlines | 2 | 2026-06-13 |
| RLH5031 | Ruili Airlines | 2 | 2026-04-26 |
| RLH6591 | - | 1 | 2026-07-09 |
| RLH6578 | - | 1 | 2026-07-12 |
| RLH6564 | Ruili Airlines | 1 | 2026-06-22 |
| RLH6562 | - | 1 | 2026-07-18 |
| RLH6561 | - | 1 | 2026-05-21 |
| RLH6549 | - | 1 | 2026-06-28 |
| RLH6548 | - | 1 | 2026-07-08 |
| RLH6538 | Ruili Airlines | 1 | 2026-06-14 |
| RLH5307 | - | 1 | 2026-07-13 |
| RLH5302 | - | 1 | 2026-05-27 |
Recent flights last 36
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-21 | RLH6577 | - | Jul 21, 01:00 UTC | Jul 21, 01:15 UTC | 15m |
| 2026-07-18 | RLH6562 | - | Jul 18, 14:10 UTC | Jul 18, 14:20 UTC | 10m |
| 2026-07-16 | RLH6594 | - | Jul 16, 21:00 UTC | Jul 16, 21:10 UTC | 10m |
| 2026-07-13 | RLH5308 | - | Jul 13, 12:55 UTC | Jul 13, 13:35 UTC | 40m |
| 2026-07-13 | RLH5307 | - | Jul 13, 11:35 UTC | Jul 13, 11:45 UTC | 10m |
| 2026-07-12 | RLH6578 | - | Jul 12, 16:05 UTC | Jul 12, 16:20 UTC | 15m |
| 2026-07-10 | RLH5308 | - | Jul 10, 13:45 UTC | Jul 10, 13:55 UTC | 10m |
| 2026-07-09 | RLH6591 | - | Jul 9, 06:30 UTC | Jul 9, 06:50 UTC | 20m |
| 2026-07-08 | RLH6548 | - | Jul 8, 05:10 UTC | Jul 8, 09:40 UTC | 4h 30m |
| 2026-07-04 | RLH5040 | - | Jul 4, 12:55 UTC | Jul 4, 13:35 UTC | 40m |
| 2026-07-04 | RLH5039 | - | Jul 4, 11:10 UTC | Jul 4, 11:45 UTC | 35m |
| 2026-06-28 | RLH6549 | - | Jun 28, 00:35 UTC | Jun 28, 00:45 UTC | 10m |
| 2026-06-22 | RLH6564 | ZUH → KMG | Jun 22, 02:14 UTC | Jun 22, 11:24 UTC | 9h 10m |
| 2026-06-18 | RLH5040 | CJJ → KMG | Jun 18, 12:35 UTC | Jun 18, 13:15 UTC | 40m |
| 2026-06-18 | RLH5039 | - | Jun 18, 10:40 UTC | Jun 18, 11:15 UTC | 35m |
| 2026-06-16 | RLH5029 | KMG → KOS | Jun 16, 11:40 UTC | Jun 17, 00:50 UTC | 13h 11m |
| 2026-06-14 | RLH6538 | YNT → KMG | Jun 14, 09:50 UTC | Jun 14, 10:20 UTC | 30m |
| 2026-06-13 | RLH6531 | NNY → HRB | Jun 13, 05:15 UTC | Jun 13, 05:30 UTC | 15m |
| 2026-06-12 | RLH6531 | NNY → HRB | Jun 12, 06:40 UTC | Jun 13, 05:30 UTC | 22h 49m |
| 2026-06-11 | RLH6577 | KMG → FOC | Jun 11, 00:35 UTC | Jun 11, 00:45 UTC | 10m |
| 2026-06-06 | RLH6594 | CGO → SHE | Jun 6, 15:25 UTC | Jun 6, 15:34 UTC | 10m |
| 2026-05-30 | RLH6582 | SHE → WUT | May 30, 09:55 UTC | May 30, 10:05 UTC | 10m |
| 2026-05-27 | RLH5308 | HUZ → LUM | May 27, 13:50 UTC | May 28, 06:00 UTC | 16h 10m |
| 2026-05-27 | RLH5302 | - | May 27, 04:14 UTC | May 27, 06:44 UTC | 2h 30m |
| 2026-05-23 | RLH5040 | CJJ → KMG | May 23, 12:30 UTC | May 23, 12:50 UTC | 20m |
| 2026-05-23 | RLH5039 | KMG → CJJ | May 23, 10:45 UTC | May 23, 11:15 UTC | 30m |
| 2026-05-21 | RLH6561 | - | May 21, 06:05 UTC | May 21, 06:15 UTC | 10m |
| 2026-05-02 | RLH6582 | SHE → WUT | May 2, 10:00 UTC | May 2, 10:15 UTC | 15m |
| 2026-04-26 | RLH5031 | WUX → KOS | Apr 26, 08:50 UTC | Apr 26, 09:10 UTC | 20m |
| 2026-04-25 | RLH5004 | SZX → WUX | Apr 25, 10:35 UTC | Apr 26, 09:10 UTC | 22h 35m |
| 2026-04-25 | RLH5003 | WUX → SZX | Apr 25, 08:40 UTC | Apr 25, 08:55 UTC | 15m |
| 2026-04-21 | RLH5004 | SZX → WUX | Apr 21, 10:25 UTC | Apr 21, 11:25 UTC | 1h 0m |
| 2026-04-21 | RLH5003 | WUX → SZX | Apr 21, 09:05 UTC | Apr 21, 09:15 UTC | 10m |
| 2026-04-19 | RLH5031 | WUX → KOS | Apr 19, 10:20 UTC | Apr 19, 10:40 UTC | 20m |
| 2026-04-18 | RLH5004 | SZX → WUX | Apr 18, 10:40 UTC | Apr 18, 10:50 UTC | 10m |
| 2026-04-18 | RLH5003 | WUX → SZX | Apr 18, 08:40 UTC | Apr 18, 09:20 UTC | 40m |
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-7865 page for operator, model, and routing details .