sensors Mode-S transponder
7815E6
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-208L · BOEING 737 MAX 8
- Hex
- 7815E6
- Octal
- 36012746
- Decimal
- 7,869,926
- Country
- CN
- Tail
- B-208L
- Type
- B38M
- Flights observed
- 40
- Distinct callsigns
- 14
- Country
- CN
- Last broadcast
- 2h ago
Current position
Country allocation
The ICAO 24-bit address 7815E6 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 |
|---|---|---|---|
| CXA8674 | - | 10 | 2026-07-10 |
| CXA8673 | - | 9 | 2026-07-13 |
| CXA8694 | - | 4 | 2026-07-14 |
| CXA8693 | - | 3 | 2026-07-14 |
| CXA8684 | - | 3 | 2026-07-09 |
| CXA8793 | Xiamen Airlines | 2 | 2026-07-02 |
| CXA8359 | Xiamen Airlines | 2 | 2026-04-25 |
| CXA8842 | - | 1 | 2026-06-24 |
| CXA8841 | - | 1 | 2026-06-24 |
| CXA8783 | Xiamen Airlines | 1 | 2026-05-03 |
| CXA8683 | Xiamen Airlines | 1 | 2026-04-20 |
| CXA8660 | - | 1 | 2026-07-12 |
| CXA8659 | - | 1 | 2026-07-11 |
| CXA8375 | Xiamen Airlines | 1 | 2026-04-27 |
Recent flights last 40
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | CXA8693 | - | Jul 14, 14:15 UTC | Jul 14, 14:35 UTC | 20m |
| 2026-07-14 | CXA8694 | - | Jul 14, 00:15 UTC | Jul 14, 12:55 UTC | 12h 40m |
| 2026-07-13 | CXA8673 | - | Jul 13, 21:05 UTC | Jul 13, 21:20 UTC | 15m |
| 2026-07-13 | CXA8673 | - | Jul 13, 17:15 UTC | Jul 13, 20:30 UTC | 3h 15m |
| 2026-07-12 | CXA8660 | - | Jul 12, 09:55 UTC | Jul 12, 10:30 UTC | 35m |
| 2026-07-11 | CXA8659 | - | Jul 11, 14:20 UTC | Jul 12, 08:40 UTC | 18h 20m |
| 2026-07-10 | CXA8674 | - | Jul 10, 20:10 UTC | Jul 11, 14:30 UTC | 18h 20m |
| 2026-07-10 | CXA8674 | - | Jul 10, 17:35 UTC | Jul 11, 14:30 UTC | 20h 55m |
| 2026-07-10 | CXA8674 | - | Jul 10, 16:30 UTC | Jul 11, 14:30 UTC | 22h 0m |
| 2026-07-09 | CXA8684 | - | Jul 9, 23:55 UTC | Jul 10, 10:10 UTC | 10h 15m |
| 2026-07-09 | CXA8673 | - | Jul 9, 21:15 UTC | Jul 9, 21:30 UTC | 15m |
| 2026-07-09 | CXA8673 | - | Jul 9, 17:25 UTC | Jul 9, 20:40 UTC | 3h 15m |
| 2026-07-07 | CXA8674 | - | Jul 7, 17:35 UTC | Jul 8, 14:25 UTC | 20h 50m |
| 2026-07-07 | CXA8674 | - | Jul 7, 16:30 UTC | Jul 8, 14:25 UTC | 21h 55m |
| 2026-07-07 | CXA8693 | - | Jul 7, 14:30 UTC | Jul 7, 14:50 UTC | 20m |
| 2026-07-06 | CXA8694 | - | Jul 6, 23:55 UTC | Jul 7, 13:05 UTC | 13h 10m |
| 2026-07-06 | CXA8673 | - | Jul 6, 21:20 UTC | Jul 6, 21:40 UTC | 20m |
| 2026-07-06 | CXA8673 | - | Jul 6, 17:40 UTC | Jul 6, 20:45 UTC | 3h 5m |
| 2026-07-02 | CXA8793 | FOC → NNG | Jul 2, 04:50 UTC | Jul 2, 15:35 UTC | 10h 45m |
| 2026-06-24 | CXA8842 | - | Jun 24, 09:24 UTC | Jun 24, 09:39 UTC | 15m |
| 2026-06-24 | CXA8841 | - | Jun 24, 07:34 UTC | Jun 24, 07:59 UTC | 25m |
| 2026-05-06 | CXA8793 | FOC → NNG | May 6, 04:30 UTC | May 6, 14:30 UTC | 10h 0m |
| 2026-05-03 | CXA8783 | FOC → HAK | May 3, 02:35 UTC | May 3, 14:45 UTC | 12h 9m |
| 2026-04-27 | CXA8375 | XMN → NNG | Apr 27, 14:05 UTC | Apr 28, 03:20 UTC | 13h 15m |
| 2026-04-25 | CXA8359 | XMN → NNG | Apr 25, 10:05 UTC | Apr 25, 10:30 UTC | 25m |
| 2026-04-23 | CXA8674 | CGK → CKG | Apr 23, 17:40 UTC | Apr 23, 18:05 UTC | 25m |
| 2026-04-23 | CXA8674 | CGK → CKG | Apr 23, 16:35 UTC | Apr 23, 16:50 UTC | 15m |
| 2026-04-23 | CXA8693 | NKG → CGK | Apr 23, 14:35 UTC | Apr 23, 14:50 UTC | 15m |
| 2026-04-23 | CXA8694 | CGK → NKG | Apr 23, 01:00 UTC | Apr 23, 12:50 UTC | 11h 50m |
| 2026-04-22 | CXA8694 | CGK → NKG | Apr 22, 23:55 UTC | Apr 23, 00:05 UTC | 10m |
| 2026-04-22 | CXA8673 | CKG → CGK | Apr 22, 19:50 UTC | Apr 22, 20:20 UTC | 30m |
| 2026-04-20 | CXA8674 | CGK → CKG | Apr 20, 17:35 UTC | Apr 21, 11:40 UTC | 18h 5m |
| 2026-04-20 | CXA8674 | CGK → CKG | Apr 20, 17:20 UTC | Apr 21, 11:40 UTC | 18h 20m |
| 2026-04-20 | CXA8674 | CGK → CKG | Apr 20, 16:20 UTC | Apr 20, 16:30 UTC | 10m |
| 2026-04-20 | CXA8683 | WUH → CGK | Apr 20, 13:55 UTC | Apr 20, 14:10 UTC | 15m |
| 2026-04-20 | CXA8684 | CGK → WUH | Apr 20, 00:50 UTC | Apr 20, 12:05 UTC | 11h 15m |
| 2026-04-19 | CXA8684 | CGK → WUH | Apr 19, 23:50 UTC | Apr 20, 00:00 UTC | 10m |
| 2026-04-19 | CXA8673 | CKG → CGK | Apr 19, 21:40 UTC | Apr 19, 21:55 UTC | 15m |
| 2026-04-19 | CXA8673 | CKG → CGK | Apr 19, 20:15 UTC | Apr 19, 20:50 UTC | 35m |
| 2026-04-13 | CXA8359 | XMN → NNG | Apr 13, 09:40 UTC | Apr 13, 10:25 UTC | 45m |
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-208L page for operator, model, and routing details .