sensors Mode-S transponder
78074B
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-5586 · BOEING 737-800
- Hex
- 78074B
- Octal
- 36003513
- Decimal
- 7,866,187
- Country
- CN
- Tail
- B-5586
- Type
- B738
- Flights observed
- 41
- Distinct callsigns
- 8
- Country
- CN
- Last broadcast
- 4h ago
Last known position
Country allocation
The ICAO 24-bit address 78074B 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 8 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| CSN6222 | - | 14 | 2026-07-08 |
| CSN5104 | - | 13 | 2026-07-11 |
| CSN3987 | - | 5 | 2026-07-14 |
| CSN5103 | - | 3 | 2026-07-06 |
| CSN3988 | - | 2 | 2026-07-13 |
| CSN3292 | China Southern Airlines | 2 | 2026-04-27 |
| CSN6317 | China Southern Airlines | 1 | 2026-04-22 |
| CSN3278 | - | 1 | 2026-07-10 |
Recent flights last 41
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | CSN3987 | - | Jul 14, 05:25 UTC | Jul 14, 10:45 UTC | 5h 20m |
| 2026-07-13 | CSN3988 | - | Jul 13, 09:45 UTC | Jul 14, 05:40 UTC | 19h 55m |
| 2026-07-13 | CSN3987 | - | Jul 13, 05:15 UTC | Jul 13, 10:00 UTC | 4h 45m |
| 2026-07-12 | CSN3987 | - | Jul 12, 10:10 UTC | Jul 13, 05:31 UTC | 19h 20m |
| 2026-07-11 | CSN5104 | - | Jul 11, 14:50 UTC | Jul 12, 10:25 UTC | 19h 35m |
| 2026-07-11 | CSN5104 | - | Jul 11, 11:35 UTC | Jul 12, 10:25 UTC | 22h 50m |
| 2026-07-10 | CSN3278 | - | Jul 10, 04:55 UTC | Jul 10, 05:05 UTC | 10m |
| 2026-07-09 | CSN5104 | - | Jul 9, 11:40 UTC | Jul 9, 15:00 UTC | 3h 20m |
| 2026-07-08 | CSN6222 | - | Jul 8, 05:00 UTC | Jul 8, 05:45 UTC | 45m |
| 2026-07-07 | CSN5104 | - | Jul 7, 14:35 UTC | Jul 7, 15:20 UTC | 45m |
| 2026-07-06 | CSN5103 | - | Jul 6, 12:00 UTC | Jul 6, 12:15 UTC | 15m |
| 2026-07-02 | CSN6222 | - | Jul 2, 12:40 UTC | Jul 3, 04:20 UTC | 15h 40m |
| 2026-06-29 | CSN5104 | - | Jun 29, 11:55 UTC | Jun 29, 15:04 UTC | 3h 10m |
| 2026-06-28 | CSN3987 | - | Jun 28, 05:29 UTC | Jun 28, 10:50 UTC | 5h 20m |
| 2026-06-26 | CSN6222 | - | Jun 26, 01:20 UTC | Jun 26, 08:24 UTC | 7h 5m |
| 2026-06-25 | CSN6222 | - | Jun 25, 01:50 UTC | Jun 25, 06:00 UTC | 4h 10m |
| 2026-06-23 | CSN5104 | - | Jun 23, 12:15 UTC | Jun 23, 15:24 UTC | 3h 10m |
| 2026-06-22 | CSN5104 | - | Jun 22, 11:54 UTC | Jun 22, 15:20 UTC | 3h 25m |
| 2026-06-21 | CSN5104 | - | Jun 21, 11:59 UTC | Jun 21, 14:59 UTC | 3h 0m |
| 2026-06-19 | CSN6222 | - | Jun 19, 04:00 UTC | Jun 19, 04:19 UTC | 20m |
| 2026-06-14 | CSN5104 | - | Jun 14, 14:35 UTC | Jun 14, 15:15 UTC | 40m |
| 2026-06-12 | CSN3988 | CSX → SZX | Jun 12, 05:20 UTC | Jun 12, 10:05 UTC | 4h 45m |
| 2026-06-08 | CSN6222 | XMN → NNG | Jun 8, 09:40 UTC | Jun 9, 04:25 UTC | 18h 45m |
| 2026-06-08 | CSN3987 | SZX → CSX | Jun 8, 05:20 UTC | Jun 9, 04:25 UTC | 23h 5m |
| 2026-06-06 | CSN6222 | XMN → NNG | Jun 6, 05:10 UTC | Jun 6, 05:20 UTC | 10m |
| 2026-06-06 | CSN6222 | XMN → NNG | Jun 6, 01:20 UTC | Jun 6, 04:35 UTC | 3h 15m |
| 2026-06-03 | CSN5104 | - | Jun 3, 14:55 UTC | Jun 3, 15:15 UTC | 20m |
| 2026-06-03 | CSN5103 | - | Jun 3, 12:15 UTC | Jun 3, 12:30 UTC | 15m |
| 2026-05-25 | CSN6222 | XMN → NNG | May 25, 03:50 UTC | May 25, 04:20 UTC | 30m |
| 2026-05-22 | CSN6222 | XMN → NNG | May 22, 01:05 UTC | May 22, 04:30 UTC | 3h 25m |
| 2026-05-19 | CSN5104 | - | May 19, 11:55 UTC | May 19, 14:55 UTC | 3h 0m |
| 2026-05-17 | CSN6222 | XMN → NNG | May 17, 10:25 UTC | May 18, 04:20 UTC | 17h 55m |
| 2026-05-16 | CSN6222 | XMN → NNG | May 16, 01:10 UTC | May 16, 04:20 UTC | 3h 10m |
| 2026-05-08 | CSN5104 | - | May 8, 11:40 UTC | May 8, 15:05 UTC | 3h 25m |
| 2026-05-06 | CSN6222 | XMN → NNG | May 6, 00:55 UTC | May 6, 04:20 UTC | 3h 25m |
| 2026-04-27 | CSN3292 | NNY → CAN | Apr 27, 02:10 UTC | Apr 27, 02:25 UTC | 15m |
| 2026-04-23 | CSN5104 | - | Apr 23, 15:10 UTC | Apr 23, 16:15 UTC | 1h 5m |
| 2026-04-23 | CSN5103 | - | Apr 23, 12:20 UTC | Apr 23, 12:30 UTC | 10m |
| 2026-04-22 | CSN6317 | WUH → HRB | Apr 22, 04:30 UTC | Apr 22, 09:05 UTC | 4h 35m |
| 2026-04-18 | CSN6222 | XMN → NNG | Apr 18, 05:45 UTC | Apr 18, 06:10 UTC | 25m |
| 2026-04-13 | CSN3292 | NNY → CAN | Apr 13, 02:35 UTC | Apr 13, 02:50 UTC | 15m |
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-5586 page for operator, model, and routing details .