sensors Mode-S transponder
7813AB
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-1077 · AIRBUS A-320neo
- Hex
- 7813AB
- Octal
- 36011653
- Decimal
- 7,869,355
- Country
- CN
- Tail
- B-1077
- Type
- A20N
- Flights observed
- 37
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 7813AB 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 |
|---|---|---|---|
| CDC8656 | - | 3 | 2026-06-21 |
| CDC8095 | - | 3 | 2026-07-13 |
| CDC8021 | Zhejiang Loong Airlines | 3 | 2026-06-07 |
| CDC6094 | - | 3 | 2026-07-21 |
| CDC8866 | Zhejiang Loong Airlines | 2 | 2026-05-03 |
| CDC8655 | - | 2 | 2026-06-21 |
| CDC8565 | - | 2 | 2026-05-15 |
| CDC8054 | Zhejiang Loong Airlines | 2 | 2026-04-30 |
| CDC8053 | Zhejiang Loong Airlines | 2 | 2026-04-30 |
| CDC8022 | Zhejiang Loong Airlines | 2 | 2026-06-07 |
| CDC6054 | Zhejiang Loong Airlines | 2 | 2026-05-06 |
| CDC8998 | Zhejiang Loong Airlines | 1 | 2026-05-05 |
| CDC8997 | Zhejiang Loong Airlines | 1 | 2026-05-05 |
| CDC8706 | Zhejiang Loong Airlines | 1 | 2026-05-28 |
| CDC8705 | Zhejiang Loong Airlines | 1 | 2026-05-28 |
| CDC8539 | - | 1 | 2026-07-17 |
| CDC8358 | - | 1 | 2026-06-19 |
| CDC8357 | - | 1 | 2026-06-19 |
| CDC8241 | - | 1 | 2026-06-06 |
| CDC6053 | Zhejiang Loong Airlines | 1 | 2026-04-15 |
Recent flights last 37
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-21 | CDC6094 | - | Jul 21, 06:50 UTC | Jul 21, 07:00 UTC | 10m |
| 2026-07-20 | CDC6094 | - | Jul 20, 16:10 UTC | Jul 21, 05:45 UTC | 13h 34m |
| 2026-07-17 | CDC8539 | - | Jul 17, 05:50 UTC | Jul 18, 00:39 UTC | 18h 50m |
| 2026-07-13 | CDC8095 | - | Jul 13, 23:35 UTC | Jul 14, 03:20 UTC | 3h 45m |
| 2026-07-13 | CDC8095 | - | Jul 13, 03:50 UTC | Jul 14, 00:00 UTC | 20h 10m |
| 2026-07-12 | CDC8095 | - | Jul 12, 23:40 UTC | Jul 13, 04:00 UTC | 4h 20m |
| 2026-06-27 | CDC6094 | - | Jun 27, 03:25 UTC | Jun 27, 03:34 UTC | 10m |
| 2026-06-21 | CDC8656 | - | Jun 21, 09:35 UTC | Jun 21, 09:44 UTC | 10m |
| 2026-06-21 | CDC8655 | - | Jun 21, 06:50 UTC | Jun 21, 07:09 UTC | 20m |
| 2026-06-19 | CDC8358 | - | Jun 19, 08:09 UTC | Jun 19, 08:34 UTC | 25m |
| 2026-06-19 | CDC8357 | - | Jun 19, 05:54 UTC | Jun 19, 06:14 UTC | 20m |
| 2026-06-17 | CDC8656 | - | Jun 17, 12:40 UTC | Jun 17, 12:55 UTC | 15m |
| 2026-06-17 | CDC8656 | - | Jun 17, 08:40 UTC | Jun 17, 08:50 UTC | 10m |
| 2026-06-17 | CDC8655 | - | Jun 17, 01:25 UTC | Jun 17, 06:50 UTC | 5h 25m |
| 2026-06-07 | CDC8022 | BKK → HGH | Jun 7, 11:10 UTC | Jun 7, 13:25 UTC | 2h 15m |
| 2026-06-07 | CDC8021 | HGH → BKK | Jun 7, 07:30 UTC | Jun 7, 09:50 UTC | 2h 20m |
| 2026-06-06 | CDC8021 | HGH → BKK | Jun 6, 12:40 UTC | Jun 7, 09:50 UTC | 21h 10m |
| 2026-06-06 | CDC8241 | - | Jun 6, 00:15 UTC | Jun 6, 12:40 UTC | 12h 25m |
| 2026-05-28 | CDC8706 | VTE → HGH | May 28, 10:45 UTC | May 28, 12:00 UTC | 1h 15m |
| 2026-05-28 | CDC8705 | HGH → VTE | May 28, 06:45 UTC | May 28, 08:15 UTC | 1h 30m |
| 2026-05-15 | CDC8565 | - | May 15, 05:00 UTC | May 16, 02:55 UTC | 21h 54m |
| 2026-05-15 | CDC8565 | - | May 15, 04:35 UTC | May 15, 05:15 UTC | 40m |
| 2026-05-06 | CDC6054 | ZUH → HGH | May 6, 02:25 UTC | May 6, 02:35 UTC | 10m |
| 2026-05-05 | CDC8998 | SIN → DYG | May 5, 07:50 UTC | May 5, 08:10 UTC | 20m |
| 2026-05-05 | CDC8997 | DYG → SIN | May 5, 05:40 UTC | May 5, 06:00 UTC | 20m |
| 2026-05-03 | CDC8866 | SHE → HGH | May 3, 14:30 UTC | May 3, 15:05 UTC | 35m |
| 2026-04-30 | CDC8054 | HKG → HGH | Apr 30, 09:50 UTC | Apr 30, 10:15 UTC | 25m |
| 2026-04-30 | CDC8053 | HGH → HKG | Apr 30, 07:55 UTC | Apr 30, 08:20 UTC | 25m |
| 2026-04-29 | CDC8022 | BKK → HGH | Apr 29, 10:45 UTC | Apr 29, 13:00 UTC | 2h 15m |
| 2026-04-29 | CDC8021 | HGH → BKK | Apr 29, 06:49 UTC | Apr 29, 09:30 UTC | 2h 41m |
| 2026-04-27 | CDC6030 | - | Apr 27, 07:30 UTC | Apr 27, 07:55 UTC | 25m |
| 2026-04-27 | CDC6029 | - | Apr 27, 05:20 UTC | Apr 27, 06:00 UTC | 40m |
| 2026-04-23 | CDC8866 | SHE → HGH | Apr 23, 14:30 UTC | Apr 23, 15:15 UTC | 45m |
| 2026-04-22 | CDC8054 | HKG → HGH | Apr 22, 09:45 UTC | Apr 22, 10:35 UTC | 50m |
| 2026-04-22 | CDC8053 | HGH → HKG | Apr 22, 07:40 UTC | Apr 22, 08:05 UTC | 25m |
| 2026-04-16 | CDC6054 | ZUH → HGH | Apr 16, 02:34 UTC | Apr 16, 02:54 UTC | 20m |
| 2026-04-15 | CDC6053 | HGH → ZUH | Apr 15, 23:55 UTC | Apr 16, 00:15 UTC | 20m |
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-1077 page for operator, model, and routing details .