sensors Mode-S transponder
780B96
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-1906 · BOEING 737-800
- Hex
- 780B96
- Octal
- 36005626
- Decimal
- 7,867,286
- Country
- CN
- Tail
- B-1906
- Type
- B738
- Flights observed
- 44
- Distinct callsigns
- 18
- Country
- CN
- Last broadcast
- 6h ago
Last known position
Country allocation
The ICAO 24-bit address 780B96 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 18 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| FZA6573 | - | 7 | 2026-07-01 |
| FZA6718 | Fuzhou Airlines | 6 | 2026-06-09 |
| FZA6658 | - | 5 | 2026-07-18 |
| FZA6531 | - | 5 | 2026-07-10 |
| FZA6720 | Fuzhou Airlines | 3 | 2026-07-02 |
| FZA6768 | - | 2 | 2026-07-08 |
| FZA6767 | - | 2 | 2026-07-08 |
| FZA6741 | Fuzhou Airlines | 2 | 2026-07-17 |
| FZA6636 | Fuzhou Airlines | 2 | 2026-04-21 |
| FZA6532 | - | 2 | 2026-07-10 |
| FZA6747 | - | 1 | 2026-06-20 |
| FZA6742 | - | 1 | 2026-07-15 |
| FZA6717 | Fuzhou Airlines | 1 | 2026-06-08 |
| FZA6666 | Fuzhou Airlines | 1 | 2026-04-29 |
| FZA6620 | Fuzhou Airlines | 1 | 2026-05-24 |
| FZA6598 | - | 1 | 2026-07-13 |
| FZA6538 | - | 1 | 2026-07-01 |
| FZA6512 | Fuzhou Airlines | 1 | 2026-06-20 |
Recent flights last 44
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-18 | FZA6658 | - | Jul 18, 13:50 UTC | Jul 18, 14:05 UTC | 15m |
| 2026-07-17 | FZA6741 | FOC → SYX | Jul 17, 06:20 UTC | Jul 17, 10:20 UTC | 4h 0m |
| 2026-07-16 | FZA6741 | FOC → SYX | Jul 16, 14:10 UTC | Jul 17, 10:20 UTC | 20h 10m |
| 2026-07-15 | FZA6742 | - | Jul 15, 06:05 UTC | Jul 15, 11:15 UTC | 5h 10m |
| 2026-07-14 | FZA6658 | - | Jul 14, 14:05 UTC | Jul 14, 14:20 UTC | 15m |
| 2026-07-13 | FZA6598 | - | Jul 13, 02:10 UTC | Jul 13, 14:15 UTC | 12h 5m |
| 2026-07-11 | FZA6658 | - | Jul 11, 15:00 UTC | Jul 11, 15:10 UTC | 10m |
| 2026-07-10 | FZA6658 | - | Jul 10, 15:45 UTC | Jul 11, 15:10 UTC | 23h 26m |
| 2026-07-10 | FZA6532 | - | Jul 10, 09:40 UTC | Jul 10, 09:55 UTC | 15m |
| 2026-07-10 | FZA6531 | - | Jul 10, 06:35 UTC | Jul 10, 07:15 UTC | 40m |
| 2026-07-09 | FZA6658 | - | Jul 9, 14:00 UTC | Jul 9, 14:15 UTC | 15m |
| 2026-07-08 | FZA6768 | - | Jul 8, 10:35 UTC | Jul 8, 15:30 UTC | 4h 55m |
| 2026-07-08 | FZA6767 | - | Jul 8, 02:15 UTC | Jul 8, 08:25 UTC | 6h 10m |
| 2026-07-06 | FZA6531 | - | Jul 6, 07:55 UTC | Jul 6, 17:15 UTC | 9h 20m |
| 2026-07-05 | FZA6531 | - | Jul 5, 12:35 UTC | Jul 6, 11:20 UTC | 22h 45m |
| 2026-07-02 | FZA6720 | CGQ → FOC | Jul 2, 11:20 UTC | Jul 2, 12:05 UTC | 45m |
| 2026-07-01 | FZA6573 | - | Jul 1, 03:45 UTC | Jul 1, 10:10 UTC | 6h 25m |
| 2026-07-01 | FZA6538 | - | Jul 1, 00:15 UTC | Jul 1, 00:50 UTC | 35m |
| 2026-06-23 | FZA6531 | - | Jun 23, 01:54 UTC | Jun 23, 05:04 UTC | 3h 10m |
| 2026-06-22 | FZA6573 | - | Jun 22, 02:50 UTC | Jun 22, 07:00 UTC | 4h 10m |
| 2026-06-21 | FZA6573 | - | Jun 21, 03:44 UTC | Jun 21, 06:55 UTC | 3h 10m |
| 2026-06-20 | FZA6512 | KWE → FOC | Jun 20, 15:34 UTC | Jun 20, 15:49 UTC | 15m |
| 2026-06-20 | FZA6747 | - | Jun 20, 04:14 UTC | Jun 20, 04:29 UTC | 15m |
| 2026-06-11 | FZA6720 | CGQ → FOC | Jun 11, 11:35 UTC | Jun 11, 12:15 UTC | 40m |
| 2026-06-09 | FZA6718 | HRB → HSN | Jun 9, 11:15 UTC | Jun 9, 11:50 UTC | 35m |
| 2026-06-08 | FZA6717 | HSN → HRB | Jun 8, 23:50 UTC | Jun 9, 00:20 UTC | 30m |
| 2026-06-06 | FZA6718 | HRB → HSN | Jun 6, 14:59 UTC | Jun 6, 15:34 UTC | 35m |
| 2026-06-06 | FZA6718 | HRB → HSN | Jun 6, 11:30 UTC | Jun 6, 12:20 UTC | 50m |
| 2026-06-01 | FZA6573 | FOC → NNG | Jun 1, 03:05 UTC | Jun 1, 07:30 UTC | 4h 25m |
| 2026-05-25 | FZA6573 | FOC → NNG | May 25, 03:25 UTC | May 25, 07:20 UTC | 3h 55m |
| 2026-05-24 | FZA6620 | TAO → FOC | May 24, 12:40 UTC | May 24, 12:50 UTC | 10m |
| 2026-05-23 | FZA6720 | CGQ → FOC | May 23, 11:20 UTC | May 23, 12:05 UTC | 45m |
| 2026-05-22 | FZA6718 | HRB → HSN | May 22, 11:25 UTC | May 22, 12:15 UTC | 50m |
| 2026-05-13 | FZA6718 | HRB → HSN | May 13, 15:20 UTC | May 13, 15:40 UTC | 20m |
| 2026-05-13 | FZA6718 | HRB → HSN | May 13, 11:25 UTC | May 13, 12:10 UTC | 45m |
| 2026-04-29 | FZA6666 | PEK → FOC | Apr 29, 14:25 UTC | Apr 29, 14:40 UTC | 15m |
| 2026-04-28 | FZA6573 | FOC → NNG | Apr 28, 02:50 UTC | Apr 28, 03:15 UTC | 25m |
| 2026-04-24 | FZA6573 | FOC → NNG | Apr 24, 01:35 UTC | Apr 24, 02:00 UTC | 25m |
| 2026-04-21 | FZA6636 | XNT → HRB | Apr 21, 13:20 UTC | Apr 21, 13:35 UTC | 15m |
| 2026-04-20 | FZA6532 | HAK → FOC | Apr 20, 06:55 UTC | Apr 20, 07:35 UTC | 40m |
| 2026-04-20 | FZA6531 | FOC → HAK | Apr 20, 03:50 UTC | Apr 20, 04:15 UTC | 25m |
| 2026-04-18 | FZA6636 | XNT → HRB | Apr 18, 13:40 UTC | Apr 18, 13:50 UTC | 10m |
| 2026-04-15 | FZA6768 | - | Apr 15, 10:10 UTC | Apr 15, 10:20 UTC | 10m |
| 2026-04-15 | FZA6767 | - | Apr 15, 05:30 UTC | Apr 15, 05:55 UTC | 25m |
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-1906 page for operator, model, and routing details .