sensors Mode-S transponder
78096B
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-6958 · AIRBUS A-320
- Hex
- 78096B
- Octal
- 36004553
- Decimal
- 7,866,731
- Country
- CN
- Tail
- B-6958
- Type
- A320
- Flights observed
- 45
- Distinct callsigns
- 14
- Country
- CN
- Last broadcast
- 1d ago
Current position
Country allocation
The ICAO 24-bit address 78096B 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 |
|---|---|---|---|
| CBJ5193 | - | 8 | 2026-05-22 |
| CBJ5388 | - | 7 | 2026-06-01 |
| CBJ5098 | - | 5 | 2026-05-12 |
| CBJ5097 | - | 5 | 2026-05-12 |
| CBJ5387 | - | 4 | 2026-05-30 |
| CBJ5974 | - | 3 | 2026-05-09 |
| CBJ5973 | - | 3 | 2026-05-09 |
| CBJ5194 | - | 3 | 2026-05-20 |
| CBJ5649 | - | 2 | 2026-05-07 |
| CBJ5654 | - | 1 | 2026-05-05 |
| CBJ5595 | - | 1 | 2026-04-24 |
| CBJ5540 | - | 1 | 2026-04-19 |
| CBJ5312 | - | 1 | 2026-04-30 |
| CBJ5156 | - | 1 | 2026-05-12 |
Recent flights last 45
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-01 | CBJ5388 | - | Jun 1, 02:25 UTC | Jun 1, 13:00 UTC | 10h 35m |
| 2026-05-31 | CBJ5388 | - | May 31, 11:00 UTC | Jun 1, 02:30 UTC | 15h 30m |
| 2026-05-30 | CBJ5388 | - | May 30, 10:45 UTC | May 30, 11:10 UTC | 25m |
| 2026-05-30 | CBJ5387 | - | May 30, 03:05 UTC | May 30, 03:20 UTC | 15m |
| 2026-05-29 | CBJ5388 | - | May 29, 10:45 UTC | May 29, 11:10 UTC | 25m |
| 2026-05-28 | CBJ5387 | - | May 28, 10:45 UTC | May 29, 02:55 UTC | 16h 10m |
| 2026-05-28 | CBJ5387 | - | May 28, 02:30 UTC | May 28, 02:50 UTC | 20m |
| 2026-05-27 | CBJ5388 | - | May 27, 02:24 UTC | May 27, 10:55 UTC | 8h 30m |
| 2026-05-24 | CBJ5388 | - | May 24, 10:50 UTC | May 24, 11:15 UTC | 25m |
| 2026-05-24 | CBJ5387 | - | May 24, 02:25 UTC | May 24, 02:40 UTC | 15m |
| 2026-05-23 | CBJ5388 | - | May 23, 02:25 UTC | May 23, 11:05 UTC | 8h 39m |
| 2026-05-22 | CBJ5193 | - | May 22, 02:15 UTC | May 22, 02:30 UTC | 15m |
| 2026-05-21 | CBJ5193 | - | May 21, 02:25 UTC | May 21, 02:35 UTC | 10m |
| 2026-05-20 | CBJ5194 | - | May 20, 13:30 UTC | May 20, 13:40 UTC | 10m |
| 2026-05-20 | CBJ5193 | - | May 20, 02:15 UTC | May 20, 02:30 UTC | 15m |
| 2026-05-19 | CBJ5193 | - | May 19, 02:30 UTC | May 19, 02:40 UTC | 10m |
| 2026-05-18 | CBJ5194 | - | May 18, 13:20 UTC | May 18, 13:40 UTC | 20m |
| 2026-05-18 | CBJ5193 | - | May 18, 02:15 UTC | May 18, 02:35 UTC | 20m |
| 2026-05-12 | CBJ5098 | - | May 12, 13:51 UTC | May 12, 14:10 UTC | 20m |
| 2026-05-12 | CBJ5097 | - | May 12, 11:45 UTC | May 12, 12:05 UTC | 20m |
| 2026-05-12 | CBJ5156 | - | May 12, 08:45 UTC | May 12, 09:05 UTC | 20m |
| 2026-05-11 | CBJ5098 | - | May 11, 11:00 UTC | May 11, 13:45 UTC | 2h 45m |
| 2026-05-09 | CBJ5974 | - | May 9, 13:15 UTC | May 9, 13:30 UTC | 15m |
| 2026-05-09 | CBJ5973 | - | May 9, 11:10 UTC | May 9, 11:25 UTC | 15m |
| 2026-05-07 | CBJ5649 | - | May 7, 01:25 UTC | May 7, 01:35 UTC | 10m |
| 2026-05-06 | CBJ5193 | - | May 6, 02:25 UTC | May 6, 02:40 UTC | 15m |
| 2026-05-05 | CBJ5654 | - | May 5, 14:45 UTC | May 5, 15:05 UTC | 20m |
| 2026-05-04 | CBJ5194 | - | May 4, 13:15 UTC | May 4, 13:25 UTC | 10m |
| 2026-05-03 | CBJ5193 | - | May 3, 16:25 UTC | May 4, 02:25 UTC | 10h 0m |
| 2026-05-02 | CBJ5974 | - | May 2, 13:05 UTC | May 2, 13:20 UTC | 15m |
| 2026-05-02 | CBJ5973 | - | May 2, 11:15 UTC | May 2, 11:30 UTC | 15m |
| 2026-05-01 | CBJ5098 | - | May 1, 12:50 UTC | May 1, 13:20 UTC | 30m |
| 2026-05-01 | CBJ5097 | - | May 1, 11:00 UTC | May 1, 11:20 UTC | 20m |
| 2026-04-30 | CBJ5974 | - | Apr 30, 15:35 UTC | Apr 30, 15:50 UTC | 15m |
| 2026-04-30 | CBJ5973 | - | Apr 30, 13:40 UTC | Apr 30, 14:00 UTC | 20m |
| 2026-04-30 | CBJ5312 | - | Apr 30, 00:15 UTC | Apr 30, 03:45 UTC | 3h 30m |
| 2026-04-29 | CBJ5098 | - | Apr 29, 14:55 UTC | Apr 29, 15:15 UTC | 20m |
| 2026-04-29 | CBJ5097 | - | Apr 29, 13:00 UTC | Apr 29, 13:15 UTC | 15m |
| 2026-04-24 | CBJ5595 | - | Apr 24, 03:10 UTC | Apr 24, 07:35 UTC | 4h 25m |
| 2026-04-22 | CBJ5098 | - | Apr 22, 14:25 UTC | Apr 22, 14:50 UTC | 25m |
| 2026-04-22 | CBJ5097 | - | Apr 22, 11:45 UTC | Apr 22, 12:05 UTC | 20m |
| 2026-04-21 | CBJ5097 | - | Apr 21, 13:20 UTC | Apr 22, 12:05 UTC | 22h 45m |
| 2026-04-20 | CBJ5193 | - | Apr 20, 02:15 UTC | Apr 20, 02:30 UTC | 15m |
| 2026-04-19 | CBJ5540 | - | Apr 19, 14:50 UTC | Apr 19, 15:00 UTC | 10m |
| 2026-04-15 | CBJ5649 | - | Apr 15, 01:20 UTC | Apr 15, 01:30 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-6958 page for operator, model, and routing details .