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