sensors Mode-S transponder
780F5A
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-7395 · BOEING 737-800
- Hex
- 780F5A
- Octal
- 36007532
- Decimal
- 7,868,250
- Country
- CN
- Tail
- B-7395
- Type
- B738
- Flights observed
- 37
- Distinct callsigns
- 11
- Country
- CN
- Last broadcast
- 16h ago
Current position
Country allocation
The ICAO 24-bit address 780F5A 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 11 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| FZA6767 | - | 14 | 2026-05-28 |
| FZA6652 | Fuzhou Airlines | 5 | 2026-05-20 |
| FZA6587 | - | 5 | 2026-04-26 |
| FZA6648 | - | 3 | 2026-05-07 |
| FZA6768 | - | 2 | 2026-05-29 |
| FZA6531 | Fuzhou Airlines | 2 | 2026-05-04 |
| FZA6510 | Fuzhou Airlines | 2 | 2026-05-13 |
| FZA6651 | Fuzhou Airlines | 1 | 2026-04-13 |
| FZA6647 | - | 1 | 2026-05-07 |
| FZA6573 | Fuzhou Airlines | 1 | 2026-05-11 |
| FZA6532 | Fuzhou Airlines | 1 | 2026-05-04 |
Recent flights last 37
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | FZA6768 | - | May 29, 01:30 UTC | May 29, 13:55 UTC | 12h 25m |
| 2026-05-28 | FZA6767 | - | May 28, 13:15 UTC | May 29, 09:50 UTC | 20h 35m |
| 2026-05-20 | FZA6652 | SZX → KMG | May 20, 10:40 UTC | May 20, 11:00 UTC | 20m |
| 2026-05-13 | FZA6510 | KMG → FOC | May 13, 15:00 UTC | May 13, 15:50 UTC | 50m |
| 2026-05-13 | FZA6652 | SZX → KMG | May 13, 10:25 UTC | May 13, 10:40 UTC | 15m |
| 2026-05-11 | FZA6573 | FOC → NNG | May 11, 03:30 UTC | May 11, 06:55 UTC | 3h 25m |
| 2026-05-07 | FZA6647 | - | May 7, 12:40 UTC | May 7, 12:55 UTC | 15m |
| 2026-05-07 | FZA6648 | - | May 7, 02:45 UTC | May 7, 02:55 UTC | 10m |
| 2026-05-06 | FZA6767 | - | May 6, 00:10 UTC | May 6, 13:35 UTC | 13h 25m |
| 2026-05-05 | FZA6767 | - | May 5, 12:35 UTC | May 6, 09:20 UTC | 20h 45m |
| 2026-05-05 | FZA6767 | - | May 5, 12:25 UTC | May 6, 09:20 UTC | 20h 55m |
| 2026-05-04 | FZA6532 | HAK → FOC | May 4, 15:50 UTC | May 5, 12:40 UTC | 20h 51m |
| 2026-05-04 | FZA6531 | FOC → HAK | May 4, 13:10 UTC | May 5, 12:30 UTC | 23h 21m |
| 2026-05-03 | FZA6531 | FOC → HAK | May 3, 15:05 UTC | May 4, 13:35 UTC | 22h 30m |
| 2026-05-03 | FZA6652 | SZX → KMG | May 3, 10:20 UTC | May 3, 10:30 UTC | 10m |
| 2026-05-01 | FZA6652 | SZX → KMG | May 1, 10:25 UTC | May 1, 10:40 UTC | 15m |
| 2026-04-28 | FZA6648 | - | Apr 28, 02:20 UTC | Apr 28, 02:30 UTC | 10m |
| 2026-04-27 | FZA6767 | - | Apr 27, 01:00 UTC | Apr 27, 14:15 UTC | 13h 15m |
| 2026-04-26 | FZA6767 | - | Apr 26, 13:35 UTC | Apr 27, 10:15 UTC | 20h 40m |
| 2026-04-26 | FZA6767 | - | Apr 26, 09:45 UTC | Apr 27, 05:35 UTC | 19h 50m |
| 2026-04-26 | FZA6587 | - | Apr 26, 06:00 UTC | Apr 27, 01:10 UTC | 19h 10m |
| 2026-04-26 | FZA6587 | - | Apr 26, 01:45 UTC | Apr 26, 14:30 UTC | 12h 45m |
| 2026-04-25 | FZA6587 | - | Apr 25, 12:40 UTC | Apr 26, 09:55 UTC | 21h 15m |
| 2026-04-24 | FZA6767 | - | Apr 24, 05:20 UTC | Apr 24, 14:05 UTC | 8h 45m |
| 2026-04-24 | FZA6767 | - | Apr 24, 01:20 UTC | Apr 24, 01:30 UTC | 10m |
| 2026-04-23 | FZA6648 | - | Apr 23, 02:40 UTC | Apr 23, 02:50 UTC | 10m |
| 2026-04-22 | FZA6768 | - | Apr 22, 01:10 UTC | Apr 22, 13:30 UTC | 12h 20m |
| 2026-04-21 | FZA6767 | - | Apr 21, 12:15 UTC | Apr 22, 09:45 UTC | 21h 30m |
| 2026-04-20 | FZA6767 | - | Apr 20, 01:05 UTC | Apr 20, 13:40 UTC | 12h 35m |
| 2026-04-19 | FZA6767 | - | Apr 19, 14:20 UTC | Apr 20, 09:40 UTC | 19h 20m |
| 2026-04-19 | FZA6767 | - | Apr 19, 09:45 UTC | Apr 20, 05:45 UTC | 20h 0m |
| 2026-04-19 | FZA6587 | - | Apr 19, 05:50 UTC | Apr 20, 01:15 UTC | 19h 25m |
| 2026-04-19 | FZA6587 | - | Apr 19, 01:05 UTC | Apr 19, 14:20 UTC | 13h 15m |
| 2026-04-17 | FZA6767 | - | Apr 17, 05:25 UTC | Apr 17, 05:35 UTC | 10m |
| 2026-04-13 | FZA6510 | - | Apr 13, 15:10 UTC | Apr 13, 15:25 UTC | 15m |
| 2026-04-13 | FZA6652 | - | Apr 13, 10:15 UTC | Apr 13, 10:35 UTC | 20m |
| 2026-04-13 | FZA6651 | KMG → SZX | Apr 13, 07:00 UTC | Apr 13, 07:10 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-7395 page for operator, model, and routing details .