sensors Mode-S transponder
7807A3
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-5279 · BOEING 737-700
- Hex
- 7807A3
- Octal
- 36003643
- Decimal
- 7,866,275
- Country
- CN
- Tail
- B-5279
- Type
- B737
- Flights observed
- 39
- Distinct callsigns
- 17
- Country
- CN
- Last broadcast
- 8d ago
Last known position
Country allocation
The ICAO 24-bit address 7807A3 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 17 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| CXA8770 | - | 6 | 2026-07-03 |
| CXA8769 | - | 4 | 2026-07-10 |
| CXA8361 | Xiamen Airlines | 4 | 2026-04-29 |
| CXA8827 | - | 3 | 2026-06-30 |
| CXA820 | - | 3 | 2026-07-08 |
| CXA819 | - | 3 | 2026-07-08 |
| CXA8074 | Xiamen Airlines | 3 | 2026-06-12 |
| CXA8847 | - | 2 | 2026-04-24 |
| CXA8828 | - | 2 | 2026-06-30 |
| CXA8341 | - | 2 | 2026-06-30 |
| CXA8672 | Xiamen Airlines | 1 | 2026-05-17 |
| CXA8671 | Xiamen Airlines | 1 | 2026-05-17 |
| CXA8415 | Xiamen Airlines | 1 | 2026-04-23 |
| CXA8362 | - | 1 | 2026-04-18 |
| CXA8323 | Xiamen Airlines | 1 | 2026-06-03 |
| CXA828 | Xiamen Airlines | 1 | 2026-05-26 |
| CXA827 | Xiamen Airlines | 1 | 2026-05-26 |
Recent flights last 39
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-10 | CXA8769 | - | Jul 10, 00:45 UTC | Jul 10, 01:25 UTC | 40m |
| 2026-07-09 | CXA8769 | - | Jul 9, 05:20 UTC | Jul 10, 01:25 UTC | 20h 5m |
| 2026-07-08 | CXA820 | - | Jul 8, 14:20 UTC | Jul 8, 14:50 UTC | 30m |
| 2026-07-08 | CXA819 | - | Jul 8, 12:00 UTC | Jul 8, 12:30 UTC | 30m |
| 2026-07-08 | CXA8769 | - | Jul 8, 00:55 UTC | Jul 8, 01:35 UTC | 40m |
| 2026-07-03 | CXA8770 | - | Jul 3, 05:00 UTC | Jul 3, 05:50 UTC | 50m |
| 2026-06-30 | CXA8828 | - | Jun 30, 13:55 UTC | Jun 30, 14:05 UTC | 10m |
| 2026-06-30 | CXA8827 | - | Jun 30, 11:45 UTC | Jun 30, 12:05 UTC | 20m |
| 2026-06-30 | CXA8341 | - | Jun 30, 05:45 UTC | Jun 30, 08:50 UTC | 3h 5m |
| 2026-06-29 | CXA8770 | - | Jun 29, 04:34 UTC | Jun 29, 05:30 UTC | 55m |
| 2026-06-28 | CXA8341 | - | Jun 28, 08:09 UTC | Jun 28, 11:00 UTC | 2h 50m |
| 2026-06-26 | CXA8770 | - | Jun 26, 05:35 UTC | Jun 26, 11:55 UTC | 6h 20m |
| 2026-06-23 | CXA8828 | ZUH → XMN | Jun 23, 14:49 UTC | Jun 23, 14:59 UTC | 10m |
| 2026-06-23 | CXA8827 | XMN → ZUH | Jun 23, 13:09 UTC | Jun 23, 13:34 UTC | 25m |
| 2026-06-15 | CXA8769 | XMN → JHG | Jun 15, 01:10 UTC | Jun 15, 06:35 UTC | 5h 25m |
| 2026-06-12 | CXA8074 | HRB → HGH | Jun 12, 05:20 UTC | Jun 12, 16:05 UTC | 10h 45m |
| 2026-06-07 | CXA8074 | HRB → HGH | Jun 7, 04:35 UTC | Jun 7, 07:40 UTC | 3h 5m |
| 2026-06-05 | CXA8074 | HRB → HGH | Jun 5, 04:25 UTC | Jun 5, 07:25 UTC | 3h 0m |
| 2026-06-03 | CXA8323 | FOC → CAN | Jun 3, 03:15 UTC | Jun 3, 03:25 UTC | 10m |
| 2026-05-26 | CXA828 | MNL → XMN | May 26, 04:20 UTC | May 26, 05:30 UTC | 1h 10m |
| 2026-05-26 | CXA827 | XMN → MNL | May 26, 01:00 UTC | May 26, 02:19 UTC | 1h 20m |
| 2026-05-25 | CXA820 | MNL → XMN | May 25, 14:10 UTC | May 25, 15:30 UTC | 1h 20m |
| 2026-05-25 | CXA819 | XMN → MNL | May 25, 06:25 UTC | May 25, 12:15 UTC | 5h 50m |
| 2026-05-23 | CXA820 | MNL → XMN | May 23, 14:15 UTC | May 23, 15:30 UTC | 1h 15m |
| 2026-05-23 | CXA819 | XMN → MNL | May 23, 05:20 UTC | May 23, 12:20 UTC | 7h 0m |
| 2026-05-17 | CXA8672 | MFM → FOC | May 17, 10:50 UTC | May 17, 11:01 UTC | 10m |
| 2026-05-17 | CXA8671 | FOC → MFM | May 17, 08:50 UTC | May 17, 09:10 UTC | 20m |
| 2026-05-06 | CXA8770 | JHG → XMN | May 6, 06:05 UTC | May 7, 00:10 UTC | 18h 5m |
| 2026-05-01 | CXA8770 | JHG → XMN | May 1, 06:10 UTC | May 1, 06:25 UTC | 15m |
| 2026-04-29 | CXA8361 | XMN → HAK | Apr 29, 09:05 UTC | Apr 29, 15:30 UTC | 6h 25m |
| 2026-04-24 | CXA8847 | - | Apr 24, 00:30 UTC | Apr 24, 09:20 UTC | 8h 50m |
| 2026-04-23 | CXA8827 | XMN → ZUH | Apr 23, 12:35 UTC | Apr 23, 12:50 UTC | 15m |
| 2026-04-23 | CXA8415 | XMN → KMG | Apr 23, 04:35 UTC | Apr 23, 09:30 UTC | 4h 55m |
| 2026-04-22 | CXA8847 | - | Apr 22, 00:15 UTC | Apr 22, 00:30 UTC | 15m |
| 2026-04-18 | CXA8362 | - | Apr 18, 13:50 UTC | Apr 18, 14:05 UTC | 15m |
| 2026-04-18 | CXA8361 | XMN → HAK | Apr 18, 10:45 UTC | Apr 18, 11:10 UTC | 25m |
| 2026-04-17 | CXA8361 | XMN → HAK | Apr 17, 15:15 UTC | Apr 18, 11:10 UTC | 19h 56m |
| 2026-04-17 | CXA8361 | XMN → HAK | Apr 17, 12:10 UTC | Apr 17, 12:25 UTC | 15m |
| 2026-04-15 | CXA8770 | JHG → XMN | Apr 15, 07:05 UTC | Apr 15, 07:15 UTC | 10m |
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-5279 page for operator, model, and routing details .