sensors Mode-S transponder
780011
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-5130 · BOEING 737-800
- Hex
- 780011
- Octal
- 36000021
- Decimal
- 7,864,337
- Country
- CN
- Tail
- B-5130
- Type
- B738
- Flights observed
- 51
- Distinct callsigns
- 10
- Country
- CN
- Last broadcast
- 5h ago
Last known position
Country allocation
The ICAO 24-bit address 780011 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 10 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | CYZ282 | - | Jul 14, 15:40 UTC | Jul 14, 15:50 UTC | 10m |
| 2026-07-14 | CYZ281 | - | Jul 14, 12:55 UTC | Jul 14, 13:20 UTC | 25m |
| 2026-07-14 | CYZ281 | - | Jul 14, 10:55 UTC | Jul 14, 11:05 UTC | 10m |
| 2026-07-11 | CYZ282 | - | Jul 11, 07:30 UTC | Jul 11, 07:45 UTC | 15m |
| 2026-07-11 | CYZ281 | - | Jul 11, 03:20 UTC | Jul 11, 03:30 UTC | 10m |
| 2026-07-07 | CYZ282 | - | Jul 7, 07:30 UTC | Jul 7, 09:00 UTC | 1h 30m |
| 2026-07-07 | CYZ281 | - | Jul 7, 04:45 UTC | Jul 7, 05:15 UTC | 30m |
| 2026-07-04 | CYZ282 | - | Jul 4, 15:30 UTC | Jul 4, 16:20 UTC | 50m |
| 2026-07-04 | CYZ281 | - | Jul 4, 12:50 UTC | Jul 4, 13:30 UTC | 40m |
| 2026-07-02 | CYZ282 | - | Jul 2, 08:15 UTC | Jul 2, 09:40 UTC | 1h 25m |
| 2026-07-02 | CYZ281 | ZGN → BKK | Jul 2, 03:30 UTC | Jul 2, 05:35 UTC | 2h 5m |
| 2026-06-30 | CYZ282 | - | Jun 30, 07:15 UTC | Jun 30, 08:40 UTC | 1h 25m |
| 2026-06-30 | CYZ281 | - | Jun 30, 03:15 UTC | Jun 30, 05:20 UTC | 2h 5m |
| 2026-06-16 | CYZ222 | - | Jun 16, 05:50 UTC | Jun 16, 05:59 UTC | 10m |
| 2026-06-16 | CYZ221 | - | Jun 16, 04:00 UTC | Jun 16, 04:25 UTC | 25m |
| 2026-06-11 | CYZ218 | - | Jun 11, 08:10 UTC | Jun 11, 09:50 UTC | 1h 40m |
| 2026-06-11 | CYZ217 | - | Jun 11, 05:10 UTC | Jun 11, 06:35 UTC | 1h 25m |
| 2026-06-05 | CYZ218 | - | Jun 5, 08:10 UTC | Jun 5, 09:45 UTC | 1h 35m |
| 2026-06-04 | CYZ217 | - | Jun 4, 12:20 UTC | Jun 5, 07:00 UTC | 18h 40m |
| 2026-06-04 | CYZ280 | - | Jun 4, 10:35 UTC | Jun 5, 07:00 UTC | 20h 25m |
| 2026-06-04 | CYZ279 | - | Jun 4, 06:35 UTC | Jun 4, 08:30 UTC | 1h 55m |
| 2026-06-02 | CYZ218 | - | Jun 2, 08:15 UTC | Jun 2, 09:45 UTC | 1h 30m |
| 2026-06-02 | CYZ217 | - | Jun 2, 05:05 UTC | Jun 2, 06:30 UTC | 1h 25m |
| 2026-05-31 | CYZ280 | - | May 31, 10:25 UTC | May 31, 12:40 UTC | 2h 15m |
| 2026-05-31 | CYZ279 | - | May 31, 08:25 UTC | May 31, 08:40 UTC | 15m |
| 2026-05-28 | CYZ222 | ICN → CGO | May 28, 06:15 UTC | May 28, 06:35 UTC | 20m |
| 2026-05-28 | CYZ221 | CGO → ICN | May 28, 04:10 UTC | May 28, 04:30 UTC | 20m |
| 2026-05-21 | CYZ218 | - | May 21, 08:25 UTC | May 21, 10:05 UTC | 1h 40m |
| 2026-05-21 | CYZ217 | - | May 21, 05:05 UTC | May 21, 06:35 UTC | 1h 30m |
| 2026-05-15 | CYZ218 | - | May 15, 07:55 UTC | May 15, 09:10 UTC | 1h 15m |
| 2026-05-15 | CYZ217 | - | May 15, 05:15 UTC | May 15, 06:45 UTC | 1h 30m |
| 2026-05-14 | CYZ217 | - | May 14, 08:20 UTC | May 15, 06:45 UTC | 22h 25m |
| 2026-05-14 | CYZ217 | - | May 14, 05:25 UTC | May 14, 07:00 UTC | 1h 35m |
| 2026-05-12 | CYZ222 | ICN → CGO | May 12, 06:45 UTC | May 12, 07:00 UTC | 15m |
| 2026-05-12 | CYZ221 | CGO → ICN | May 12, 04:55 UTC | May 12, 05:10 UTC | 15m |
| 2026-05-07 | CYZ222 | ICN → CGO | May 7, 05:50 UTC | May 7, 06:05 UTC | 15m |
| 2026-05-05 | CYZ222 | ICN → CGO | May 5, 06:10 UTC | May 5, 06:20 UTC | 10m |
| 2026-05-02 | CYZ280 | - | May 2, 10:20 UTC | May 2, 12:25 UTC | 2h 5m |
| 2026-05-02 | CYZ279 | - | May 2, 06:30 UTC | May 2, 08:20 UTC | 1h 50m |
| 2026-04-28 | CYZ202 | ICN → XIY | Apr 28, 11:35 UTC | Apr 28, 11:50 UTC | 15m |
| 2026-04-28 | CYZ201 | XIY → ICN | Apr 28, 09:45 UTC | Apr 28, 09:55 UTC | 10m |
| 2026-04-25 | CYZ221 | CGO → ICN | Apr 25, 04:20 UTC | Apr 25, 04:30 UTC | 10m |
| 2026-04-24 | CYZ202 | ICN → XIY | Apr 24, 12:00 UTC | Apr 24, 12:15 UTC | 15m |
| 2026-04-24 | CYZ201 | XIY → ICN | Apr 24, 10:20 UTC | Apr 24, 10:35 UTC | 15m |
| 2026-04-23 | CYZ222 | ICN → CGO | Apr 23, 06:10 UTC | Apr 23, 06:20 UTC | 10m |
| 2026-04-23 | CYZ221 | CGO → ICN | Apr 23, 04:15 UTC | Apr 23, 04:25 UTC | 10m |
| 2026-04-21 | CYZ202 | ICN → XIY | Apr 21, 12:10 UTC | Apr 21, 12:25 UTC | 15m |
| 2026-04-21 | CYZ201 | XIY → ICN | Apr 21, 09:50 UTC | Apr 21, 10:10 UTC | 20m |
| 2026-04-16 | CYZ222 | ICN → CGO | Apr 16, 05:45 UTC | Apr 16, 06:00 UTC | 15m |
| 2026-04-14 | CYZ202 | ICN → XIY | Apr 14, 11:40 UTC | Apr 14, 11:50 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-5130 page for operator, model, and routing details .