sensors Mode-S transponder
7809A0
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-5725 · BOEING 737-800
- Hex
- 7809A0
- Octal
- 36004640
- Decimal
- 7,866,784
- Country
- CN
- Tail
- B-5725
- Type
- B738
- Flights observed
- 64
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 9h ago
Last known position
Country allocation
The ICAO 24-bit address 7809A0 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 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| CDG4911 | - | 4 | 2026-07-16 |
| CDG4686 | - | 4 | 2026-07-02 |
| CDG4685 | - | 4 | 2026-07-02 |
| CDG4612 | Shandong Airlines | 4 | 2026-07-20 |
| CDG4912 | - | 3 | 2026-07-16 |
| CDG4883 | Shandong Airlines | 3 | 2026-06-12 |
| CDG4619 | - | 3 | 2026-06-12 |
| CDG4611 | - | 3 | 2026-07-20 |
| CDG7948 | - | 2 | 2026-06-29 |
| CDG7941 | Shandong Airlines | 2 | 2026-05-29 |
| CDG4682 | - | 2 | 2026-06-22 |
| CDG4681 | - | 2 | 2026-06-22 |
| CDG4642 | - | 2 | 2026-07-16 |
| CDG4620 | Shandong Airlines | 2 | 2026-05-24 |
| CDG4614 | - | 2 | 2026-06-17 |
| CDG4086 | - | 2 | 2026-06-16 |
| CDG4085 | - | 2 | 2026-06-16 |
| CDG8833 | Shandong Airlines | 1 | 2026-05-09 |
| CDG7630 | Shandong Airlines | 1 | 2026-05-12 |
| CDG7629 | Shandong Airlines | 1 | 2026-05-12 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-20 | CDG4612 | ICN → TAO | Jul 20, 05:55 UTC | Jul 20, 06:25 UTC | 30m |
| 2026-07-20 | CDG4611 | - | Jul 20, 03:15 UTC | Jul 20, 03:40 UTC | 25m |
| 2026-07-16 | CDG4912 | - | Jul 16, 11:34 UTC | Jul 16, 12:14 UTC | 40m |
| 2026-07-16 | CDG4911 | - | Jul 16, 09:30 UTC | Jul 16, 09:45 UTC | 15m |
| 2026-07-16 | CDG4642 | - | Jul 16, 02:00 UTC | Jul 16, 02:10 UTC | 10m |
| 2026-07-07 | CDG4910 | - | Jul 7, 06:50 UTC | Jul 7, 07:00 UTC | 10m |
| 2026-07-02 | CDG4686 | - | Jul 2, 13:50 UTC | Jul 2, 14:05 UTC | 15m |
| 2026-07-02 | CDG4685 | - | Jul 2, 11:00 UTC | Jul 2, 11:20 UTC | 20m |
| 2026-07-02 | CDG4612 | - | Jul 2, 05:20 UTC | Jul 2, 05:45 UTC | 25m |
| 2026-07-02 | CDG4611 | - | Jul 2, 03:20 UTC | Jul 2, 03:40 UTC | 20m |
| 2026-06-29 | CDG7948 | - | Jun 29, 10:34 UTC | Jun 29, 10:44 UTC | 10m |
| 2026-06-29 | CDG7948 | - | Jun 29, 06:19 UTC | Jun 29, 06:34 UTC | 15m |
| 2026-06-25 | CDG7608 | - | Jun 25, 12:25 UTC | Jun 25, 12:35 UTC | 10m |
| 2026-06-25 | CDG1158 | - | Jun 25, 07:49 UTC | Jun 25, 07:59 UTC | 10m |
| 2026-06-25 | CDG1157 | - | Jun 25, 03:24 UTC | Jun 25, 03:40 UTC | 15m |
| 2026-06-24 | CDG2112 | - | Jun 24, 09:34 UTC | Jun 24, 09:45 UTC | 10m |
| 2026-06-22 | CDG4682 | - | Jun 22, 06:29 UTC | Jun 22, 06:39 UTC | 10m |
| 2026-06-22 | CDG4681 | - | Jun 22, 04:19 UTC | Jun 22, 04:40 UTC | 20m |
| 2026-06-17 | CDG4614 | - | Jun 17, 06:30 UTC | Jun 17, 07:00 UTC | 30m |
| 2026-06-17 | CDG4613 | - | Jun 17, 04:40 UTC | Jun 17, 05:15 UTC | 35m |
| 2026-06-16 | CDG4086 | - | Jun 16, 09:25 UTC | Jun 16, 09:55 UTC | 30m |
| 2026-06-16 | CDG4085 | - | Jun 16, 07:20 UTC | Jun 16, 07:55 UTC | 35m |
| 2026-06-15 | CDG4610 | - | Jun 15, 03:30 UTC | Jun 15, 23:50 UTC | 20h 20m |
| 2026-06-15 | CDG4609 | - | Jun 15, 01:45 UTC | Jun 15, 02:15 UTC | 30m |
| 2026-06-14 | CDG4094 | KIX → TNA | Jun 14, 08:35 UTC | Jun 14, 10:15 UTC | 1h 40m |
| 2026-06-14 | CDG4093 | TNA → KIX | Jun 14, 05:35 UTC | Jun 14, 07:25 UTC | 1h 50m |
| 2026-06-13 | CDG4092 | - | Jun 13, 04:05 UTC | Jun 13, 05:45 UTC | 1h 40m |
| 2026-06-12 | CDG4091 | ICN → KIX | Jun 12, 14:15 UTC | Jun 13, 02:15 UTC | 12h 0m |
| 2026-06-12 | CDG4619 | - | Jun 12, 12:35 UTC | Jun 12, 12:55 UTC | 20m |
| 2026-06-12 | CDG4883 | NGB → HAK | Jun 12, 03:25 UTC | Jun 12, 06:30 UTC | 3h 5m |
| 2026-05-31 | CDG1156 | ZUH → PEK | May 31, 12:05 UTC | May 31, 12:15 UTC | 10m |
| 2026-05-29 | CDG7941 | TSN → CGQ | May 29, 01:55 UTC | May 29, 02:15 UTC | 20m |
| 2026-05-28 | CDG1192 | ZUH → TNA | May 28, 00:10 UTC | May 28, 00:25 UTC | 15m |
| 2026-05-27 | CDG7941 | TSN → CGQ | May 27, 02:24 UTC | May 27, 02:34 UTC | 10m |
| 2026-05-26 | CDG4911 | FOC → ZUH | May 26, 08:59 UTC | May 26, 09:29 UTC | 30m |
| 2026-05-26 | CDG4642 | PEK → TAO | May 26, 02:04 UTC | May 26, 02:15 UTC | 10m |
| 2026-05-25 | CDG4686 | SZX → TAO | May 25, 11:55 UTC | May 25, 12:05 UTC | 10m |
| 2026-05-25 | CDG4685 | TAO → SZX | May 25, 10:15 UTC | May 25, 10:35 UTC | 20m |
| 2026-05-25 | CDG4612 | ICN → TAO | May 25, 05:20 UTC | May 25, 05:45 UTC | 25m |
| 2026-05-25 | CDG4611 | TAO → ICN | May 25, 03:05 UTC | May 25, 03:35 UTC | 30m |
| 2026-05-24 | CDG4620 | ICN → TAO | May 24, 15:10 UTC | May 24, 15:35 UTC | 25m |
| 2026-05-24 | CDG4619 | TAO → ICN | May 24, 13:30 UTC | May 24, 14:00 UTC | 30m |
| 2026-05-24 | CDG4086 | TPE → TAO | May 24, 09:35 UTC | May 24, 10:00 UTC | 25m |
| 2026-05-24 | CDG4085 | TAO → TPE | May 24, 07:25 UTC | May 24, 08:10 UTC | 45m |
| 2026-05-23 | CDG4912 | FOC → TAO | May 23, 12:00 UTC | May 23, 12:10 UTC | 10m |
| 2026-05-23 | CDG4911 | FOC → ZUH | May 23, 10:10 UTC | May 23, 10:25 UTC | 15m |
| 2026-05-12 | CDG7630 | SZX → YNT | May 12, 09:00 UTC | May 12, 09:10 UTC | 10m |
| 2026-05-12 | CDG7629 | YNT → SZX | May 12, 07:25 UTC | May 12, 07:45 UTC | 20m |
| 2026-05-11 | CDG4686 | SZX → TAO | May 11, 11:55 UTC | May 11, 12:05 UTC | 10m |
| 2026-05-11 | CDG4685 | TAO → SZX | May 11, 10:10 UTC | May 11, 10:35 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-5725 page for operator, model, and routing details .