sensors Mode-S transponder
78085B
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-6858 · AIRBUS A-320
- Hex
- 78085B
- Octal
- 36004133
- Decimal
- 7,866,459
- Country
- CN
- Tail
- B-6858
- Type
- A320
- Flights observed
- 42
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 4d ago
Last known position
Country allocation
The ICAO 24-bit address 78085B 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 |
|---|---|---|---|
| CBJ5618 | - | 8 | 2026-05-06 |
| CBJ5617 | - | 5 | 2026-05-06 |
| CBJ5542 | - | 3 | 2026-04-28 |
| CBJ5263 | - | 3 | 2026-04-21 |
| CBJ5145 | - | 3 | 2026-04-23 |
| CBJ5765 | - | 2 | 2026-05-05 |
| CBJ5272 | - | 2 | 2026-04-29 |
| CBJ5264 | - | 2 | 2026-04-17 |
| CBJ5126 | - | 2 | 2026-04-21 |
| CBJ5125 | - | 2 | 2026-04-21 |
| CBJ5974 | - | 1 | 2026-05-16 |
| CBJ5973 | - | 1 | 2026-05-16 |
| CBJ5761 | - | 1 | 2026-05-28 |
| CBJ5686 | - | 1 | 2026-05-26 |
| CBJ5685 | - | 1 | 2026-05-26 |
| CBJ5596 | - | 1 | 2026-05-07 |
| CBJ5554 | - | 1 | 2026-05-01 |
| CBJ5553 | - | 1 | 2026-04-30 |
| CBJ5513 | - | 1 | 2026-05-04 |
| CBJ5271 | - | 1 | 2026-04-29 |
Recent flights last 42
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-28 | CBJ5761 | - | May 28, 22:55 UTC | May 29, 10:55 UTC | 12h 0m |
| 2026-05-26 | CBJ5686 | - | May 26, 05:00 UTC | May 26, 05:10 UTC | 10m |
| 2026-05-26 | CBJ5685 | - | May 26, 00:04 UTC | May 26, 00:24 UTC | 20m |
| 2026-05-16 | CBJ5974 | - | May 16, 12:55 UTC | May 16, 13:11 UTC | 15m |
| 2026-05-16 | CBJ5973 | - | May 16, 11:21 UTC | May 16, 11:35 UTC | 15m |
| 2026-05-07 | CBJ5596 | - | May 7, 06:15 UTC | May 7, 16:05 UTC | 9h 50m |
| 2026-05-06 | CBJ5618 | - | May 6, 13:55 UTC | May 7, 06:30 UTC | 16h 34m |
| 2026-05-06 | CBJ5618 | - | May 6, 09:45 UTC | May 7, 06:30 UTC | 20h 44m |
| 2026-05-06 | CBJ5617 | - | May 6, 01:20 UTC | May 6, 01:40 UTC | 20m |
| 2026-05-05 | CBJ5617 | - | May 5, 04:50 UTC | May 6, 01:40 UTC | 20h 50m |
| 2026-05-05 | CBJ5765 | - | May 5, 04:40 UTC | May 6, 01:40 UTC | 21h 0m |
| 2026-05-04 | CBJ5765 | - | May 4, 08:50 UTC | May 5, 05:00 UTC | 20h 11m |
| 2026-05-04 | CBJ5513 | - | May 4, 08:30 UTC | May 5, 05:00 UTC | 20h 31m |
| 2026-05-01 | CBJ5554 | - | May 1, 09:25 UTC | May 1, 13:15 UTC | 3h 50m |
| 2026-04-30 | CBJ5553 | - | Apr 30, 07:05 UTC | Apr 30, 23:50 UTC | 16h 45m |
| 2026-04-29 | CBJ5272 | - | Apr 29, 10:30 UTC | Apr 29, 10:40 UTC | 10m |
| 2026-04-29 | CBJ5271 | - | Apr 29, 04:25 UTC | Apr 29, 04:34 UTC | 10m |
| 2026-04-28 | CBJ5542 | - | Apr 28, 06:10 UTC | Apr 29, 04:34 UTC | 22h 24m |
| 2026-04-28 | CBJ5542 | - | Apr 28, 00:25 UTC | Apr 28, 06:35 UTC | 6h 10m |
| 2026-04-26 | CBJ5272 | - | Apr 26, 04:40 UTC | Apr 26, 10:35 UTC | 5h 55m |
| 2026-04-25 | CBJ5542 | - | Apr 25, 05:40 UTC | Apr 26, 04:45 UTC | 23h 5m |
| 2026-04-24 | CBJ5618 | - | Apr 24, 13:20 UTC | Apr 25, 06:05 UTC | 16h 45m |
| 2026-04-24 | CBJ5618 | - | Apr 24, 11:10 UTC | Apr 24, 11:25 UTC | 15m |
| 2026-04-24 | CBJ5618 | - | Apr 24, 04:40 UTC | Apr 24, 09:55 UTC | 5h 15m |
| 2026-04-23 | CBJ5617 | - | Apr 23, 09:01 UTC | Apr 24, 02:05 UTC | 17h 4m |
| 2026-04-23 | CBJ5145 | - | Apr 23, 03:00 UTC | Apr 24, 02:05 UTC | 23h 5m |
| 2026-04-22 | CBJ5145 | - | Apr 22, 13:25 UTC | Apr 23, 09:05 UTC | 19h 40m |
| 2026-04-22 | CBJ5145 | - | Apr 22, 09:00 UTC | Apr 23, 04:15 UTC | 19h 14m |
| 2026-04-21 | CBJ5263 | - | Apr 21, 12:50 UTC | Apr 22, 09:15 UTC | 20h 25m |
| 2026-04-21 | CBJ5126 | - | Apr 21, 12:35 UTC | Apr 22, 09:15 UTC | 20h 40m |
| 2026-04-21 | CBJ5125 | - | Apr 21, 07:45 UTC | Apr 21, 12:50 UTC | 5h 5m |
| 2026-04-20 | CBJ5618 | - | Apr 20, 14:10 UTC | Apr 21, 12:45 UTC | 22h 35m |
| 2026-04-19 | CBJ5617 | - | Apr 19, 07:55 UTC | Apr 20, 01:45 UTC | 17h 50m |
| 2026-04-17 | CBJ5264 | - | Apr 17, 13:40 UTC | Apr 17, 14:05 UTC | 25m |
| 2026-04-17 | CBJ5263 | - | Apr 17, 08:45 UTC | Apr 17, 09:10 UTC | 25m |
| 2026-04-16 | CBJ5126 | - | Apr 16, 13:50 UTC | Apr 16, 14:05 UTC | 15m |
| 2026-04-16 | CBJ5125 | - | Apr 16, 07:34 UTC | Apr 16, 07:49 UTC | 15m |
| 2026-04-15 | CBJ5618 | - | Apr 15, 18:00 UTC | Apr 15, 19:00 UTC | 1h 0m |
| 2026-04-15 | CBJ5618 | - | Apr 15, 12:05 UTC | Apr 15, 12:15 UTC | 10m |
| 2026-04-15 | CBJ5617 | - | Apr 15, 01:20 UTC | Apr 15, 01:40 UTC | 20m |
| 2026-04-13 | CBJ5264 | - | Apr 13, 13:40 UTC | Apr 13, 14:00 UTC | 20m |
| 2026-04-13 | CBJ5263 | - | Apr 13, 08:30 UTC | Apr 13, 08:45 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-6858 page for operator, model, and routing details .