sensors Mode-S transponder
78102D
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-7997 · BOEING 737-800
- Hex
- 78102D
- Octal
- 36010055
- Decimal
- 7,868,461
- Country
- CN
- Tail
- B-7997
- Type
- B738
- Flights observed
- 42
- Distinct callsigns
- 14
- Country
- CN
- Last broadcast
- 4d ago
Last known position
Country allocation
The ICAO 24-bit address 78102D 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 14 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| CSN6040 | - | 8 | 2026-07-05 |
| CSN6039 | - | 8 | 2026-07-05 |
| CSN604 | - | 4 | 2026-07-10 |
| CSN603 | - | 4 | 2026-07-10 |
| CSN6890 | - | 3 | 2026-07-04 |
| CSN8894 | - | 2 | 2026-06-27 |
| CSN8893 | - | 2 | 2026-06-27 |
| CSN6902 | China Southern Airlines | 2 | 2026-04-29 |
| CSN6901 | China Southern Airlines | 2 | 2026-04-29 |
| CSN5092 | China Southern Airlines | 2 | 2026-04-15 |
| CSN5091 | China Southern Airlines | 2 | 2026-04-15 |
| CSN6916 | China Southern Airlines | 1 | 2026-05-17 |
| CSN6014 | - | 1 | 2026-06-28 |
| CSN6013 | China Southern Airlines | 1 | 2026-06-02 |
Recent flights last 42
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-10 | CSN604 | - | Jul 10, 09:00 UTC | Jul 10, 09:15 UTC | 15m |
| 2026-07-10 | CSN603 | - | Jul 10, 07:00 UTC | Jul 10, 07:25 UTC | 25m |
| 2026-07-05 | CSN6040 | - | Jul 5, 19:05 UTC | Jul 5, 22:50 UTC | 3h 45m |
| 2026-07-05 | CSN6039 | - | Jul 5, 12:55 UTC | Jul 5, 16:55 UTC | 4h 0m |
| 2026-07-04 | CSN6890 | - | Jul 4, 10:25 UTC | Jul 4, 10:35 UTC | 10m |
| 2026-07-02 | CSN604 | - | Jul 2, 09:30 UTC | Jul 2, 09:45 UTC | 15m |
| 2026-07-02 | CSN603 | - | Jul 2, 06:55 UTC | Jul 2, 07:30 UTC | 35m |
| 2026-07-01 | CSN6040 | - | Jul 1, 19:00 UTC | Jul 1, 19:30 UTC | 30m |
| 2026-07-01 | CSN6039 | - | Jul 1, 16:25 UTC | Jul 1, 17:05 UTC | 40m |
| 2026-06-28 | CSN6014 | - | Jun 28, 16:49 UTC | Jun 28, 21:40 UTC | 4h 50m |
| 2026-06-27 | CSN8894 | - | Jun 27, 07:45 UTC | Jun 27, 07:59 UTC | 15m |
| 2026-06-27 | CSN8893 | - | Jun 27, 05:25 UTC | Jun 27, 05:35 UTC | 10m |
| 2026-06-26 | CSN8894 | - | Jun 26, 07:45 UTC | Jun 26, 08:00 UTC | 15m |
| 2026-06-26 | CSN8893 | - | Jun 26, 04:55 UTC | Jun 26, 05:10 UTC | 15m |
| 2026-06-13 | CSN604 | HKG → URC | Jun 13, 09:10 UTC | Jun 13, 09:25 UTC | 15m |
| 2026-06-13 | CSN603 | URC → HKG | Jun 13, 06:50 UTC | Jun 13, 07:30 UTC | 40m |
| 2026-06-12 | CSN6040 | - | Jun 12, 18:45 UTC | Jun 12, 19:50 UTC | 1h 5m |
| 2026-06-12 | CSN6039 | URC → TBS | Jun 12, 16:00 UTC | Jun 12, 17:10 UTC | 1h 10m |
| 2026-06-02 | CSN6013 | URC → NQZ | Jun 2, 16:35 UTC | Jun 2, 21:35 UTC | 5h 0m |
| 2026-06-02 | CSN604 | HKG → URC | Jun 2, 09:00 UTC | Jun 2, 09:15 UTC | 15m |
| 2026-06-02 | CSN603 | URC → HKG | Jun 2, 06:50 UTC | Jun 2, 07:20 UTC | 30m |
| 2026-05-31 | CSN6040 | TBS → URC | May 31, 19:05 UTC | May 31, 22:35 UTC | 3h 30m |
| 2026-05-31 | CSN6039 | URC → TBS | May 31, 16:50 UTC | May 31, 17:20 UTC | 30m |
| 2026-05-28 | CSN6890 | SZX → URC | May 28, 09:55 UTC | May 28, 10:05 UTC | 10m |
| 2026-05-25 | CSN6040 | TBS → URC | May 25, 19:00 UTC | May 25, 19:30 UTC | 29m |
| 2026-05-25 | CSN6039 | URC → TBS | May 25, 16:30 UTC | May 25, 17:00 UTC | 30m |
| 2026-05-17 | CSN6916 | PKX → URC | May 17, 09:45 UTC | May 17, 09:55 UTC | 10m |
| 2026-05-04 | CSN6040 | TBS → URC | May 4, 19:15 UTC | May 4, 19:45 UTC | 30m |
| 2026-05-04 | CSN6039 | URC → TBS | May 4, 12:50 UTC | May 4, 16:50 UTC | 4h 0m |
| 2026-05-02 | CSN6040 | TBS → URC | May 2, 19:00 UTC | May 2, 19:30 UTC | 30m |
| 2026-05-02 | CSN6039 | URC → TBS | May 2, 12:50 UTC | May 2, 17:00 UTC | 4h 10m |
| 2026-04-29 | CSN6902 | PKX → URC | Apr 29, 07:24 UTC | Apr 29, 07:40 UTC | 15m |
| 2026-04-29 | CSN6901 | URC → PKX | Apr 29, 05:09 UTC | Apr 29, 05:30 UTC | 20m |
| 2026-04-21 | CSN6040 | TBS → URC | Apr 21, 19:05 UTC | Apr 21, 19:35 UTC | 30m |
| 2026-04-21 | CSN6039 | URC → TBS | Apr 21, 16:31 UTC | Apr 21, 17:05 UTC | 35m |
| 2026-04-19 | CSN6902 | PKX → URC | Apr 19, 07:30 UTC | Apr 19, 07:50 UTC | 20m |
| 2026-04-19 | CSN6901 | URC → PKX | Apr 19, 04:45 UTC | Apr 19, 05:00 UTC | 15m |
| 2026-04-18 | CSN6890 | SZX → URC | Apr 18, 09:50 UTC | Apr 18, 10:05 UTC | 15m |
| 2026-04-15 | CSN5092 | EVN → URC | Apr 15, 20:00 UTC | Apr 15, 20:25 UTC | 25m |
| 2026-04-15 | CSN5091 | URC → EVN | Apr 15, 17:10 UTC | Apr 15, 17:40 UTC | 30m |
| 2026-04-13 | CSN5092 | - | Apr 13, 20:05 UTC | Apr 13, 20:30 UTC | 25m |
| 2026-04-13 | CSN5091 | URC → EVN | Apr 13, 17:20 UTC | Apr 13, 17:45 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-7997 page for operator, model, and routing details .