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
- Flights observed
- 91
- Distinct callsigns
- 4
- Country
- CN
- Last broadcast
- 5h ago
Last known position
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 4 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| CHH423 | Hainan Airlines | 37 | 2026-05-11 |
| CHH7048 | - | 21 | 2026-05-28 |
| CHH424 | Hainan Airlines | 20 | 2026-05-11 |
| CHH7047 | - | 11 | 2026-05-30 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | CHH7047 | - | May 30, 03:00 UTC | May 30, 03:10 UTC | 10m |
| 2026-05-29 | CHH7047 | - | May 29, 13:45 UTC | May 30, 00:25 UTC | 10h 40m |
| 2026-05-28 | CHH7048 | - | May 28, 12:30 UTC | May 29, 00:30 UTC | 12h 0m |
| 2026-05-28 | CHH7048 | - | May 28, 10:00 UTC | May 28, 10:15 UTC | 15m |
| 2026-05-28 | CHH7047 | - | May 28, 00:10 UTC | May 28, 00:30 UTC | 20m |
| 2026-05-27 | CHH7048 | - | May 27, 12:30 UTC | May 27, 12:50 UTC | 20m |
| 2026-05-27 | CHH7048 | - | May 27, 09:40 UTC | May 27, 10:00 UTC | 20m |
| 2026-05-27 | CHH7047 | - | May 27, 00:04 UTC | May 27, 08:15 UTC | 8h 10m |
| 2026-05-26 | CHH7048 | - | May 26, 12:24 UTC | May 27, 08:15 UTC | 19h 50m |
| 2026-05-25 | CHH7048 | - | May 25, 07:35 UTC | May 26, 00:35 UTC | 16h 59m |
| 2026-05-24 | CHH7048 | - | May 24, 23:30 UTC | May 25, 12:45 UTC | 13h 15m |
| 2026-05-24 | CHH7048 | - | May 24, 12:20 UTC | May 24, 12:45 UTC | 25m |
| 2026-05-23 | CHH7047 | - | May 23, 23:50 UTC | May 24, 08:15 UTC | 8h 25m |
| 2026-05-23 | CHH7048 | - | May 23, 12:30 UTC | May 24, 08:15 UTC | 19h 45m |
| 2026-05-23 | - | - | May 23, 09:35 UTC | May 23, 09:55 UTC | 20m |
| 2026-05-22 | CHH7048 | - | May 22, 12:25 UTC | May 23, 00:20 UTC | 11h 55m |
| 2026-05-22 | CHH7047 | - | May 22, 00:05 UTC | May 22, 00:25 UTC | 20m |
| 2026-05-21 | CHH7048 | - | May 21, 08:20 UTC | May 21, 12:50 UTC | 4h 30m |
| 2026-05-20 | CHH7048 | - | May 20, 08:15 UTC | May 21, 00:35 UTC | 16h 20m |
| 2026-05-20 | CHH7048 | - | May 20, 00:00 UTC | May 20, 12:40 UTC | 12h 41m |
| 2026-05-19 | CHH7048 | - | May 19, 12:25 UTC | May 20, 08:30 UTC | 20h 6m |
| 2026-05-19 | CHH7048 | - | May 19, 07:45 UTC | May 20, 00:10 UTC | 16h 25m |
| 2026-05-18 | CHH7048 | - | May 18, 12:35 UTC | May 19, 00:25 UTC | 11h 49m |
| 2026-05-18 | CHH7047 | - | May 18, 03:10 UTC | May 18, 08:25 UTC | 5h 15m |
| 2026-05-17 | CHH7047 | - | May 17, 23:35 UTC | May 17, 23:55 UTC | 20m |
| 2026-05-17 | CHH7048 | - | May 17, 12:30 UTC | May 17, 12:50 UTC | 20m |
| 2026-05-17 | - | - | May 17, 09:55 UTC | May 17, 10:05 UTC | 10m |
| 2026-05-16 | CHH7048 | - | May 16, 07:41 UTC | May 17, 00:20 UTC | 16h 40m |
| 2026-05-15 | CHH7048 | - | May 15, 12:30 UTC | May 16, 00:55 UTC | 12h 24m |
| 2026-05-15 | CHH7048 | - | May 15, 09:30 UTC | May 15, 10:15 UTC | 45m |
| 2026-05-15 | CHH7047 | - | May 15, 00:00 UTC | May 15, 00:25 UTC | 25m |
| 2026-05-13 | CHH7048 | - | May 13, 12:35 UTC | May 13, 12:50 UTC | 15m |
| 2026-05-13 | CHH7047 | - | May 13, 00:00 UTC | May 13, 00:20 UTC | 20m |
| 2026-05-12 | CHH7047 | - | May 12, 04:25 UTC | May 13, 00:20 UTC | 19h 55m |
| 2026-05-11 | CHH424 | BKK → CKG | May 11, 04:35 UTC | May 11, 05:30 UTC | 55m |
| 2026-05-11 | CHH423 | CKG → BKK | May 11, 01:55 UTC | May 11, 02:55 UTC | 1h 0m |
| 2026-05-10 | CHH424 | BKK → CKG | May 10, 04:29 UTC | May 11, 02:55 UTC | 22h 25m |
| 2026-05-10 | CHH423 | CKG → BKK | May 10, 02:00 UTC | May 10, 02:55 UTC | 55m |
| 2026-05-09 | CHH423 | CKG → BKK | May 9, 04:35 UTC | May 10, 02:55 UTC | 22h 20m |
| 2026-05-09 | CHH423 | CKG → BKK | May 9, 02:00 UTC | May 9, 03:10 UTC | 1h 10m |
| 2026-05-08 | CHH423 | CKG → BKK | May 8, 04:34 UTC | May 9, 03:10 UTC | 22h 35m |
| 2026-05-08 | CHH423 | CKG → BKK | May 8, 01:59 UTC | May 8, 02:55 UTC | 55m |
| 2026-05-07 | CHH424 | BKK → CKG | May 7, 04:30 UTC | May 8, 02:55 UTC | 22h 25m |
| 2026-05-07 | CHH423 | CKG → BKK | May 7, 01:55 UTC | May 7, 02:55 UTC | 1h 0m |
| 2026-05-06 | CHH423 | CKG → BKK | May 6, 04:30 UTC | May 7, 02:55 UTC | 22h 24m |
| 2026-05-06 | CHH423 | CKG → BKK | May 6, 02:25 UTC | May 6, 03:00 UTC | 35m |
| 2026-05-05 | CHH423 | CKG → BKK | May 5, 05:05 UTC | May 6, 03:00 UTC | 21h 55m |
| 2026-05-05 | CHH423 | CKG → BKK | May 5, 02:15 UTC | May 5, 02:45 UTC | 30m |
| 2026-05-04 | CHH423 | CKG → BKK | May 4, 04:24 UTC | May 5, 02:45 UTC | 22h 21m |
| 2026-05-04 | CHH423 | CKG → BKK | May 4, 02:39 UTC | May 4, 03:09 UTC | 30m |
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 .