sensors Mode-S transponder
7809A8
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-5728 · BOEING 737-800
- Hex
- 7809A8
- Octal
- 36004650
- Decimal
- 7,866,792
- Country
- CN
- Tail
- B-5728
- Type
- B738
- Flights observed
- 39
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 7809A8 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 |
|---|---|---|---|
| CDG7948 | Shandong Airlines | 5 | 2026-06-09 |
| CDG2320 | - | 4 | 2026-07-16 |
| CDG7629 | Shandong Airlines | 3 | 2026-06-08 |
| CDG4912 | - | 3 | 2026-07-20 |
| CDG4911 | - | 3 | 2026-07-20 |
| CDG1178 | - | 3 | 2026-07-15 |
| CDG1177 | - | 3 | 2026-07-15 |
| CDG1200 | - | 2 | 2026-07-02 |
| CDG7630 | Shandong Airlines | 1 | 2026-06-08 |
| CDG7622 | Shandong Airlines | 1 | 2026-04-20 |
| CDG4998 | - | 1 | 2026-06-23 |
| CDG4997 | - | 1 | 2026-06-22 |
| CDG4994 | - | 1 | 2026-07-18 |
| CDG4993 | - | 1 | 2026-07-17 |
| CDG4910 | Shandong Airlines | 1 | 2026-06-11 |
| CDG4632 | Shandong Airlines | 1 | 2026-06-01 |
| CDG4631 | Shandong Airlines | 1 | 2026-06-01 |
| CDG4614 | Shandong Airlines | 1 | 2026-06-02 |
| CDG4613 | Shandong Airlines | 1 | 2026-06-02 |
| CDG2319 | - | 1 | 2026-07-11 |
Recent flights last 39
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-20 | CDG4912 | - | Jul 20, 14:30 UTC | Jul 20, 14:40 UTC | 10m |
| 2026-07-20 | CDG4911 | - | Jul 20, 12:50 UTC | Jul 20, 13:00 UTC | 10m |
| 2026-07-18 | CDG4994 | - | Jul 18, 09:15 UTC | Jul 18, 09:35 UTC | 20m |
| 2026-07-17 | CDG4993 | - | Jul 17, 08:49 UTC | Jul 18, 00:45 UTC | 15h 55m |
| 2026-07-16 | CDG2320 | - | Jul 16, 23:29 UTC | Jul 16, 23:49 UTC | 20m |
| 2026-07-15 | CDG1178 | - | Jul 15, 15:40 UTC | Jul 15, 15:55 UTC | 15m |
| 2026-07-15 | CDG1178 | - | Jul 15, 13:20 UTC | Jul 15, 13:30 UTC | 10m |
| 2026-07-15 | CDG1177 | - | Jul 15, 04:00 UTC | Jul 15, 04:15 UTC | 15m |
| 2026-07-13 | CDG4912 | - | Jul 13, 10:50 UTC | Jul 13, 11:05 UTC | 15m |
| 2026-07-13 | CDG4911 | - | Jul 13, 08:55 UTC | Jul 13, 09:15 UTC | 20m |
| 2026-07-11 | CDG2319 | - | Jul 11, 09:15 UTC | Jul 11, 09:40 UTC | 25m |
| 2026-07-10 | CDG2320 | - | Jul 10, 23:25 UTC | Jul 10, 23:35 UTC | 10m |
| 2026-07-10 | CDG1178 | - | Jul 10, 09:25 UTC | Jul 10, 09:40 UTC | 15m |
| 2026-07-10 | CDG1177 | - | Jul 10, 07:45 UTC | Jul 10, 08:00 UTC | 15m |
| 2026-07-10 | CDG1177 | - | Jul 10, 05:15 UTC | Jul 10, 05:25 UTC | 10m |
| 2026-07-02 | CDG1200 | - | Jul 2, 11:40 UTC | Jul 2, 11:50 UTC | 10m |
| 2026-06-29 | CDG2109 | - | Jun 29, 22:39 UTC | Jun 29, 22:55 UTC | 15m |
| 2026-06-23 | CDG4998 | - | Jun 23, 02:24 UTC | Jun 23, 02:45 UTC | 20m |
| 2026-06-22 | CDG4997 | - | Jun 22, 08:35 UTC | Jun 23, 00:30 UTC | 15h 55m |
| 2026-06-21 | CDG2320 | SHE → TYN | Jun 21, 23:30 UTC | Jun 21, 23:44 UTC | 15m |
| 2026-06-11 | CDG4910 | ZUH → KHN | Jun 11, 05:10 UTC | Jun 11, 05:20 UTC | 10m |
| 2026-06-09 | CDG2320 | SHE → TYN | Jun 9, 23:30 UTC | Jun 9, 23:40 UTC | 10m |
| 2026-06-09 | CDG7948 | WUH → SHE | Jun 9, 06:05 UTC | Jun 9, 06:15 UTC | 10m |
| 2026-06-08 | CDG7630 | SZX → YNT | Jun 8, 08:40 UTC | Jun 8, 08:50 UTC | 10m |
| 2026-06-08 | CDG7629 | YNT → SZX | Jun 8, 06:30 UTC | Jun 8, 07:20 UTC | 50m |
| 2026-06-02 | CDG4614 | ICN → TAO | Jun 2, 06:40 UTC | Jun 2, 07:05 UTC | 25m |
| 2026-06-02 | CDG4613 | TAO → ICN | Jun 2, 04:50 UTC | Jun 2, 05:15 UTC | 25m |
| 2026-06-01 | CDG4632 | HKG → TAO | Jun 1, 09:40 UTC | Jun 1, 11:15 UTC | 1h 35m |
| 2026-06-01 | CDG4631 | TAO → HKG | Jun 1, 06:25 UTC | Jun 1, 07:45 UTC | 1h 20m |
| 2026-05-29 | CDG1200 | ZUH → KHN | May 29, 07:05 UTC | May 29, 07:20 UTC | 15m |
| 2026-05-20 | CDG4912 | FOC → TAO | May 20, 10:45 UTC | May 20, 11:00 UTC | 15m |
| 2026-05-20 | CDG4911 | FOC → ZUH | May 20, 08:45 UTC | May 20, 09:30 UTC | 45m |
| 2026-05-17 | CDG7948 | WUH → SHE | May 17, 06:05 UTC | May 17, 06:15 UTC | 10m |
| 2026-05-08 | CDG7629 | YNT → SZX | May 8, 07:14 UTC | May 8, 07:29 UTC | 15m |
| 2026-04-30 | CDG7948 | WUH → SHE | Apr 30, 09:10 UTC | Apr 30, 09:20 UTC | 10m |
| 2026-04-28 | CDG7948 | WUH → SHE | Apr 28, 09:10 UTC | Apr 28, 09:25 UTC | 15m |
| 2026-04-26 | CDG7948 | WUH → SHE | Apr 26, 07:00 UTC | Apr 26, 07:10 UTC | 10m |
| 2026-04-25 | CDG7629 | YNT → SZX | Apr 25, 07:10 UTC | Apr 25, 07:30 UTC | 20m |
| 2026-04-20 | CDG7622 | CAN → YNT | Apr 20, 04:55 UTC | Apr 20, 05:05 UTC | 10m |
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-5728 page for operator, model, and routing details .