Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

7820F7

ICAO 24-bit transponder address · allocated to China

Currently assigned to B-225R · BOEING 737 MAX 8

Hex
7820F7
Octal
36020367
Decimal
7,872,759
Country
CN
Tail
B-225R
Type
B38M
No current signal · last broadcast 13h ago
Flights observed
144
Distinct callsigns
11
Country
CN
Last broadcast
13h ago

Last known position

Most recent position reported by Mode-S 7820F7.

Country allocation

The ICAO 24-bit address 7820F7 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
CHH7048 - 46 2026-07-13
CHH423 Hainan Airlines 37 2026-05-11
CHH7047 - 20 2026-07-14
CHH424 Hainan Airlines 20 2026-05-11
CHH7022 Hainan Airlines 7 2026-06-28
CHH7021 - 5 2026-06-27
CHH7061 - 2 2026-07-12
CHH7063 Hainan Airlines 1 2026-06-06
CHH7045 Hainan Airlines 1 2026-06-07
CHH7037 - 1 2026-06-25
CHH7032 - 1 2026-06-25

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-14 CHH7047 - Jul 14, 00:05 UTCJul 14, 00:25 UTC20m
2026-07-13 CHH7048 - Jul 13, 12:05 UTCJul 13, 12:45 UTC40m
2026-07-13 CHH7048 - Jul 13, 00:15 UTCJul 13, 08:30 UTC8h 15m
2026-07-12 CHH7061 - Jul 12, 06:15 UTCJul 13, 00:25 UTC18h 10m
2026-07-11 CHH7048 - Jul 11, 07:50 UTCJul 11, 12:40 UTC4h 50m
2026-07-10 CHH7048 - Jul 10, 12:10 UTCJul 11, 01:05 UTC12h 56m
2026-07-09 CHH7048 - Jul 9, 13:05 UTCJul 10, 00:35 UTC11h 30m
2026-07-09 CHH7047 - Jul 9, 04:00 UTCJul 9, 08:55 UTC4h 55m
2026-07-08 CHH7048 - Jul 8, 12:35 UTCJul 9, 00:55 UTC12h 20m
2026-07-07 CHH7048 - Jul 7, 16:10 UTCJul 8, 09:10 UTC17h 0m
2026-07-07 CHH7048 - Jul 7, 12:35 UTCJul 7, 13:05 UTC30m
2026-07-06 CHH7047 - Jul 6, 07:30 UTCJul 7, 00:30 UTC17h 0m
2026-07-05 CHH7048 - Jul 5, 12:10 UTCJul 6, 07:45 UTC19h 35m
2026-07-05 CHH7048 - Jul 5, 08:15 UTCJul 6, 07:45 UTC23h 30m
2026-07-04 CHH7048 - Jul 4, 08:25 UTCJul 5, 00:15 UTC15h 50m
2026-07-04 CHH7048 - Jul 4, 03:10 UTCJul 5, 00:15 UTC21h 5m
2026-07-04 CHH7048 - Jul 4, 00:05 UTCJul 4, 15:05 UTC15h 0m
2026-07-03 CHH7048 - Jul 3, 00:25 UTCJul 3, 13:40 UTC13h 15m
2026-07-02 CHH7048 - Jul 2, 08:20 UTCJul 3, 00:25 UTC16h 5m
2026-07-02 CHH7048 - Jul 2, 00:05 UTCJul 2, 12:40 UTC12h 35m
2026-07-01 CHH7048 - Jul 1, 13:00 UTCJul 2, 08:20 UTC19h 20m
2026-07-01 CHH7048 - Jul 1, 00:15 UTCJul 1, 13:25 UTC13h 10m
2026-06-30 CHH7047 - Jun 30, 06:20 UTCJul 1, 00:35 UTC18h 15m
2026-06-28 CHH7022 CAN → SYX Jun 28, 01:25 UTCJun 28, 01:34 UTC10m
2026-06-27 CHH7021 - Jun 27, 23:19 UTCJun 27, 23:39 UTC20m
2026-06-26 CHH7022 CAN → SYX Jun 26, 01:10 UTCJun 26, 01:20 UTC10m
2026-06-25 CHH7037 - Jun 25, 10:30 UTCJun 25, 15:34 UTC5h 5m
2026-06-25 CHH7032 - Jun 25, 00:55 UTCJun 25, 06:44 UTC5h 50m
2026-06-23 CHH7022 CAN → SYX Jun 23, 01:50 UTCJun 23, 01:59 UTC10m
2026-06-22 CHH7021 - Jun 22, 23:20 UTCJun 22, 23:29 UTC10m
2026-06-21 CHH7022 CAN → SYX Jun 21, 01:19 UTCJun 21, 01:35 UTC15m
2026-06-20 CHH7021 - Jun 20, 23:14 UTCJun 20, 23:29 UTC15m
2026-06-20 CHH7022 CAN → SYX Jun 20, 01:09 UTCJun 20, 01:19 UTC10m
2026-06-19 CHH7021 - Jun 19, 23:09 UTCJun 19, 23:25 UTC15m
2026-06-18 CHH7022 CAN → SYX Jun 18, 04:00 UTCJun 18, 04:10 UTC10m
2026-06-17 CHH7022 CAN → SYX Jun 17, 01:05 UTCJun 17, 01:15 UTC10m
2026-06-16 CHH7021 - Jun 16, 23:10 UTCJun 16, 23:30 UTC20m
2026-06-15 CHH7048 - Jun 15, 12:49 UTCJun 15, 13:10 UTC20m
2026-06-15 CHH7048 - Jun 15, 09:54 UTCJun 15, 10:24 UTC30m
2026-06-14 CHH7047 - Jun 14, 14:40 UTCJun 15, 08:20 UTC17h 39m
2026-06-13 CHH7048 - Jun 13, 12:30 UTCJun 13, 12:50 UTC20m
2026-06-12 CHH7047 - Jun 12, 23:55 UTCJun 13, 00:05 UTC10m
2026-06-11 CHH7048 - Jun 11, 12:25 UTCJun 12, 07:30 UTC19h 6m
2026-06-11 - - Jun 11, 02:45 UTCJun 11, 03:15 UTC30m
2026-06-10 CHH7047 - Jun 10, 06:20 UTCJun 11, 00:20 UTC18h 0m
2026-06-09 CHH7048 - Jun 9, 03:35 UTCJun 9, 13:15 UTC9h 40m
2026-06-08 CHH7047 - Jun 8, 06:45 UTCJun 9, 00:20 UTC17h 35m
2026-06-07 CHH7045 ZUH → TYN Jun 7, 06:15 UTCJun 7, 06:25 UTC10m
2026-06-06 CHH7063 HAK → WUH Jun 6, 05:10 UTCJun 6, 05:20 UTC10m
2026-06-03 CHH7061 HAK → HGH Jun 3, 06:10 UTCJun 3, 14:50 UTC8h 40m

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

Mode-S 7820F7 frequently asked

What is Mode-S code 7820F7?
7820F7 is an ICAO 24-bit transponder address. Allocated to China. Assigned to B-225R.
Where is Mode-S 7820F7 registered?
Mode-S code 7820F7 is allocated to China (CN). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 7820F7 broadcasting right now?
No active broadcast right now. Last signal was 13h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 7820F7, octal 36020367, decimal 7,872,759.
What flights does 7820F7 operate?
Mode-S 7820F7 has broadcast 11 distinct callsigns, including CHH7048, CHH423, CHH7047, CHH424, CHH7022.