sensors Mode-S transponder
781754
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-30A1 · AIRBUS A-320neo
- Hex
- 781754
- Octal
- 36013524
- Decimal
- 7,870,292
- Country
- CN
- Tail
- B-30A1
- Type
- A20N
- Flights observed
- 39
- Distinct callsigns
- 16
- Country
- CN
- Last broadcast
- 8d ago
Last known position
Country allocation
The ICAO 24-bit address 781754 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 |
|---|---|---|---|
| QDA917 | Qingdao Airlines | 7 | 2026-05-25 |
| QDA918 | Qingdao Airlines | 6 | 2026-05-25 |
| QDA929 | - | 4 | 2026-05-08 |
| QDA909 | Qingdao Airlines | 3 | 2026-05-17 |
| QDA9786 | - | 2 | 2026-05-26 |
| QDA9785 | - | 2 | 2026-05-26 |
| QDA930 | - | 2 | 2026-05-08 |
| QDA923 | Qingdao Airlines | 2 | 2026-05-11 |
| QDA920 | Qingdao Airlines | 2 | 2026-05-17 |
| QDA910 | Qingdao Airlines | 2 | 2026-05-17 |
| QDA903 | - | 2 | 2026-05-14 |
| QDA926 | Qingdao Airlines | 1 | 2026-05-03 |
| QDA925 | Qingdao Airlines | 1 | 2026-05-18 |
| QDA904 | - | 1 | 2026-05-15 |
| QDA6241 | Qingdao Airlines | 1 | 2026-05-06 |
| QDA6063 | Qingdao Airlines | 1 | 2026-04-25 |
Recent flights last 39
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-26 | QDA9786 | - | May 26, 12:00 UTC | May 26, 12:14 UTC | 15m |
| 2026-05-26 | QDA9785 | - | May 26, 10:14 UTC | May 26, 10:39 UTC | 25m |
| 2026-05-25 | QDA918 | BKK → TAO | May 25, 11:25 UTC | May 25, 12:25 UTC | 1h 0m |
| 2026-05-25 | QDA917 | TAO → BKK | May 25, 09:10 UTC | May 25, 10:10 UTC | 1h 0m |
| 2026-05-23 | QDA918 | BKK → TAO | May 23, 11:45 UTC | May 23, 12:40 UTC | 55m |
| 2026-05-23 | QDA917 | TAO → BKK | May 23, 09:20 UTC | May 23, 10:20 UTC | 1h 0m |
| 2026-05-19 | QDA918 | BKK → TAO | May 19, 11:40 UTC | May 19, 12:10 UTC | 30m |
| 2026-05-18 | QDA917 | TAO → BKK | May 18, 15:25 UTC | May 19, 10:25 UTC | 18h 59m |
| 2026-05-18 | QDA917 | TAO → BKK | May 18, 14:50 UTC | May 19, 10:25 UTC | 19h 34m |
| 2026-05-18 | QDA925 | TAO → SGN | May 18, 10:25 UTC | May 18, 22:25 UTC | 11h 59m |
| 2026-05-17 | QDA920 | TAE → TAO | May 17, 13:25 UTC | May 17, 14:05 UTC | 40m |
| 2026-05-17 | QDA910 | NGO → TAO | May 17, 04:45 UTC | May 17, 12:01 UTC | 7h 16m |
| 2026-05-17 | QDA909 | TAO → NGO | May 17, 01:55 UTC | May 17, 03:25 UTC | 1h 30m |
| 2026-05-15 | QDA904 | - | May 15, 04:05 UTC | May 15, 05:25 UTC | 1h 20m |
| 2026-05-14 | QDA903 | - | May 14, 11:40 UTC | May 15, 03:00 UTC | 15h 20m |
| 2026-05-14 | QDA903 | - | May 14, 03:10 UTC | May 15, 03:00 UTC | 23h 50m |
| 2026-05-13 | QDA920 | TAE → TAO | May 13, 13:10 UTC | May 13, 13:50 UTC | 40m |
| 2026-05-13 | QDA910 | NGO → TAO | May 13, 04:45 UTC | May 13, 12:10 UTC | 7h 25m |
| 2026-05-12 | QDA909 | TAO → NGO | May 12, 12:15 UTC | May 13, 03:20 UTC | 15h 5m |
| 2026-05-12 | QDA909 | TAO → NGO | May 12, 03:50 UTC | May 13, 03:00 UTC | 23h 10m |
| 2026-05-11 | QDA923 | TAO → PEN | May 11, 21:55 UTC | May 12, 13:20 UTC | 15h 25m |
| 2026-05-11 | QDA923 | TAO → PEN | May 11, 16:20 UTC | May 12, 13:20 UTC | 21h 1m |
| 2026-05-08 | QDA930 | - | May 8, 17:25 UTC | May 9, 12:50 UTC | 19h 25m |
| 2026-05-08 | QDA929 | - | May 8, 15:40 UTC | May 8, 15:50 UTC | 10m |
| 2026-05-08 | QDA929 | - | May 8, 11:25 UTC | May 8, 12:34 UTC | 1h 10m |
| 2026-05-07 | QDA9786 | - | May 7, 12:05 UTC | May 7, 12:15 UTC | 10m |
| 2026-05-07 | QDA9785 | - | May 7, 09:55 UTC | May 7, 10:35 UTC | 40m |
| 2026-05-06 | QDA6241 | CGO → CGQ | May 6, 05:15 UTC | May 6, 05:30 UTC | 15m |
| 2026-05-03 | QDA926 | SGN → TAO | May 3, 14:50 UTC | May 3, 22:45 UTC | 7h 55m |
| 2026-05-02 | QDA918 | BKK → TAO | May 2, 11:45 UTC | May 2, 12:15 UTC | 30m |
| 2026-05-02 | QDA917 | TAO → BKK | May 2, 09:45 UTC | May 2, 10:25 UTC | 40m |
| 2026-04-28 | QDA918 | BKK → TAO | Apr 28, 12:00 UTC | Apr 28, 12:20 UTC | 20m |
| 2026-04-28 | QDA917 | TAO → BKK | Apr 28, 10:00 UTC | Apr 28, 10:35 UTC | 35m |
| 2026-04-25 | QDA6063 | HRB → CSX | Apr 25, 05:00 UTC | Apr 25, 11:10 UTC | 6h 10m |
| 2026-04-19 | QDA930 | - | Apr 19, 17:55 UTC | Apr 19, 22:00 UTC | 4h 5m |
| 2026-04-19 | QDA929 | - | Apr 19, 15:55 UTC | Apr 19, 16:10 UTC | 15m |
| 2026-04-19 | QDA929 | - | Apr 19, 11:55 UTC | Apr 19, 14:55 UTC | 3h 0m |
| 2026-04-16 | QDA918 | BKK → TAO | Apr 16, 12:29 UTC | Apr 16, 12:55 UTC | 25m |
| 2026-04-16 | QDA917 | TAO → BKK | Apr 16, 10:19 UTC | Apr 16, 10:54 UTC | 35m |
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-30A1 page for operator, model, and routing details .