sensors Mode-S transponder
781201
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-3263 · EMBRAER ERJ-190-200
- Hex
- 781201
- Octal
- 36011001
- Decimal
- 7,868,929
- Country
- CN
- Tail
- B-3263
- Type
- E195
- Flights observed
- 42
- Distinct callsigns
- 14
- Country
- CN
- Last broadcast
- 3d ago
Last known position
Country allocation
The ICAO 24-bit address 781201 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 |
|---|---|---|---|
| GCR7994 | - | 6 | 2026-06-18 |
| GCR7993 | - | 6 | 2026-06-18 |
| GCR6413 | - | 6 | 2026-06-23 |
| GCR6414 | - | 5 | 2026-06-28 |
| GCR6675 | - | 4 | 2026-07-08 |
| GCR7797 | - | 3 | 2026-06-05 |
| GCR6676 | Tianjin Airlines | 3 | 2026-07-08 |
| GCR7930 | Tianjin Airlines | 2 | 2026-06-10 |
| GCR7929 | Tianjin Airlines | 2 | 2026-06-10 |
| GCR7674 | Tianjin Airlines | 1 | 2026-05-27 |
| GCR7635 | - | 1 | 2026-07-01 |
| GCR6613 | - | 1 | 2026-06-22 |
| GCR6544 | - | 1 | 2026-05-29 |
| GCR6543 | - | 1 | 2026-05-29 |
Recent flights last 42
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-08 | GCR6676 | YIE → HET | Jul 8, 14:35 UTC | Jul 8, 14:45 UTC | 10m |
| 2026-07-08 | GCR6675 | - | Jul 8, 07:50 UTC | Jul 8, 08:00 UTC | 10m |
| 2026-07-06 | GCR6676 | YIE → HET | Jul 6, 16:00 UTC | Jul 6, 16:15 UTC | 15m |
| 2026-07-06 | GCR6675 | - | Jul 6, 07:55 UTC | Jul 6, 08:05 UTC | 10m |
| 2026-07-05 | GCR6676 | YIE → HET | Jul 5, 18:05 UTC | Jul 5, 18:15 UTC | 10m |
| 2026-07-05 | GCR6675 | - | Jul 5, 09:45 UTC | Jul 5, 09:55 UTC | 10m |
| 2026-07-03 | GCR6675 | - | Jul 3, 08:00 UTC | Jul 3, 08:10 UTC | 10m |
| 2026-07-01 | GCR7635 | - | Jul 1, 10:15 UTC | Jul 1, 10:25 UTC | 10m |
| 2026-06-28 | GCR6414 | - | Jun 28, 08:25 UTC | Jun 28, 08:55 UTC | 30m |
| 2026-06-23 | GCR6413 | - | Jun 23, 14:29 UTC | Jun 23, 14:44 UTC | 15m |
| 2026-06-23 | GCR6414 | - | Jun 23, 07:55 UTC | Jun 23, 08:20 UTC | 25m |
| 2026-06-22 | GCR6613 | - | Jun 22, 06:25 UTC | Jun 22, 06:35 UTC | 10m |
| 2026-06-21 | GCR6413 | HET → TSN | Jun 21, 14:40 UTC | Jun 21, 14:54 UTC | 15m |
| 2026-06-21 | GCR6414 | TSN → HET | Jun 21, 08:15 UTC | Jun 21, 08:35 UTC | 20m |
| 2026-06-20 | GCR6413 | HET → TSN | Jun 20, 14:29 UTC | Jun 20, 14:50 UTC | 20m |
| 2026-06-18 | GCR7994 | - | Jun 18, 13:00 UTC | Jun 18, 13:15 UTC | 15m |
| 2026-06-18 | GCR7993 | - | Jun 18, 11:05 UTC | Jun 18, 11:30 UTC | 25m |
| 2026-06-10 | GCR6413 | HET → TSN | Jun 10, 12:40 UTC | Jun 10, 12:55 UTC | 15m |
| 2026-06-10 | GCR6414 | TSN → HET | Jun 10, 06:15 UTC | Jun 10, 06:35 UTC | 20m |
| 2026-06-10 | GCR7929 | TSN → KWE | Jun 10, 03:35 UTC | Jun 10, 03:55 UTC | 20m |
| 2026-06-10 | GCR7930 | KWE → TSN | Jun 10, 01:30 UTC | Jun 10, 01:55 UTC | 25m |
| 2026-06-08 | GCR6413 | HET → TSN | Jun 8, 15:25 UTC | Jun 8, 15:40 UTC | 15m |
| 2026-06-08 | GCR7994 | ICN → TSN | Jun 8, 04:50 UTC | Jun 8, 05:05 UTC | 15m |
| 2026-06-08 | GCR7993 | TSN → ICN | Jun 8, 02:10 UTC | Jun 8, 02:30 UTC | 20m |
| 2026-06-07 | GCR7994 | ICN → TSN | Jun 7, 04:45 UTC | Jun 7, 05:05 UTC | 20m |
| 2026-06-07 | GCR7993 | TSN → ICN | Jun 7, 02:14 UTC | Jun 7, 02:40 UTC | 25m |
| 2026-06-06 | GCR7994 | ICN → TSN | Jun 6, 13:30 UTC | Jun 6, 13:49 UTC | 20m |
| 2026-06-06 | GCR7993 | TSN → ICN | Jun 6, 11:14 UTC | Jun 6, 11:39 UTC | 25m |
| 2026-06-06 | GCR6414 | TSN → HET | Jun 6, 05:55 UTC | Jun 6, 06:20 UTC | 25m |
| 2026-06-06 | GCR7929 | TSN → KWE | Jun 6, 03:35 UTC | Jun 6, 03:50 UTC | 15m |
| 2026-06-06 | GCR7930 | KWE → TSN | Jun 6, 01:10 UTC | Jun 6, 01:35 UTC | 25m |
| 2026-06-05 | GCR6413 | HET → TSN | Jun 5, 12:30 UTC | Jun 5, 13:00 UTC | 30m |
| 2026-06-05 | GCR7797 | - | Jun 5, 00:40 UTC | Jun 5, 00:55 UTC | 15m |
| 2026-05-30 | GCR7994 | ICN → TSN | May 30, 13:15 UTC | May 30, 13:40 UTC | 25m |
| 2026-05-30 | GCR7993 | TSN → ICN | May 30, 11:00 UTC | May 30, 11:25 UTC | 25m |
| 2026-05-29 | GCR6544 | - | May 29, 09:30 UTC | May 29, 09:50 UTC | 20m |
| 2026-05-29 | GCR6543 | - | May 29, 06:45 UTC | May 29, 07:00 UTC | 15m |
| 2026-05-27 | GCR7674 | XIY → TSN | May 27, 06:34 UTC | May 27, 06:49 UTC | 15m |
| 2026-04-27 | GCR7797 | - | Apr 27, 00:35 UTC | Apr 27, 00:50 UTC | 15m |
| 2026-04-26 | GCR7994 | ICN → TSN | Apr 26, 04:45 UTC | Apr 26, 05:00 UTC | 15m |
| 2026-04-26 | GCR7993 | TSN → ICN | Apr 26, 02:20 UTC | Apr 26, 02:35 UTC | 15m |
| 2026-04-22 | GCR7797 | - | Apr 22, 00:35 UTC | Apr 22, 00: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-3263 page for operator, model, and routing details .