sensors Mode-S transponder
78101C
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-7990 · BOEING 737-800
- Hex
- 78101C
- Octal
- 36010034
- Decimal
- 7,868,444
- Country
- CN
- Tail
- B-7990
- Type
- B738
- Flights observed
- 56
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- Jul 21, 15:40 UTC
Last known position
Country allocation
The ICAO 24-bit address 78101C 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 |
|---|---|---|---|
| LKE9662 | - | 7 | 2026-07-01 |
| LKE9844 | Lucky Air | 5 | 2026-06-11 |
| LKE9556 | - | 4 | 2026-06-29 |
| LKE9972 | Lucky Air | 3 | 2026-06-24 |
| LKE9971 | Lucky Air | 3 | 2026-06-23 |
| LKE9966 | Lucky Air | 3 | 2026-06-22 |
| LKE9965 | Lucky Air | 3 | 2026-06-25 |
| LKE9695 | Lucky Air | 3 | 2026-06-30 |
| LKE9555 | - | 3 | 2026-06-29 |
| LKE9980 | Lucky Air | 2 | 2026-06-09 |
| LKE9890 | - | 2 | 2026-06-17 |
| LKE9889 | Lucky Air | 2 | 2026-06-17 |
| LKE9879 | Lucky Air | 2 | 2026-06-09 |
| LKE9668 | Lucky Air | 2 | 2026-06-22 |
| LKE9884 | - | 1 | 2026-06-25 |
| LKE9880 | Lucky Air | 1 | 2026-04-16 |
| LKE9877 | - | 1 | 2026-06-27 |
| LKE9707 | - | 1 | 2026-07-18 |
| LKE9696 | - | 1 | 2026-07-21 |
| LKE9692 | Lucky Air | 1 | 2026-06-14 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-21 | LKE9696 | - | Jul 21, 04:15 UTC | Jul 21, 15:40 UTC | 11h 25m |
| 2026-07-20 | - | - | Jul 20, 08:05 UTC | Jul 21, 07:00 UTC | 22h 54m |
| 2026-07-18 | LKE9707 | - | Jul 18, 00:25 UTC | Jul 18, 03:10 UTC | 2h 46m |
| 2026-07-01 | LKE9662 | - | Jul 1, 06:00 UTC | Jul 1, 11:50 UTC | 5h 50m |
| 2026-06-30 | LKE9662 | - | Jun 30, 14:00 UTC | Jul 1, 11:50 UTC | 21h 50m |
| 2026-06-30 | LKE9662 | - | Jun 30, 11:10 UTC | Jul 1, 06:20 UTC | 19h 10m |
| 2026-06-30 | LKE9662 | - | Jun 30, 10:55 UTC | Jul 1, 06:20 UTC | 19h 25m |
| 2026-06-30 | LKE9695 | TFU → SYX | Jun 30, 04:55 UTC | Jun 30, 14:00 UTC | 9h 5m |
| 2026-06-29 | LKE9556 | - | Jun 29, 09:05 UTC | Jun 29, 09:20 UTC | 15m |
| 2026-06-29 | LKE9555 | - | Jun 29, 04:45 UTC | Jun 29, 05:00 UTC | 15m |
| 2026-06-27 | LKE9877 | - | Jun 27, 13:09 UTC | Jun 27, 13:24 UTC | 15m |
| 2026-06-26 | LKE9695 | TFU → SYX | Jun 26, 00:20 UTC | Jun 26, 14:09 UTC | 13h 50m |
| 2026-06-25 | LKE9965 | KMG → SYX | Jun 25, 07:05 UTC | Jun 26, 03:50 UTC | 20h 45m |
| 2026-06-25 | LKE9884 | - | Jun 25, 03:54 UTC | Jun 26, 00:39 UTC | 20h 45m |
| 2026-06-24 | LKE9972 | HAK → KMG | Jun 24, 10:25 UTC | Jun 25, 01:19 UTC | 14h 55m |
| 2026-06-24 | LKE9972 | HAK → KMG | Jun 24, 02:45 UTC | Jun 24, 12:54 UTC | 10h 10m |
| 2026-06-23 | LKE9971 | KMG → HAK | Jun 23, 23:55 UTC | Jun 24, 00:20 UTC | 25m |
| 2026-06-22 | LKE9668 | HAK → TFU | Jun 22, 13:59 UTC | Jun 22, 14:14 UTC | 15m |
| 2026-06-22 | LKE9966 | SYX → KMG | Jun 22, 00:24 UTC | Jun 22, 11:44 UTC | 11h 20m |
| 2026-06-18 | LKE9561 | - | Jun 18, 06:55 UTC | Jun 18, 23:30 UTC | 16h 35m |
| 2026-06-17 | LKE9890 | - | Jun 17, 17:00 UTC | Jun 18, 07:00 UTC | 14h 0m |
| 2026-06-17 | LKE9889 | KMG → SZX | Jun 17, 15:35 UTC | Jun 17, 15:46 UTC | 10m |
| 2026-06-17 | LKE9889 | KMG → SZX | Jun 17, 14:25 UTC | Jun 17, 14:35 UTC | 10m |
| 2026-06-14 | LKE9692 | SYX → TFU | Jun 14, 05:55 UTC | Jun 14, 06:10 UTC | 15m |
| 2026-06-14 | LKE9691 | TFU → SYX | Jun 14, 03:00 UTC | Jun 14, 03:20 UTC | 20m |
| 2026-06-12 | LKE9695 | TFU → SYX | Jun 12, 00:35 UTC | Jun 12, 14:01 UTC | 13h 25m |
| 2026-06-11 | LKE9966 | SYX → KMG | Jun 11, 12:50 UTC | Jun 12, 11:00 UTC | 22h 10m |
| 2026-06-11 | LKE9844 | KOW → HAK | Jun 11, 10:00 UTC | Jun 12, 03:40 UTC | 17h 41m |
| 2026-06-11 | LKE9844 | KOW → HAK | Jun 11, 03:05 UTC | Jun 12, 00:35 UTC | 21h 31m |
| 2026-06-10 | LKE9971 | KMG → HAK | Jun 10, 07:45 UTC | Jun 11, 00:20 UTC | 16h 35m |
| 2026-06-09 | LKE9980 | SZX → KMG | Jun 9, 12:50 UTC | Jun 10, 07:55 UTC | 19h 5m |
| 2026-06-09 | LKE9980 | SZX → KMG | Jun 9, 12:05 UTC | Jun 9, 12:15 UTC | 10m |
| 2026-06-09 | LKE9879 | KMG → FOC | Jun 9, 01:40 UTC | Jun 9, 01:50 UTC | 10m |
| 2026-06-07 | LKE9971 | KMG → HAK | Jun 7, 07:50 UTC | Jun 8, 00:15 UTC | 16h 25m |
| 2026-06-07 | LKE9966 | SYX → KMG | Jun 7, 03:40 UTC | Jun 8, 00:15 UTC | 20h 35m |
| 2026-06-06 | LKE9965 | KMG → SYX | Jun 6, 14:09 UTC | Jun 7, 07:50 UTC | 17h 40m |
| 2026-06-06 | LKE9965 | KMG → SYX | Jun 6, 11:55 UTC | Jun 7, 07:50 UTC | 19h 55m |
| 2026-06-06 | LKE9972 | HAK → KMG | Jun 6, 00:10 UTC | Jun 6, 14:14 UTC | 14h 5m |
| 2026-06-05 | LKE9890 | SZX → KMG | Jun 5, 17:05 UTC | Jun 6, 14:14 UTC | 21h 10m |
| 2026-06-03 | LKE9684 | SJW → TFU | Jun 3, 07:20 UTC | Jun 3, 07:30 UTC | 10m |
| 2026-06-03 | LKE9683 | TFU → SJW | Jun 3, 03:00 UTC | Jun 3, 03:15 UTC | 15m |
| 2026-05-29 | LKE9668 | HAK → TFU | May 29, 14:00 UTC | May 29, 14:15 UTC | 15m |
| 2026-05-28 | LKE9662 | ZUH → TFU | May 28, 15:30 UTC | May 29, 06:35 UTC | 15h 5m |
| 2026-05-28 | LKE9667 | - | May 28, 13:10 UTC | May 28, 13:25 UTC | 15m |
| 2026-05-16 | LKE9879 | KMG → FOC | May 16, 01:40 UTC | May 16, 01:55 UTC | 15m |
| 2026-05-12 | LKE9844 | KOW → HAK | May 12, 03:15 UTC | May 12, 11:05 UTC | 7h 50m |
| 2026-05-08 | LKE9662 | ZUH → TFU | May 8, 02:39 UTC | May 8, 06:30 UTC | 3h 50m |
| 2026-05-06 | LKE9662 | ZUH → TFU | May 6, 02:40 UTC | May 6, 06:45 UTC | 4h 5m |
| 2026-05-04 | LKE9556 | SJW → KMG | May 4, 08:55 UTC | May 4, 09:15 UTC | 20m |
| 2026-05-04 | LKE9555 | SJW → HRB | May 4, 04:44 UTC | May 4, 05:00 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-7990 page for operator, model, and routing details .