sensors Mode-S transponder
78142A
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-300T · AIRBUS A-320
- Hex
- 78142A
- Octal
- 36012052
- Decimal
- 7,869,482
- Country
- CN
- Tail
- B-300T
- Type
- A320
- Flights observed
- 39
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 10d ago
Last known position
Country allocation
The ICAO 24-bit address 78142A 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 |
|---|---|---|---|
| GCR7835 | Tianjin Airlines | 6 | 2026-07-18 |
| GCR7836 | - | 5 | 2026-07-17 |
| GCR7539 | Tianjin Airlines | 4 | 2026-05-30 |
| GCR7655 | Tianjin Airlines | 3 | 2026-07-26 |
| GCR7830 | - | 2 | 2026-06-22 |
| GCR7978 | Tianjin Airlines | 1 | 2026-06-03 |
| GCR7977 | Tianjin Airlines | 1 | 2026-06-03 |
| GCR7964 | - | 1 | 2026-06-14 |
| GCR7963 | - | 1 | 2026-06-14 |
| GCR7926 | Tianjin Airlines | 1 | 2026-05-07 |
| GCR7925 | Tianjin Airlines | 1 | 2026-05-07 |
| GCR7910 | Tianjin Airlines | 1 | 2026-06-04 |
| GCR7690 | Tianjin Airlines | 1 | 2026-07-20 |
| GCR7674 | Tianjin Airlines | 1 | 2026-05-15 |
| GCR7577 | Tianjin Airlines | 1 | 2026-06-03 |
| GCR7532 | - | 1 | 2026-07-15 |
| GCR7530 | - | 1 | 2026-07-02 |
| GCR6583 | - | 1 | 2026-07-08 |
| GCR6562 | - | 1 | 2026-06-05 |
| GCR6453 | - | 1 | 2026-06-21 |
Recent flights last 39
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | GCR7655 | XIY → DLC | Jul 26, 00:45 UTC | Jul 26, 00:55 UTC | 10m |
| 2026-07-24 | GCR7655 | XIY → DLC | Jul 24, 00:35 UTC | Jul 24, 03:35 UTC | 3h 0m |
| 2026-07-23 | GCR7655 | XIY → DLC | Jul 23, 03:25 UTC | Jul 24, 00:45 UTC | 21h 20m |
| 2026-07-22 | - | - | Jul 22, 03:30 UTC | Jul 23, 00:30 UTC | 21h 0m |
| 2026-07-20 | GCR7690 | ZUH → XIY | Jul 20, 08:45 UTC | Jul 20, 08:55 UTC | 10m |
| 2026-07-18 | GCR7835 | TSN → URC | Jul 18, 00:10 UTC | Jul 18, 00:35 UTC | 25m |
| 2026-07-17 | GCR7836 | - | Jul 17, 14:30 UTC | Jul 17, 14:50 UTC | 20m |
| 2026-07-15 | GCR7532 | - | Jul 15, 07:00 UTC | Jul 15, 09:55 UTC | 2h 55m |
| 2026-07-08 | GCR6450 | - | Jul 8, 18:00 UTC | Jul 8, 18:20 UTC | 20m |
| 2026-07-08 | GCR6449 | - | Jul 8, 16:35 UTC | Jul 8, 16:45 UTC | 10m |
| 2026-07-08 | GCR6583 | - | Jul 8, 00:25 UTC | Jul 8, 03:55 UTC | 3h 30m |
| 2026-07-02 | GCR7530 | - | Jul 2, 10:20 UTC | Jul 2, 10:40 UTC | 20m |
| 2026-06-24 | GCR7836 | - | Jun 24, 14:20 UTC | Jun 24, 14:39 UTC | 20m |
| 2026-06-24 | GCR7835 | - | Jun 24, 00:20 UTC | Jun 24, 00:44 UTC | 25m |
| 2026-06-23 | GCR7836 | - | Jun 23, 14:44 UTC | Jun 23, 15:04 UTC | 20m |
| 2026-06-23 | GCR7835 | - | Jun 23, 00:09 UTC | Jun 23, 00:30 UTC | 20m |
| 2026-06-22 | GCR7830 | - | Jun 22, 05:29 UTC | Jun 22, 05:44 UTC | 15m |
| 2026-06-21 | GCR6453 | - | Jun 21, 15:44 UTC | Jun 21, 15:59 UTC | 15m |
| 2026-06-17 | GCR7830 | - | Jun 17, 08:00 UTC | Jun 17, 08:15 UTC | 15m |
| 2026-06-14 | GCR7964 | - | Jun 14, 19:45 UTC | Jun 14, 22:50 UTC | 3h 5m |
| 2026-06-14 | GCR7963 | - | Jun 14, 15:00 UTC | Jun 14, 17:50 UTC | 2h 50m |
| 2026-06-05 | GCR6562 | - | Jun 5, 14:20 UTC | Jun 5, 14:30 UTC | 10m |
| 2026-06-05 | - | - | Jun 5, 10:05 UTC | Jun 5, 10:15 UTC | 10m |
| 2026-06-04 | GCR7910 | JHG → TSN | Jun 4, 05:25 UTC | Jun 4, 05:35 UTC | 10m |
| 2026-06-03 | GCR7978 | KIX → TSN | Jun 3, 08:05 UTC | Jun 3, 09:35 UTC | 1h 30m |
| 2026-06-03 | GCR7977 | TSN → KIX | Jun 3, 04:55 UTC | Jun 3, 06:20 UTC | 1h 25m |
| 2026-06-03 | GCR7577 | URC → TSN | Jun 3, 01:55 UTC | Jun 3, 02:15 UTC | 20m |
| 2026-05-30 | GCR7539 | URC → TAO | May 30, 05:20 UTC | May 30, 05:45 UTC | 25m |
| 2026-05-29 | GCR7539 | URC → TAO | May 29, 05:50 UTC | May 29, 06:10 UTC | 20m |
| 2026-05-28 | GCR7539 | URC → TAO | May 28, 07:30 UTC | May 28, 07:50 UTC | 20m |
| 2026-05-27 | GCR7539 | URC → TAO | May 27, 07:45 UTC | May 27, 08:05 UTC | 20m |
| 2026-05-26 | GCR7835 | TSN → URC | May 26, 00:09 UTC | May 26, 00:29 UTC | 20m |
| 2026-05-15 | GCR7674 | XIY → TSN | May 15, 08:45 UTC | May 15, 08:55 UTC | 10m |
| 2026-05-07 | GCR7926 | CAN → TSN | May 7, 12:00 UTC | May 7, 12:10 UTC | 10m |
| 2026-05-07 | GCR7925 | TSN → CAN | May 7, 09:35 UTC | May 7, 09:45 UTC | 10m |
| 2026-05-06 | GCR7836 | URC → TSN | May 6, 14:05 UTC | May 6, 14:25 UTC | 20m |
| 2026-05-02 | GCR7835 | TSN → URC | May 2, 00:10 UTC | May 2, 00:35 UTC | 25m |
| 2026-05-01 | GCR7835 | TSN → URC | May 1, 00:10 UTC | May 1, 14:30 UTC | 14h 20m |
| 2026-04-30 | GCR7836 | URC → TSN | Apr 30, 14:00 UTC | Apr 30, 14:20 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-300T page for operator, model, and routing details .