sensors Mode-S transponder
781410
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-300F · AIRBUS A-321
- Hex
- 781410
- Octal
- 36012020
- Decimal
- 7,869,456
- Country
- CN
- Tail
- B-300F
- Type
- A321
- Flights observed
- 42
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 781410 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 |
|---|---|---|---|
| CBJ5347 | - | 5 | 2026-05-21 |
| CBJ5896 | - | 4 | 2026-04-20 |
| CBJ5532 | - | 3 | 2026-05-31 |
| CBJ5348 | - | 3 | 2026-05-21 |
| CBJ5136 | - | 3 | 2026-05-06 |
| CBJ5114 | - | 3 | 2026-05-25 |
| CBJ5113 | - | 3 | 2026-05-25 |
| CBJ5617 | - | 2 | 2026-05-01 |
| CBJ5596 | - | 2 | 2026-06-01 |
| CBJ5269 | - | 2 | 2026-05-27 |
| CBJ5146 | - | 2 | 2026-05-10 |
| CBJ5895 | - | 1 | 2026-04-18 |
| CBJ5618 | - | 1 | 2026-05-01 |
| CBJ5595 | - | 1 | 2026-05-29 |
| CBJ5570 | - | 1 | 2026-05-10 |
| CBJ5233 | - | 1 | 2026-04-19 |
| CBJ5227 | - | 1 | 2026-05-20 |
| CBJ5220 | - | 1 | 2026-04-23 |
| CBJ5219 | - | 1 | 2026-04-23 |
| CBJ5217 | - | 1 | 2026-04-24 |
Recent flights last 42
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-01 | CBJ5596 | - | Jun 1, 01:55 UTC | Jun 1, 15:50 UTC | 13h 55m |
| 2026-05-31 | CBJ5532 | - | May 31, 16:35 UTC | May 31, 17:00 UTC | 25m |
| 2026-05-30 | CBJ5596 | - | May 30, 03:05 UTC | May 30, 15:45 UTC | 12h 40m |
| 2026-05-29 | CBJ5595 | - | May 29, 15:50 UTC | May 30, 03:15 UTC | 11h 25m |
| 2026-05-27 | CBJ5269 | - | May 27, 00:34 UTC | May 27, 00:49 UTC | 15m |
| 2026-05-25 | CBJ5114 | - | May 25, 05:25 UTC | May 25, 05:35 UTC | 10m |
| 2026-05-25 | CBJ5113 | - | May 25, 03:25 UTC | May 25, 03:45 UTC | 20m |
| 2026-05-24 | CBJ5114 | - | May 24, 06:40 UTC | May 24, 06:55 UTC | 15m |
| 2026-05-24 | CBJ5113 | - | May 24, 03:40 UTC | May 24, 04:00 UTC | 20m |
| 2026-05-21 | CBJ5348 | - | May 21, 14:10 UTC | May 21, 14:20 UTC | 10m |
| 2026-05-21 | CBJ5347 | - | May 21, 10:10 UTC | May 21, 10:25 UTC | 15m |
| 2026-05-20 | CBJ5227 | - | May 20, 23:30 UTC | May 20, 23:40 UTC | 10m |
| 2026-05-20 | CBJ5269 | - | May 20, 01:10 UTC | May 20, 01:20 UTC | 10m |
| 2026-05-19 | CBJ5348 | - | May 19, 13:50 UTC | May 19, 14:05 UTC | 15m |
| 2026-05-19 | CBJ5347 | - | May 19, 09:50 UTC | May 19, 10:05 UTC | 15m |
| 2026-05-19 | CBJ5347 | - | May 19, 06:05 UTC | May 19, 06:15 UTC | 10m |
| 2026-05-18 | CBJ5348 | - | May 18, 13:30 UTC | May 18, 13:40 UTC | 10m |
| 2026-05-18 | CBJ5347 | - | May 18, 09:45 UTC | May 18, 10:00 UTC | 15m |
| 2026-05-18 | CBJ5347 | - | May 18, 05:55 UTC | May 18, 06:05 UTC | 10m |
| 2026-05-10 | CBJ5570 | - | May 10, 16:10 UTC | May 11, 11:25 UTC | 19h 15m |
| 2026-05-10 | CBJ5146 | - | May 10, 08:20 UTC | May 11, 01:30 UTC | 17h 10m |
| 2026-05-10 | CBJ5146 | - | May 10, 02:34 UTC | May 11, 01:30 UTC | 22h 55m |
| 2026-05-08 | CBJ5532 | - | May 8, 06:09 UTC | May 8, 11:34 UTC | 5h 25m |
| 2026-05-06 | CBJ5136 | - | May 6, 08:10 UTC | May 7, 01:25 UTC | 17h 14m |
| 2026-05-06 | CBJ5136 | - | May 6, 02:35 UTC | May 7, 01:25 UTC | 22h 49m |
| 2026-05-05 | CBJ5532 | - | May 5, 02:55 UTC | May 5, 11:45 UTC | 8h 50m |
| 2026-05-03 | CBJ5036 | - | May 3, 02:30 UTC | May 3, 02:50 UTC | 20m |
| 2026-05-01 | CBJ5618 | - | May 1, 13:50 UTC | May 1, 14:15 UTC | 25m |
| 2026-05-01 | CBJ5617 | - | May 1, 04:50 UTC | May 1, 09:05 UTC | 4h 15m |
| 2026-05-01 | CBJ5617 | - | May 1, 01:25 UTC | May 1, 01:45 UTC | 20m |
| 2026-04-27 | CBJ5114 | - | Apr 27, 06:25 UTC | Apr 27, 06:40 UTC | 15m |
| 2026-04-27 | CBJ5113 | - | Apr 27, 02:45 UTC | Apr 27, 03:05 UTC | 20m |
| 2026-04-24 | CBJ5217 | - | Apr 24, 23:40 UTC | Apr 24, 23:55 UTC | 15m |
| 2026-04-23 | CBJ5220 | - | Apr 23, 15:40 UTC | Apr 23, 15:55 UTC | 15m |
| 2026-04-23 | CBJ5219 | - | Apr 23, 08:01 UTC | Apr 23, 08:20 UTC | 20m |
| 2026-04-20 | CBJ5896 | - | Apr 20, 12:45 UTC | Apr 21, 02:00 UTC | 13h 15m |
| 2026-04-20 | CBJ5896 | - | Apr 20, 04:20 UTC | Apr 21, 02:00 UTC | 21h 40m |
| 2026-04-19 | CBJ5233 | - | Apr 19, 07:30 UTC | Apr 20, 04:35 UTC | 21h 5m |
| 2026-04-18 | CBJ5895 | - | Apr 18, 02:00 UTC | Apr 18, 02:10 UTC | 10m |
| 2026-04-17 | CBJ5896 | - | Apr 17, 13:30 UTC | Apr 17, 14:00 UTC | 30m |
| 2026-04-17 | CBJ5896 | - | Apr 17, 12:40 UTC | Apr 17, 13:10 UTC | 30m |
| 2026-04-16 | CBJ5136 | - | Apr 16, 16:10 UTC | Apr 16, 16:40 UTC | 30m |
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-300F page for operator, model, and routing details .