sensors Mode-S transponder
78101F
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-7993 · BOEING 737-800
- Hex
- 78101F
- Octal
- 36010037
- Decimal
- 7,868,447
- Country
- CN
- Tail
- B-7993
- Type
- B738
- Flights observed
- 41
- Distinct callsigns
- 19
- Country
- CN
- Last broadcast
- 17h ago
Last known position
Country allocation
The ICAO 24-bit address 78101F 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 |
|---|---|---|---|
| LKE9708 | - | 8 | 2026-07-11 |
| LKE9877 | - | 4 | 2026-06-19 |
| LKE9890 | - | 3 | 2026-06-22 |
| LKE9844 | Lucky Air | 3 | 2026-05-23 |
| LKE9556 | - | 3 | 2026-06-21 |
| LKE9965 | Lucky Air | 2 | 2026-06-02 |
| LKE9707 | - | 2 | 2026-05-29 |
| LKE9662 | - | 2 | 2026-07-14 |
| LKE9571 | Lucky Air | 2 | 2026-07-17 |
| LKE9561 | - | 2 | 2026-06-21 |
| LKE9555 | - | 2 | 2026-07-05 |
| LKE9980 | Lucky Air | 1 | 2026-06-07 |
| LKE9974 | Lucky Air | 1 | 2026-06-18 |
| LKE9973 | Lucky Air | 1 | 2026-06-18 |
| LKE9966 | Lucky Air | 1 | 2026-06-01 |
| LKE9884 | - | 1 | 2026-06-17 |
| LKE9879 | Lucky Air | 1 | 2026-05-26 |
| LKE9597 | Lucky Air | 1 | 2026-06-15 |
| LKE9545 | Lucky Air | 1 | 2026-04-23 |
Recent flights last 41
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | LKE9571 | KMG → KOW | Jul 17, 09:30 UTC | Jul 17, 09:45 UTC | 15m |
| 2026-07-14 | LKE9662 | - | Jul 14, 02:50 UTC | Jul 14, 07:20 UTC | 4h 30m |
| 2026-07-11 | LKE9708 | - | Jul 11, 02:30 UTC | Jul 11, 02:50 UTC | 20m |
| 2026-07-09 | LKE9708 | - | Jul 9, 00:20 UTC | Jul 9, 02:40 UTC | 2h 20m |
| 2026-07-07 | LKE9708 | - | Jul 7, 03:00 UTC | Jul 7, 03:15 UTC | 15m |
| 2026-07-05 | LKE9555 | - | Jul 5, 04:40 UTC | Jul 5, 04:55 UTC | 15m |
| 2026-06-22 | LKE9890 | - | Jun 22, 17:00 UTC | Jun 22, 17:20 UTC | 20m |
| 2026-06-22 | LKE9890 | - | Jun 22, 16:14 UTC | Jun 22, 16:24 UTC | 10m |
| 2026-06-21 | LKE9561 | - | Jun 21, 23:30 UTC | Jun 22, 00:24 UTC | 55m |
| 2026-06-21 | LKE9556 | - | Jun 21, 08:54 UTC | Jun 21, 09:10 UTC | 15m |
| 2026-06-21 | LKE9555 | SJW → HRB | Jun 21, 04:44 UTC | Jun 21, 05:00 UTC | 15m |
| 2026-06-19 | LKE9877 | - | Jun 19, 13:09 UTC | Jun 19, 13:20 UTC | 10m |
| 2026-06-18 | LKE9974 | HAK → KMG | Jun 18, 15:35 UTC | Jun 19, 13:20 UTC | 21h 44m |
| 2026-06-18 | LKE9973 | KMG → HAK | Jun 18, 12:50 UTC | Jun 18, 13:15 UTC | 25m |
| 2026-06-17 | LKE9884 | - | Jun 17, 07:35 UTC | Jun 17, 08:00 UTC | 25m |
| 2026-06-15 | LKE9597 | CGO → SYX | Jun 15, 09:45 UTC | Jun 15, 10:09 UTC | 25m |
| 2026-06-13 | LKE9561 | - | Jun 13, 09:30 UTC | Jun 14, 00:30 UTC | 15h 0m |
| 2026-06-11 | LKE9877 | - | Jun 11, 13:00 UTC | Jun 12, 00:20 UTC | 11h 20m |
| 2026-06-07 | LKE9980 | SZX → KMG | Jun 7, 14:15 UTC | Jun 8, 04:15 UTC | 14h 0m |
| 2026-06-02 | LKE9965 | KMG → SYX | Jun 2, 00:25 UTC | Jun 2, 03:50 UTC | 3h 25m |
| 2026-06-01 | LKE9966 | SYX → KMG | Jun 1, 03:55 UTC | Jun 2, 03:45 UTC | 23h 50m |
| 2026-06-01 | LKE9965 | KMG → SYX | Jun 1, 00:30 UTC | Jun 1, 04:10 UTC | 3h 40m |
| 2026-05-30 | LKE9708 | - | May 30, 02:20 UTC | May 30, 03:25 UTC | 1h 5m |
| 2026-05-29 | LKE9707 | - | May 29, 17:45 UTC | May 30, 01:00 UTC | 7h 15m |
| 2026-05-26 | LKE9879 | KMG → FOC | May 26, 02:15 UTC | May 26, 02:29 UTC | 15m |
| 2026-05-23 | LKE9844 | KOW → HAK | May 23, 10:25 UTC | May 23, 10:40 UTC | 15m |
| 2026-05-22 | LKE9844 | KOW → HAK | May 22, 13:20 UTC | May 23, 10:40 UTC | 21h 19m |
| 2026-05-22 | LKE9877 | - | May 22, 00:15 UTC | May 22, 13:30 UTC | 13h 15m |
| 2026-05-18 | LKE9890 | SZX → KMG | May 18, 16:20 UTC | May 18, 16:35 UTC | 15m |
| 2026-05-05 | LKE9708 | - | May 5, 02:35 UTC | May 5, 07:45 UTC | 5h 10m |
| 2026-05-04 | LKE9877 | - | May 4, 12:50 UTC | May 5, 00:25 UTC | 11h 36m |
| 2026-05-03 | LKE9662 | ZUH → TFU | May 3, 03:00 UTC | May 3, 06:35 UTC | 3h 34m |
| 2026-05-01 | LKE9844 | KOW → HAK | May 1, 03:00 UTC | May 1, 10:25 UTC | 7h 25m |
| 2026-04-29 | LKE9556 | SJW → KMG | Apr 29, 09:00 UTC | Apr 29, 09:20 UTC | 20m |
| 2026-04-26 | LKE9556 | SJW → KMG | Apr 26, 04:40 UTC | Apr 26, 09:05 UTC | 4h 25m |
| 2026-04-23 | LKE9708 | - | Apr 23, 08:50 UTC | Apr 24, 03:15 UTC | 18h 24m |
| 2026-04-23 | LKE9708 | - | Apr 23, 04:35 UTC | Apr 24, 03:15 UTC | 22h 40m |
| 2026-04-23 | LKE9545 | KMG → KOW | Apr 23, 00:50 UTC | Apr 23, 09:01 UTC | 8h 11m |
| 2026-04-20 | LKE9708 | - | Apr 20, 02:40 UTC | Apr 20, 02:55 UTC | 15m |
| 2026-04-20 | LKE9707 | - | Apr 20, 00:40 UTC | Apr 20, 00:50 UTC | 10m |
| 2026-04-16 | LKE9571 | KMG → KOW | Apr 16, 07:54 UTC | Apr 16, 08:09 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-7993 page for operator, model, and routing details .