sensors Mode-S transponder
7818F2
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-30E1 · AIRBUS A-321neo
- Hex
- 7818F2
- Octal
- 36014362
- Decimal
- 7,870,706
- Country
- CN
- Tail
- B-30E1
- Type
- A21N
- Flights observed
- 113
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 2d ago
Current position
Country allocation
The ICAO 24-bit address 7818F2 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 |
|---|---|---|---|
| CSN6148 | - | 13 | 2026-07-05 |
| CSN6758 | - | 8 | 2026-07-11 |
| CSN6624 | - | 8 | 2026-06-30 |
| CSN3978 | - | 6 | 2026-07-04 |
| CSN6782 | China Southern Airlines | 5 | 2026-06-15 |
| CSN6762 | China Southern Airlines | 5 | 2026-05-06 |
| CSN6740 | - | 5 | 2026-06-28 |
| CSN6147 | - | 5 | 2026-07-02 |
| CSN6795 | China Southern Airlines | 4 | 2026-06-25 |
| CSN8919 | China Southern Airlines | 3 | 2026-06-13 |
| CSN6757 | China Southern Airlines | 3 | 2026-05-02 |
| CSN6732 | - | 3 | 2026-06-22 |
| CSN6712 | China Southern Airlines | 3 | 2026-06-18 |
| CSN6228 | China Southern Airlines | 3 | 2026-06-20 |
| CSN3977 | China Southern Airlines | 3 | 2026-06-02 |
| CSN8920 | - | 2 | 2026-06-29 |
| CSN8276 | China Southern Airlines | 2 | 2026-06-22 |
| CSN6780 | China Southern Airlines | 2 | 2026-04-20 |
| CSN6754 | - | 2 | 2026-07-06 |
| CSN6736 | China Southern Airlines | 2 | 2026-05-13 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-11 | CSN6758 | - | Jul 11, 15:40 UTC | Jul 11, 15:50 UTC | 10m |
| 2026-07-08 | CSN5941 | - | Jul 8, 08:30 UTC | Jul 8, 08:45 UTC | 15m |
| 2026-07-07 | CSN6630 | - | Jul 7, 12:00 UTC | Jul 8, 06:05 UTC | 18h 5m |
| 2026-07-06 | CSN6754 | - | Jul 6, 02:05 UTC | Jul 6, 07:10 UTC | 5h 5m |
| 2026-07-05 | CSN6148 | - | Jul 5, 10:45 UTC | Jul 6, 07:10 UTC | 20h 25m |
| 2026-07-05 | CSN6148 | - | Jul 5, 06:20 UTC | Jul 6, 02:30 UTC | 20h 10m |
| 2026-07-04 | CSN3978 | - | Jul 4, 04:20 UTC | Jul 4, 04:35 UTC | 15m |
| 2026-07-03 | CSN5691 | - | Jul 3, 05:25 UTC | Jul 3, 19:25 UTC | 14h 0m |
| 2026-07-02 | CSN6147 | - | Jul 2, 14:40 UTC | Jul 3, 05:40 UTC | 15h 0m |
| 2026-07-02 | CSN6514 | - | Jul 2, 01:10 UTC | Jul 2, 14:50 UTC | 13h 40m |
| 2026-06-30 | - | - | Jun 30, 15:00 UTC | Jul 1, 00:35 UTC | 9h 35m |
| 2026-06-30 | CSN6624 | - | Jun 30, 05:55 UTC | Jul 1, 00:35 UTC | 18h 40m |
| 2026-06-29 | CSN6624 | - | Jun 29, 13:49 UTC | Jun 30, 06:15 UTC | 16h 26m |
| 2026-06-29 | CSN6624 | - | Jun 29, 09:05 UTC | Jun 30, 06:15 UTC | 21h 11m |
| 2026-06-29 | CSN8920 | - | Jun 29, 00:05 UTC | Jun 29, 13:54 UTC | 13h 50m |
| 2026-06-28 | CSN6740 | - | Jun 28, 16:00 UTC | Jun 29, 13:54 UTC | 21h 55m |
| 2026-06-28 | CSN6740 | - | Jun 28, 13:14 UTC | Jun 29, 09:14 UTC | 20h 0m |
| 2026-06-28 | CSN6583 | - | Jun 28, 06:24 UTC | Jun 28, 11:09 UTC | 4h 45m |
| 2026-06-28 | CSN3978 | - | Jun 28, 01:59 UTC | Jun 28, 02:49 UTC | 50m |
| 2026-06-27 | CSN6147 | - | Jun 27, 02:45 UTC | Jun 27, 12:50 UTC | 10h 5m |
| 2026-06-26 | CSN6740 | CAN → SYX | Jun 26, 15:10 UTC | Jun 27, 12:50 UTC | 21h 40m |
| 2026-06-26 | CSN6740 | CAN → SYX | Jun 26, 12:34 UTC | Jun 27, 10:05 UTC | 21h 30m |
| 2026-06-26 | CSN6740 | CAN → SYX | Jun 26, 12:19 UTC | Jun 27, 10:05 UTC | 21h 45m |
| 2026-06-26 | CSN6584 | KMG → SYX | Jun 26, 04:45 UTC | Jun 26, 09:05 UTC | 4h 20m |
| 2026-06-26 | CSN3978 | - | Jun 26, 01:34 UTC | Jun 26, 01:45 UTC | 10m |
| 2026-06-25 | CSN6795 | SYX → KWE | Jun 25, 00:44 UTC | Jun 25, 12:15 UTC | 11h 30m |
| 2026-06-24 | CSN6795 | SYX → KWE | Jun 24, 12:34 UTC | Jun 25, 12:15 UTC | 23h 40m |
| 2026-06-24 | CSN6795 | SYX → KWE | Jun 24, 07:34 UTC | Jun 25, 04:29 UTC | 20h 55m |
| 2026-06-24 | CSN6795 | SYX → KWE | Jun 24, 04:34 UTC | Jun 25, 04:29 UTC | 23h 55m |
| 2026-06-24 | CSN6700 | KMG → SYX | Jun 24, 04:05 UTC | Jun 25, 01:04 UTC | 21h 0m |
| 2026-06-24 | CSN6700 | KMG → SYX | Jun 24, 00:05 UTC | Jun 24, 12:34 UTC | 12h 30m |
| 2026-06-23 | CSN6148 | - | Jun 23, 05:15 UTC | Jun 23, 12:45 UTC | 7h 30m |
| 2026-06-22 | CSN6148 | - | Jun 22, 15:45 UTC | Jun 23, 12:45 UTC | 21h 0m |
| 2026-06-22 | CSN6147 | - | Jun 22, 12:34 UTC | Jun 23, 10:10 UTC | 21h 35m |
| 2026-06-22 | CSN6147 | - | Jun 22, 12:25 UTC | Jun 23, 10:10 UTC | 21h 45m |
| 2026-06-22 | CSN8276 | WUH → SYX | Jun 22, 10:00 UTC | Jun 22, 10:15 UTC | 15m |
| 2026-06-22 | CSN6732 | - | Jun 22, 02:10 UTC | Jun 22, 02:19 UTC | 10m |
| 2026-06-20 | CSN6228 | CKG → SYX | Jun 20, 23:55 UTC | Jun 21, 12:44 UTC | 12h 50m |
| 2026-06-20 | CSN8276 | WUH → SYX | Jun 20, 02:29 UTC | Jun 20, 09:59 UTC | 7h 30m |
| 2026-06-19 | CSN6293 | SYX → KMG | Jun 19, 10:59 UTC | Jun 19, 15:14 UTC | 4h 15m |
| 2026-06-18 | CSN6712 | PKX → SYX | Jun 18, 18:45 UTC | Jun 19, 08:34 UTC | 13h 49m |
| 2026-06-18 | CSN6732 | - | Jun 18, 07:10 UTC | Jun 18, 07:20 UTC | 10m |
| 2026-06-17 | CSN6732 | - | Jun 17, 12:20 UTC | Jun 18, 07:20 UTC | 19h 0m |
| 2026-06-16 | CSN6758 | - | Jun 16, 15:45 UTC | Jun 16, 15:55 UTC | 10m |
| 2026-06-15 | CSN6584 | KMG → SYX | Jun 15, 15:45 UTC | Jun 16, 08:39 UTC | 16h 55m |
| 2026-06-15 | CSN6782 | PVG → SYX | Jun 15, 10:15 UTC | Jun 16, 08:30 UTC | 22h 15m |
| 2026-06-15 | CSN6624 | - | Jun 15, 06:00 UTC | Jun 15, 15:55 UTC | 9h 55m |
| 2026-06-13 | CSN8919 | SYX → XIY | Jun 13, 23:55 UTC | Jun 14, 06:20 UTC | 6h 25m |
| 2026-06-13 | CSN8919 | SYX → XIY | Jun 13, 08:00 UTC | Jun 14, 06:20 UTC | 22h 20m |
| 2026-06-13 | CSN8919 | SYX → XIY | Jun 13, 00:40 UTC | Jun 14, 00:20 UTC | 23h 39m |
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-30E1 page for operator, model, and routing details .