sensors Mode-S transponder
781305
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-1208 · BOEING 737-800
- Hex
- 781305
- Octal
- 36011405
- Decimal
- 7,869,189
- Country
- CN
- Tail
- B-1208
- Type
- B738
- Flights observed
- 39
- Distinct callsigns
- 16
- Country
- CN
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address 781305 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 16 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| LKE9708 | - | 6 | 2026-07-20 |
| LKE9662 | Lucky Air | 6 | 2026-05-27 |
| LKE9890 | - | 4 | 2026-07-24 |
| LKE9667 | Lucky Air | 4 | 2026-06-20 |
| LKE9545 | - | 4 | 2026-07-01 |
| LKE9980 | Lucky Air | 3 | 2026-06-06 |
| LKE9877 | - | 2 | 2026-06-28 |
| LKE9683 | Lucky Air | 2 | 2026-07-23 |
| LKE998Z | - | 1 | 2026-05-21 |
| LKE9979 | Lucky Air | 1 | 2026-05-21 |
| LKE9973 | - | 1 | 2026-07-26 |
| LKE9732 | - | 1 | 2026-05-03 |
| LKE9696 | - | 1 | 2026-07-07 |
| LKE9684 | Lucky Air | 1 | 2026-07-23 |
| LKE9668 | Lucky Air | 1 | 2026-06-18 |
| LKE9561 | - | 1 | 2026-07-02 |
Recent flights last 39
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | LKE9973 | - | Jul 26, 13:55 UTC | Jul 26, 14:05 UTC | 10m |
| 2026-07-24 | LKE9890 | - | Jul 24, 15:45 UTC | Jul 24, 15:55 UTC | 10m |
| 2026-07-23 | LKE9684 | SJW → TFU | Jul 23, 09:45 UTC | Jul 23, 09:55 UTC | 10m |
| 2026-07-23 | LKE9683 | TFU → SJW | Jul 23, 05:40 UTC | Jul 23, 05:55 UTC | 15m |
| 2026-07-20 | LKE9708 | - | Jul 20, 03:05 UTC | Jul 20, 03:15 UTC | 10m |
| 2026-07-07 | LKE9696 | - | Jul 7, 11:35 UTC | Jul 7, 14:30 UTC | 2h 55m |
| 2026-07-06 | LKE9708 | - | Jul 6, 00:30 UTC | Jul 6, 04:35 UTC | 4h 5m |
| 2026-07-05 | LKE9708 | - | Jul 5, 02:30 UTC | Jul 6, 00:40 UTC | 22h 10m |
| 2026-07-05 | LKE9708 | - | Jul 5, 00:20 UTC | Jul 5, 02:50 UTC | 2h 30m |
| 2026-07-04 | LKE9708 | - | Jul 4, 03:30 UTC | Jul 5, 02:50 UTC | 23h 20m |
| 2026-07-04 | LKE9708 | - | Jul 4, 02:40 UTC | Jul 5, 00:35 UTC | 21h 55m |
| 2026-07-03 | LKE9890 | - | Jul 3, 18:45 UTC | Jul 4, 03:40 UTC | 8h 55m |
| 2026-07-02 | LKE9561 | - | Jul 2, 08:50 UTC | Jul 3, 00:20 UTC | 15h 30m |
| 2026-07-01 | LKE9545 | - | Jul 1, 23:45 UTC | Jul 2, 09:00 UTC | 9h 15m |
| 2026-06-29 | LKE9545 | - | Jun 29, 16:10 UTC | Jun 30, 09:05 UTC | 16h 56m |
| 2026-06-29 | LKE9890 | - | Jun 29, 15:30 UTC | Jun 29, 15:39 UTC | 10m |
| 2026-06-28 | LKE9877 | - | Jun 28, 13:10 UTC | Jun 28, 13:19 UTC | 10m |
| 2026-06-26 | LKE9545 | - | Jun 26, 13:19 UTC | Jun 27, 09:00 UTC | 19h 40m |
| 2026-06-26 | LKE9545 | AEB → TSN | Jun 26, 12:24 UTC | Jun 27, 09:00 UTC | 20h 35m |
| 2026-06-21 | LKE9890 | - | Jun 21, 15:25 UTC | Jun 21, 16:30 UTC | 1h 5m |
| 2026-06-20 | LKE9667 | TFU → HAK | Jun 20, 10:44 UTC | Jun 20, 10:59 UTC | 15m |
| 2026-06-18 | LKE9668 | HAK → TFU | Jun 18, 13:10 UTC | Jun 18, 13:25 UTC | 15m |
| 2026-06-18 | LKE9667 | TFU → HAK | Jun 18, 02:45 UTC | Jun 18, 11:05 UTC | 8h 20m |
| 2026-06-17 | LKE9667 | TFU → HAK | Jun 17, 14:10 UTC | Jun 18, 11:05 UTC | 20h 55m |
| 2026-06-17 | LKE9667 | TFU → HAK | Jun 17, 11:45 UTC | Jun 17, 12:00 UTC | 15m |
| 2026-06-06 | LKE9980 | SZX → KMG | Jun 6, 15:34 UTC | Jun 6, 15:44 UTC | 10m |
| 2026-05-30 | LKE9980 | SZX → KMG | May 30, 12:00 UTC | May 30, 12:10 UTC | 10m |
| 2026-05-27 | LKE9662 | ZUH → TFU | May 27, 06:15 UTC | May 27, 06:40 UTC | 25m |
| 2026-05-21 | LKE9980 | SZX → KMG | May 21, 17:15 UTC | May 21, 17:25 UTC | 10m |
| 2026-05-21 | LKE9979 | KMG → SZX | May 21, 14:30 UTC | May 21, 14:45 UTC | 15m |
| 2026-05-21 | LKE998Z | - | May 21, 07:50 UTC | May 21, 08:00 UTC | 10m |
| 2026-05-06 | LKE9877 | - | May 6, 13:00 UTC | May 6, 13:15 UTC | 15m |
| 2026-05-03 | LKE9732 | - | May 3, 05:40 UTC | May 3, 13:05 UTC | 7h 25m |
| 2026-05-01 | LKE9662 | ZUH → TFU | May 1, 02:50 UTC | May 1, 07:05 UTC | 4h 15m |
| 2026-04-29 | LKE9662 | ZUH → TFU | Apr 29, 03:10 UTC | Apr 29, 06:39 UTC | 3h 30m |
| 2026-04-28 | LKE9683 | TFU → SJW | Apr 28, 03:05 UTC | Apr 28, 03:20 UTC | 15m |
| 2026-04-27 | LKE9662 | ZUH → TFU | Apr 27, 06:15 UTC | Apr 28, 03:20 UTC | 21h 5m |
| 2026-04-24 | LKE9662 | ZUH → TFU | Apr 24, 06:20 UTC | Apr 24, 06:40 UTC | 20m |
| 2026-04-22 | LKE9662 | ZUH → TFU | Apr 22, 08:50 UTC | Apr 22, 09:00 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-1208 page for operator, model, and routing details .