sensors Mode-S transponder
7806F6
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-6747 · AIRBUS A-320
- Hex
- 7806F6
- Octal
- 36003366
- Decimal
- 7,866,102
- Country
- CN
- Tail
- B-6747
- Type
- A320
- Flights observed
- 37
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 4d ago
Last known position
Country allocation
The ICAO 24-bit address 7806F6 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 |
|---|---|---|---|
| CBJ419 | - | 5 | 2026-06-15 |
| CBJ5896 | - | 3 | 2026-04-18 |
| CBJ5312 | - | 3 | 2026-07-04 |
| CBJ420 | - | 3 | 2026-06-15 |
| CBJ5895 | - | 2 | 2026-07-06 |
| CBJ5531 | - | 2 | 2026-07-10 |
| CBJ5388 | - | 2 | 2026-05-11 |
| CBJ5288 | - | 2 | 2026-06-24 |
| CBJ5718 | - | 1 | 2026-07-13 |
| CBJ5685 | - | 1 | 2026-04-21 |
| CBJ5678 | - | 1 | 2026-07-12 |
| CBJ5677 | - | 1 | 2026-07-12 |
| CBJ5618 | - | 1 | 2026-04-13 |
| CBJ5617 | - | 1 | 2026-04-13 |
| CBJ5513 | - | 1 | 2026-06-28 |
| CBJ5378 | - | 1 | 2026-06-06 |
| CBJ5311 | - | 1 | 2026-07-04 |
| CBJ5307 | - | 1 | 2026-05-26 |
| CBJ5234 | - | 1 | 2026-07-07 |
| CBJ5218 | - | 1 | 2026-04-22 |
Recent flights last 37
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | CBJ5718 | - | Jul 13, 14:35 UTC | Jul 13, 14:50 UTC | 15m |
| 2026-07-12 | CBJ5678 | - | Jul 12, 14:35 UTC | Jul 12, 14:45 UTC | 10m |
| 2026-07-12 | CBJ5677 | - | Jul 12, 10:01 UTC | Jul 12, 10:20 UTC | 20m |
| 2026-07-10 | CBJ5531 | - | Jul 10, 07:45 UTC | Jul 10, 15:50 UTC | 8h 5m |
| 2026-07-07 | CBJ5234 | - | Jul 7, 02:55 UTC | Jul 7, 15:45 UTC | 12h 50m |
| 2026-07-06 | CBJ5895 | - | Jul 6, 01:50 UTC | Jul 6, 03:00 UTC | 1h 10m |
| 2026-07-04 | CBJ5312 | - | Jul 4, 23:20 UTC | Jul 5, 03:05 UTC | 3h 45m |
| 2026-07-04 | CBJ5311 | - | Jul 4, 02:20 UTC | Jul 4, 23:25 UTC | 21h 5m |
| 2026-07-01 | CBJ5312 | - | Jul 1, 02:35 UTC | Jul 1, 23:55 UTC | 21h 20m |
| 2026-06-30 | CBJ5312 | - | Jun 30, 10:10 UTC | Jul 1, 02:55 UTC | 16h 45m |
| 2026-06-28 | CBJ5513 | - | Jun 28, 09:50 UTC | Jun 28, 13:34 UTC | 3h 45m |
| 2026-06-26 | CBJ5531 | - | Jun 26, 06:50 UTC | Jun 26, 15:54 UTC | 9h 5m |
| 2026-06-24 | CBJ5288 | - | Jun 24, 23:54 UTC | Jun 25, 15:29 UTC | 15h 35m |
| 2026-06-24 | CBJ5288 | - | Jun 24, 08:49 UTC | Jun 24, 15:14 UTC | 6h 25m |
| 2026-06-15 | CBJ420 | - | Jun 15, 06:10 UTC | Jun 15, 07:45 UTC | 1h 35m |
| 2026-06-15 | CBJ419 | - | Jun 15, 01:40 UTC | Jun 15, 04:50 UTC | 3h 10m |
| 2026-06-14 | CBJ419 | - | Jun 14, 06:25 UTC | Jun 15, 04:50 UTC | 22h 25m |
| 2026-06-07 | CBJ366 | - | Jun 7, 11:25 UTC | Jun 7, 12:15 UTC | 50m |
| 2026-06-07 | CBJ365 | - | Jun 7, 08:55 UTC | Jun 7, 09:45 UTC | 50m |
| 2026-06-06 | CBJ5378 | - | Jun 6, 07:25 UTC | Jun 6, 08:00 UTC | 35m |
| 2026-05-26 | CBJ5307 | - | May 26, 22:54 UTC | May 26, 23:05 UTC | 10m |
| 2026-05-24 | CBJ420 | - | May 24, 06:20 UTC | May 24, 08:40 UTC | 2h 20m |
| 2026-05-24 | CBJ419 | - | May 24, 02:40 UTC | May 24, 05:10 UTC | 2h 30m |
| 2026-05-11 | CBJ5388 | - | May 11, 10:45 UTC | May 11, 11:05 UTC | 20m |
| 2026-05-07 | CBJ5131 | - | May 7, 04:20 UTC | May 7, 04:40 UTC | 20m |
| 2026-05-05 | CBJ5388 | - | May 5, 10:45 UTC | May 5, 11:15 UTC | 30m |
| 2026-05-03 | CBJ420 | - | May 3, 06:20 UTC | May 3, 08:35 UTC | 2h 15m |
| 2026-05-03 | CBJ419 | - | May 3, 02:35 UTC | May 3, 05:10 UTC | 2h 34m |
| 2026-05-02 | CBJ419 | - | May 2, 07:20 UTC | May 3, 05:10 UTC | 21h 49m |
| 2026-04-22 | CBJ5218 | - | Apr 22, 08:01 UTC | Apr 22, 08:10 UTC | 10m |
| 2026-04-21 | CBJ5685 | - | Apr 21, 01:50 UTC | Apr 21, 02:15 UTC | 25m |
| 2026-04-18 | CBJ5896 | - | Apr 18, 13:15 UTC | Apr 18, 14:30 UTC | 1h 15m |
| 2026-04-15 | CBJ5896 | - | Apr 15, 13:10 UTC | Apr 15, 14:01 UTC | 50m |
| 2026-04-15 | CBJ5895 | - | Apr 15, 01:05 UTC | Apr 15, 01:15 UTC | 10m |
| 2026-04-14 | CBJ5896 | - | Apr 14, 13:20 UTC | Apr 14, 14:35 UTC | 1h 15m |
| 2026-04-13 | CBJ5618 | - | Apr 13, 13:40 UTC | Apr 13, 14:25 UTC | 45m |
| 2026-04-13 | CBJ5617 | - | Apr 13, 01:25 UTC | Apr 13, 01:45 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-6747 page for operator, model, and routing details .