sensors Mode-S transponder
780660
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-3167 · EMBRAER ERJ-190-100
- Hex
- 780660
- Octal
- 36003140
- Decimal
- 7,865,952
- Country
- CN
- Tail
- B-3167
- Type
- E190
- Flights observed
- 40
- Distinct callsigns
- 16
- Country
- CN
- Last broadcast
- 10d ago
Last known position
Country allocation
The ICAO 24-bit address 780660 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 16 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| GCR7779 | - | 8 | 2026-07-17 |
| GCR7780 | - | 7 | 2026-07-17 |
| GCR6532 | Tianjin Airlines | 5 | 2026-07-23 |
| GCR6531 | Tianjin Airlines | 5 | 2026-07-23 |
| GCR7797 | - | 2 | 2026-07-19 |
| GCR6414 | Tianjin Airlines | 2 | 2026-05-04 |
| GCR6413 | Tianjin Airlines | 2 | 2026-05-07 |
| GCR7712 | - | 1 | 2026-07-24 |
| GCR7635 | Tianjin Airlines | 1 | 2026-05-26 |
| GCR6662 | - | 1 | 2026-05-17 |
| GCR6661 | - | 1 | 2026-05-29 |
| GCR6564 | Tianjin Airlines | 1 | 2026-06-05 |
| GCR6563 | Tianjin Airlines | 1 | 2026-06-08 |
| GCR6533 | Tianjin Airlines | 1 | 2026-07-24 |
| GCR6436 | Tianjin Airlines | 1 | 2026-05-05 |
| GCR6435 | Tianjin Airlines | 1 | 2026-05-05 |
Recent flights last 40
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-24 | GCR7712 | - | Jul 24, 14:05 UTC | Jul 24, 14:20 UTC | 15m |
| 2026-07-24 | GCR6533 | HAK → ZUH | Jul 24, 00:15 UTC | Jul 24, 00:25 UTC | 10m |
| 2026-07-23 | GCR6532 | HUZ → HAK | Jul 23, 03:30 UTC | Jul 23, 03:40 UTC | 10m |
| 2026-07-23 | GCR6531 | HAK → HUZ | Jul 23, 02:05 UTC | Jul 23, 02:15 UTC | 10m |
| 2026-07-19 | GCR7797 | - | Jul 19, 00:40 UTC | Jul 19, 00:55 UTC | 15m |
| 2026-07-17 | GCR7780 | - | Jul 17, 14:55 UTC | Jul 17, 15:05 UTC | 10m |
| 2026-07-17 | GCR7779 | - | Jul 17, 11:50 UTC | Jul 17, 12:00 UTC | 10m |
| 2026-07-16 | GCR7779 | - | Jul 16, 11:15 UTC | Jul 16, 11:25 UTC | 10m |
| 2026-07-14 | GCR7780 | - | Jul 14, 14:55 UTC | Jul 14, 15:05 UTC | 10m |
| 2026-07-14 | GCR7779 | - | Jul 14, 11:15 UTC | Jul 14, 11:35 UTC | 20m |
| 2026-07-13 | GCR7780 | - | Jul 13, 14:40 UTC | Jul 13, 14:50 UTC | 10m |
| 2026-07-13 | GCR7779 | - | Jul 13, 11:10 UTC | Jul 13, 11:30 UTC | 20m |
| 2026-07-12 | GCR7780 | - | Jul 12, 14:45 UTC | Jul 12, 15:01 UTC | 15m |
| 2026-07-12 | GCR7779 | - | Jul 12, 11:20 UTC | Jul 12, 11:40 UTC | 20m |
| 2026-07-10 | GCR7780 | - | Jul 10, 14:45 UTC | Jul 10, 14:55 UTC | 10m |
| 2026-07-10 | GCR7779 | - | Jul 10, 11:10 UTC | Jul 10, 11:25 UTC | 15m |
| 2026-07-06 | GCR7780 | - | Jul 6, 14:50 UTC | Jul 6, 15:00 UTC | 10m |
| 2026-07-06 | GCR7779 | - | Jul 6, 11:45 UTC | Jul 6, 12:05 UTC | 20m |
| 2026-07-05 | GCR7780 | - | Jul 5, 14:35 UTC | Jul 5, 14:50 UTC | 15m |
| 2026-07-05 | GCR7779 | - | Jul 5, 11:20 UTC | Jul 5, 11:40 UTC | 20m |
| 2026-07-05 | GCR6531 | - | Jul 5, 05:55 UTC | Jul 5, 06:05 UTC | 10m |
| 2026-07-04 | GCR6532 | - | Jul 4, 03:45 UTC | Jul 4, 04:05 UTC | 20m |
| 2026-07-04 | GCR6531 | - | Jul 4, 01:55 UTC | Jul 4, 02:10 UTC | 15m |
| 2026-07-01 | GCR7797 | - | Jul 1, 00:35 UTC | Jul 1, 00:50 UTC | 15m |
| 2026-06-09 | GCR6532 | HUZ → HAK | Jun 9, 03:35 UTC | Jun 9, 03:45 UTC | 10m |
| 2026-06-09 | GCR6531 | HAK → HUZ | Jun 9, 02:05 UTC | Jun 9, 02:15 UTC | 10m |
| 2026-06-08 | GCR6563 | HAK → CSX | Jun 8, 01:05 UTC | Jun 8, 01:15 UTC | 10m |
| 2026-06-06 | GCR6532 | HUZ → HAK | Jun 6, 06:25 UTC | Jun 6, 06:35 UTC | 10m |
| 2026-06-05 | GCR6532 | HUZ → HAK | Jun 5, 14:25 UTC | Jun 5, 14:40 UTC | 15m |
| 2026-06-05 | GCR6531 | HAK → HUZ | Jun 5, 13:00 UTC | Jun 5, 13:10 UTC | 10m |
| 2026-06-05 | GCR6564 | CSX → HAK | Jun 5, 10:20 UTC | Jun 5, 10:30 UTC | 10m |
| 2026-05-29 | GCR6661 | - | May 29, 03:55 UTC | May 29, 08:55 UTC | 5h 0m |
| 2026-05-26 | GCR7635 | XIY → SHE | May 26, 08:30 UTC | May 26, 08:39 UTC | 10m |
| 2026-05-17 | GCR6662 | - | May 17, 08:35 UTC | May 17, 08:45 UTC | 10m |
| 2026-05-07 | GCR6413 | HET → TSN | May 7, 12:20 UTC | May 7, 12:40 UTC | 20m |
| 2026-05-05 | GCR6436 | CSX → HUZ | May 5, 13:35 UTC | May 5, 13:55 UTC | 20m |
| 2026-05-05 | GCR6435 | HUZ → CSX | May 5, 11:00 UTC | May 5, 11:30 UTC | 30m |
| 2026-05-04 | GCR6414 | TSN → HET | May 4, 08:25 UTC | May 4, 08:50 UTC | 25m |
| 2026-05-03 | GCR6413 | HET → TSN | May 3, 14:35 UTC | May 3, 14:55 UTC | 20m |
| 2026-05-03 | GCR6414 | TSN → HET | May 3, 08:05 UTC | May 3, 08:25 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-3167 page for operator, model, and routing details .