sensors Mode-S transponder
78144B
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-1189 · BOEING 737-800
- Hex
- 78144B
- Octal
- 36012113
- Decimal
- 7,869,515
- Country
- CN
- Tail
- B-1189
- Type
- B738
- Flights observed
- 35
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address 78144B 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 |
|---|---|---|---|
| RLH6577 | - | 6 | 2026-07-20 |
| RLH6549 | - | 3 | 2026-06-03 |
| RLH5308 | - | 3 | 2026-07-03 |
| RLH6587 | Ruili Airlines | 2 | 2026-06-21 |
| RLH6582 | - | 2 | 2026-06-30 |
| RLH6561 | - | 2 | 2026-06-11 |
| RLH6538 | - | 2 | 2026-06-29 |
| RLH6531 | Ruili Airlines | 2 | 2026-05-26 |
| RLH5011 | Ruili Airlines | 2 | 2026-07-21 |
| RLH6562 | - | 1 | 2026-05-02 |
| RLH5307 | Ruili Airlines | 1 | 2026-05-29 |
| RLH5302 | - | 1 | 2026-04-24 |
| RLH5044 | Ruili Airlines | 1 | 2026-06-23 |
| RLH5043 | Ruili Airlines | 1 | 2026-06-23 |
| RLH5038 | - | 1 | 2026-07-07 |
| RLH5037 | - | 1 | 2026-07-07 |
| RLH5029 | Ruili Airlines | 1 | 2026-06-25 |
| RLH5016 | Ruili Airlines | 1 | 2026-06-18 |
| RLH5015 | Ruili Airlines | 1 | 2026-06-27 |
| RLH5009 | - | 1 | 2026-06-22 |
Recent flights last 35
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-21 | RLH5011 | BAV → TSN | Jul 21, 03:15 UTC | Jul 21, 03:40 UTC | 25m |
| 2026-07-20 | RLH6577 | - | Jul 20, 13:35 UTC | Jul 20, 13:45 UTC | 10m |
| 2026-07-19 | RLH6577 | - | Jul 19, 13:40 UTC | Jul 19, 13:50 UTC | 10m |
| 2026-07-07 | RLH5038 | - | Jul 7, 09:35 UTC | Jul 7, 10:05 UTC | 30m |
| 2026-07-07 | RLH5037 | - | Jul 7, 08:15 UTC | Jul 7, 08:50 UTC | 35m |
| 2026-07-03 | RLH5308 | - | Jul 3, 13:40 UTC | Jul 3, 13:55 UTC | 15m |
| 2026-07-01 | RLH6577 | - | Jul 1, 13:40 UTC | Jul 1, 13:50 UTC | 10m |
| 2026-06-30 | RLH6582 | - | Jun 30, 09:40 UTC | Jun 30, 09:55 UTC | 15m |
| 2026-06-29 | RLH6538 | - | Jun 29, 09:54 UTC | Jun 29, 10:40 UTC | 45m |
| 2026-06-27 | RLH5015 | WUX → TFU | Jun 27, 06:35 UTC | Jun 27, 11:39 UTC | 5h 5m |
| 2026-06-25 | RLH5029 | KMG → KOS | Jun 25, 11:30 UTC | Jun 25, 16:14 UTC | 4h 45m |
| 2026-06-23 | RLH5044 | HPH → KMG | Jun 23, 14:49 UTC | Jun 24, 00:40 UTC | 9h 50m |
| 2026-06-23 | RLH5043 | KMG → HPH | Jun 23, 12:55 UTC | Jun 23, 13:24 UTC | 30m |
| 2026-06-23 | RLH5011 | - | Jun 23, 03:25 UTC | Jun 23, 03:45 UTC | 20m |
| 2026-06-22 | RLH5009 | - | Jun 22, 05:40 UTC | Jun 22, 10:25 UTC | 4h 45m |
| 2026-06-21 | RLH6587 | SHE → WUT | Jun 21, 08:44 UTC | Jun 21, 08:54 UTC | 10m |
| 2026-06-18 | RLH5016 | TFU → WUX | Jun 18, 06:05 UTC | Jun 18, 11:00 UTC | 4h 55m |
| 2026-06-11 | RLH6561 | - | Jun 11, 06:00 UTC | Jun 11, 06:10 UTC | 10m |
| 2026-06-03 | RLH6549 | - | Jun 3, 00:35 UTC | Jun 3, 00:45 UTC | 10m |
| 2026-06-01 | RLH6549 | - | Jun 1, 00:30 UTC | Jun 1, 03:20 UTC | 2h 50m |
| 2026-05-29 | RLH5308 | HUZ → LUM | May 29, 15:10 UTC | May 29, 16:05 UTC | 55m |
| 2026-05-29 | RLH5307 | LUM → HUZ | May 29, 12:00 UTC | May 29, 12:55 UTC | 55m |
| 2026-05-27 | RLH6538 | YNT → KMG | May 27, 09:45 UTC | May 27, 10:30 UTC | 45m |
| 2026-05-26 | RLH6531 | NNY → HRB | May 26, 05:00 UTC | May 26, 05:20 UTC | 20m |
| 2026-05-25 | RLH6531 | NNY → HRB | May 25, 09:45 UTC | May 26, 05:20 UTC | 19h 34m |
| 2026-05-17 | RLH6587 | SHE → WUT | May 17, 08:30 UTC | May 17, 08:40 UTC | 10m |
| 2026-05-10 | RLH6577 | KMG → FOC | May 10, 10:35 UTC | May 10, 10:45 UTC | 10m |
| 2026-05-05 | RLH6577 | KMG → FOC | May 5, 00:25 UTC | May 5, 00:35 UTC | 10m |
| 2026-05-02 | RLH6562 | - | May 2, 14:30 UTC | May 2, 14:40 UTC | 10m |
| 2026-05-02 | RLH6561 | - | May 2, 06:00 UTC | May 2, 06:10 UTC | 10m |
| 2026-04-29 | RLH5308 | HUZ → LUM | Apr 29, 13:35 UTC | Apr 30, 01:15 UTC | 11h 39m |
| 2026-04-28 | RLH6582 | SHE → WUT | Apr 28, 10:05 UTC | Apr 28, 10:15 UTC | 10m |
| 2026-04-27 | RLH6577 | KMG → FOC | Apr 27, 02:00 UTC | Apr 27, 10:55 UTC | 8h 55m |
| 2026-04-24 | RLH5302 | - | Apr 24, 06:30 UTC | Apr 24, 06:50 UTC | 20m |
| 2026-04-17 | RLH6549 | - | Apr 17, 00:40 UTC | Apr 17, 00:50 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-1189 page for operator, model, and routing details .