sensors Mode-S transponder
780BFD
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-1926 · BOEING 737-800
- Hex
- 780BFD
- Octal
- 36005775
- Decimal
- 7,867,389
- Country
- CN
- Tail
- B-1926
- Type
- B738
- Flights observed
- 78
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address 780BFD 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 |
|---|---|---|---|
| KNA8369 | - | 13 | 2026-06-12 |
| KNA8370 | Knight Air | 9 | 2026-06-12 |
| KNA8272 | - | 9 | 2026-07-11 |
| KNA8269 | - | 7 | 2026-06-28 |
| KNA8286 | Knight Air | 6 | 2026-06-07 |
| KNA8271 | Knight Air | 6 | 2026-06-10 |
| KNA8270 | - | 6 | 2026-06-28 |
| KNA8249 | Knight Air | 6 | 2026-05-30 |
| KNA8368 | - | 2 | 2026-04-14 |
| KNA8367 | Knight Air | 2 | 2026-04-14 |
| KNA8280 | Knight Air | 2 | 2026-06-18 |
| KNA8274 | - | 2 | 2026-06-15 |
| KNA8285 | Knight Air | 1 | 2026-05-31 |
| KNA8284 | Knight Air | 1 | 2026-06-17 |
| KNA8283 | Knight Air | 1 | 2026-06-17 |
| KNA8282 | - | 1 | 2026-06-21 |
| KNA8278 | Knight Air | 1 | 2026-05-18 |
| KNA8250 | Knight Air | 1 | 2026-05-29 |
| KNA8245 | Knight Air | 1 | 2026-05-03 |
| KNA8214 | - | 1 | 2026-07-11 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-11 | KNA8272 | - | Jul 11, 23:25 UTC | Jul 11, 23:40 UTC | 15m |
| 2026-07-11 | KNA8214 | - | Jul 11, 04:15 UTC | Jul 11, 11:45 UTC | 7h 30m |
| 2026-06-28 | KNA8270 | - | Jun 28, 05:45 UTC | Jun 28, 06:05 UTC | 20m |
| 2026-06-28 | KNA8269 | - | Jun 28, 03:14 UTC | Jun 28, 03:40 UTC | 25m |
| 2026-06-25 | KNA8272 | - | Jun 25, 23:14 UTC | Jun 26, 00:05 UTC | 50m |
| 2026-06-21 | KNA8282 | - | Jun 21, 04:14 UTC | Jun 21, 05:10 UTC | 55m |
| 2026-06-18 | KNA8280 | CAN → KMG | Jun 18, 15:40 UTC | Jun 18, 16:50 UTC | 1h 10m |
| 2026-06-17 | KNA8284 | HAK → KMG | Jun 17, 14:00 UTC | Jun 17, 14:30 UTC | 30m |
| 2026-06-17 | KNA8283 | KMG → HAK | Jun 17, 11:35 UTC | Jun 17, 11:50 UTC | 15m |
| 2026-06-15 | KNA8274 | - | Jun 15, 03:35 UTC | Jun 15, 03:55 UTC | 20m |
| 2026-06-15 | KNA8274 | - | Jun 15, 02:44 UTC | Jun 15, 02:55 UTC | 10m |
| 2026-06-12 | KNA8370 | BKK → KMG | Jun 12, 13:35 UTC | Jun 12, 14:35 UTC | 1h 0m |
| 2026-06-12 | KNA8369 | - | Jun 12, 10:55 UTC | Jun 12, 11:35 UTC | 40m |
| 2026-06-10 | KNA8272 | SZX → KMG | Jun 10, 23:25 UTC | Jun 11, 00:15 UTC | 50m |
| 2026-06-10 | KNA8271 | KMG → SZX | Jun 10, 16:35 UTC | Jun 10, 16:45 UTC | 10m |
| 2026-06-09 | KNA8370 | BKK → KMG | Jun 9, 13:20 UTC | Jun 10, 08:25 UTC | 19h 5m |
| 2026-06-09 | KNA8369 | KMG → BKK | Jun 9, 11:00 UTC | Jun 9, 11:30 UTC | 30m |
| 2026-06-07 | KNA8286 | HUZ → KMG | Jun 7, 14:45 UTC | Jun 8, 05:00 UTC | 14h 15m |
| 2026-06-05 | KNA8286 | HUZ → KMG | Jun 5, 17:15 UTC | Jun 5, 17:30 UTC | 15m |
| 2026-06-05 | KNA8286 | HUZ → KMG | Jun 5, 16:30 UTC | Jun 5, 16:40 UTC | 10m |
| 2026-06-04 | KNA8271 | KMG → SZX | Jun 4, 16:55 UTC | Jun 4, 17:05 UTC | 10m |
| 2026-06-02 | KNA8370 | BKK → KMG | Jun 2, 13:10 UTC | Jun 2, 14:05 UTC | 55m |
| 2026-06-02 | KNA8369 | KMG → BKK | Jun 2, 10:40 UTC | Jun 2, 11:35 UTC | 55m |
| 2026-05-31 | KNA8286 | HUZ → KMG | May 31, 16:25 UTC | May 31, 16:35 UTC | 10m |
| 2026-05-31 | KNA8286 | HUZ → KMG | May 31, 15:40 UTC | May 31, 15:55 UTC | 15m |
| 2026-05-31 | KNA8285 | KMG → HUZ | May 31, 14:20 UTC | May 31, 14:30 UTC | 10m |
| 2026-05-30 | KNA8249 | KHN → HRB | May 30, 13:20 UTC | May 30, 13:35 UTC | 15m |
| 2026-05-29 | KNA8250 | HRB → KHN | May 29, 01:25 UTC | May 29, 13:20 UTC | 11h 55m |
| 2026-05-28 | KNA8249 | KHN → HRB | May 28, 13:25 UTC | May 29, 13:15 UTC | 23h 50m |
| 2026-05-28 | KNA8249 | KHN → HRB | May 28, 02:55 UTC | May 28, 13:40 UTC | 10h 45m |
| 2026-05-27 | KNA8370 | BKK → KMG | May 27, 13:20 UTC | May 27, 14:10 UTC | 50m |
| 2026-05-27 | KNA8369 | KMG → BKK | May 27, 01:59 UTC | May 27, 11:35 UTC | 9h 36m |
| 2026-05-26 | KNA8369 | KMG → BKK | May 26, 13:19 UTC | May 27, 11:35 UTC | 22h 16m |
| 2026-05-26 | KNA8369 | KMG → BKK | May 26, 13:10 UTC | May 27, 11:15 UTC | 22h 6m |
| 2026-05-23 | KNA8370 | BKK → KMG | May 23, 13:05 UTC | May 23, 14:00 UTC | 55m |
| 2026-05-23 | KNA8369 | KMG → BKK | May 23, 10:30 UTC | May 23, 11:30 UTC | 1h 0m |
| 2026-05-22 | KNA8269 | KMG → PEK | May 22, 03:00 UTC | May 22, 03:30 UTC | 30m |
| 2026-05-19 | KNA8249 | KHN → HRB | May 19, 13:50 UTC | May 20, 02:05 UTC | 12h 15m |
| 2026-05-19 | KNA8249 | KHN → HRB | May 19, 01:50 UTC | May 19, 14:05 UTC | 12h 15m |
| 2026-05-18 | KNA8249 | KHN → HRB | May 18, 13:10 UTC | May 19, 02:00 UTC | 12h 49m |
| 2026-05-18 | KNA8278 | WUH → KMG | May 18, 02:20 UTC | May 18, 02:35 UTC | 15m |
| 2026-05-13 | KNA8370 | BKK → KMG | May 13, 13:15 UTC | May 13, 14:05 UTC | 50m |
| 2026-05-13 | KNA8369 | KMG → BKK | May 13, 10:50 UTC | May 13, 11:45 UTC | 55m |
| 2026-05-11 | KNA8370 | BKK → KMG | May 11, 13:20 UTC | May 11, 14:20 UTC | 1h 0m |
| 2026-05-11 | KNA8369 | KMG → BKK | May 11, 10:40 UTC | May 11, 11:45 UTC | 1h 5m |
| 2026-05-10 | KNA8369 | KMG → BKK | May 10, 13:30 UTC | May 11, 11:45 UTC | 22h 15m |
| 2026-05-10 | KNA8369 | KMG → BKK | May 10, 10:35 UTC | May 10, 11:35 UTC | 1h 0m |
| 2026-05-08 | KNA8280 | CAN → KMG | May 8, 14:35 UTC | May 9, 05:05 UTC | 14h 30m |
| 2026-05-08 | KNA8270 | PEK → KMG | May 8, 05:59 UTC | May 8, 06:25 UTC | 25m |
| 2026-05-08 | KNA8269 | KMG → PEK | May 8, 03:30 UTC | May 8, 03:49 UTC | 20m |
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-1926 page for operator, model, and routing details .