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