sensors Mode-S transponder

780B99

ICAO 24-bit transponder address · allocated to China

Currently assigned to B-1905 · BOEING 737-800

Hex
780B99
Octal
36005631
Decimal
7,867,289
Country
CN
Tail
B-1905
Type
B738
No current signal · last broadcast 5d ago
Flights observed
69
Distinct callsigns
16
Country
CN
Last broadcast
5d ago

Last known position

Most recent position reported by Mode-S 780B99.

Country allocation

The ICAO 24-bit address 780B99 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
FZA6573 Fuzhou Airlines 15 2026-06-10
FZA6636 - 9 2026-06-27
FZA6635 - 8 2026-06-27
FZA6718 - 6 2026-07-05
FZA6574 Fuzhou Airlines 6 2026-06-08
FZA6531 - 6 2026-06-26
FZA6768 - 4 2026-06-29
FZA6767 - 4 2026-06-22
FZA6720 Fuzhou Airlines 2 2026-06-20
FZA6717 - 2 2026-07-09
FZA6665 Fuzhou Airlines 1 2026-04-18
FZA6648 - 1 2026-06-30
FZA6632 Fuzhou Airlines 1 2026-04-24
FZA6597 - 1 2026-06-14
FZA6538 - 1 2026-07-01
FZA6532 - 1 2026-06-15

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-09 FZA6717 - Jul 9, 23:55 UTCJul 10, 00:30 UTC35m
2026-07-05 FZA6718 - Jul 5, 08:05 UTCJul 5, 12:10 UTC4h 5m
2026-07-01 FZA6538 - Jul 1, 23:25 UTCJul 2, 00:20 UTC55m
2026-06-30 FZA6648 - Jun 30, 02:40 UTCJun 30, 02:55 UTC15m
2026-06-29 FZA6768 - Jun 29, 02:35 UTCJun 29, 15:14 UTC12h 40m
2026-06-28 FZA6768 - Jun 28, 17:00 UTCJun 29, 15:14 UTC22h 15m
2026-06-27 FZA6636 - Jun 27, 15:14 UTCJun 28, 11:09 UTC19h 55m
2026-06-27 FZA6636 - Jun 27, 09:09 UTCJun 28, 08:14 UTC23h 5m
2026-06-27 FZA6635 - Jun 27, 06:30 UTCJun 27, 06:50 UTC20m
2026-06-27 FZA6635 - Jun 27, 02:09 UTCJun 27, 02:20 UTC10m
2026-06-26 FZA6531 - Jun 26, 07:05 UTCJun 26, 16:30 UTC9h 25m
2026-06-25 FZA6531 - Jun 25, 13:29 UTCJun 26, 10:35 UTC21h 5m
2026-06-25 FZA6636 - Jun 25, 09:20 UTCJun 26, 07:30 UTC22h 10m
2026-06-25 FZA6636 - Jun 25, 06:40 UTCJun 25, 13:45 UTC7h 5m
2026-06-25 FZA6635 - Jun 25, 02:25 UTCJun 25, 02:35 UTC10m
2026-06-24 FZA6768 - Jun 24, 02:24 UTCJun 24, 14:15 UTC11h 50m
2026-06-23 FZA6636 XNT → HRB Jun 23, 13:34 UTCJun 24, 10:25 UTC20h 50m
2026-06-23 FZA6636 XNT → HRB Jun 23, 09:45 UTCJun 24, 07:10 UTC21h 25m
2026-06-23 FZA6636 XNT → HRB Jun 23, 06:39 UTCJun 24, 02:40 UTC20h 0m
2026-06-23 FZA6635 - Jun 23, 02:34 UTCJun 23, 02:45 UTC10m
2026-06-22 FZA6767 - Jun 22, 02:19 UTCJun 22, 14:19 UTC12h 0m
2026-06-20 FZA6720 CGQ → FOC Jun 20, 11:34 UTCJun 20, 12:19 UTC45m
2026-06-17 FZA6531 - Jun 17, 06:25 UTCJun 17, 10:35 UTC4h 10m
2026-06-15 FZA6532 - Jun 15, 11:24 UTCJun 15, 11:39 UTC15m
2026-06-15 FZA6531 FOC → HAK Jun 15, 07:10 UTCJun 15, 10:50 UTC3h 40m
2026-06-14 FZA6597 - Jun 14, 06:25 UTCJun 14, 06:45 UTC20m
2026-06-13 FZA6635 HRB → XNT Jun 13, 06:45 UTCJun 13, 07:05 UTC20m
2026-06-13 FZA6635 HRB → XNT Jun 13, 02:20 UTCJun 13, 02:30 UTC10m
2026-06-12 FZA6767 - Jun 12, 01:15 UTCJun 12, 14:10 UTC12h 55m
2026-06-11 FZA6767 - Jun 11, 12:50 UTCJun 12, 10:20 UTC21h 30m
2026-06-10 FZA6573 FOC → NNG Jun 10, 03:30 UTCJun 10, 07:30 UTC4h 0m
2026-06-08 FZA6574 NNG → FOC Jun 8, 06:20 UTCJun 8, 07:10 UTC50m
2026-06-08 FZA6573 FOC → NNG Jun 8, 03:50 UTCJun 8, 04:10 UTC20m
2026-06-06 FZA6720 CGQ → FOC Jun 6, 11:25 UTCJun 6, 12:10 UTC45m
2026-06-05 FZA6718 HRB → HSN Jun 5, 11:25 UTCJun 5, 12:00 UTC35m
2026-06-04 FZA6718 HRB → HSN Jun 4, 11:45 UTCJun 4, 12:35 UTC50m
2026-06-01 - - Jun 1, 15:00 UTCJun 1, 15:10 UTC10m
2026-05-30 FZA6718 HRB → HSN May 30, 11:45 UTCMay 30, 12:00 UTC15m
2026-05-27 FZA6718 HRB → HSN May 27, 11:25 UTCMay 27, 12:10 UTC45m
2026-05-25 FZA6717 HSN → HRB May 25, 23:45 UTCMay 25, 23:54 UTC10m
2026-05-23 FZA6718 HRB → HSN May 23, 11:15 UTCMay 23, 11:50 UTC35m
2026-05-20 FZA6573 FOC → NNG May 20, 03:30 UTCMay 20, 07:30 UTC4h 1m
2026-05-19 FZA6574 NNG → FOC May 19, 06:10 UTCMay 19, 06:25 UTC15m
2026-05-19 FZA6573 FOC → NNG May 19, 02:55 UTCMay 19, 03:20 UTC25m
2026-05-14 FZA6573 FOC → NNG May 14, 03:00 UTCMay 14, 03:25 UTC25m
2026-05-13 FZA6573 FOC → NNG May 13, 04:20 UTCMay 14, 03:25 UTC23h 5m
2026-05-10 FZA6573 FOC → NNG May 10, 03:40 UTCMay 10, 08:00 UTC4h 20m
2026-05-09 FZA6574 NNG → FOC May 9, 06:20 UTCMay 9, 06:30 UTC10m
2026-05-09 FZA6573 FOC → NNG May 9, 03:00 UTCMay 9, 03:25 UTC25m
2026-05-06 FZA6531 FOC → HAK May 6, 12:55 UTCMay 7, 07:00 UTC18h 4m

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-1905 page for operator, model, and routing details .

Mode-S 780B99 frequently asked

What is Mode-S code 780B99?
780B99 is an ICAO 24-bit transponder address. Allocated to China. Assigned to B-1905.
Where is Mode-S 780B99 registered?
Mode-S code 780B99 is allocated to China (CN). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 780B99 broadcasting right now?
No active broadcast right now. Last signal was 5d ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 780B99, octal 36005631, decimal 7,867,289.
What flights does 780B99 operate?
Mode-S 780B99 has broadcast 16 distinct callsigns, including FZA6573, FZA6636, FZA6635, FZA6718, FZA6574.