sensors Mode-S transponder
78137D
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-1248 · AIRBUS A-320neo
- Hex
- 78137D
- Octal
- 36011575
- Decimal
- 7,869,309
- Country
- CN
- Tail
- B-1248
- Type
- A20N
- Flights observed
- 56
- Distinct callsigns
- 7
- Country
- CN
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 78137D 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 7 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-01 | CBJ420 | - | Jun 1, 05:50 UTC | Jun 1, 08:15 UTC | 2h 25m |
| 2026-06-01 | CBJ419 | - | Jun 1, 02:10 UTC | Jun 1, 04:30 UTC | 2h 20m |
| 2026-05-28 | CBJ5775 | - | May 28, 23:15 UTC | May 29, 12:55 UTC | 13h 40m |
| 2026-05-27 | CBJ5724 | - | May 27, 23:35 UTC | May 28, 10:00 UTC | 10h 25m |
| 2026-05-27 | CBJ5288 | - | May 27, 13:00 UTC | May 27, 16:25 UTC | 3h 25m |
| 2026-05-14 | CBJ420 | - | May 14, 06:15 UTC | May 14, 06:55 UTC | 40m |
| 2026-05-14 | CBJ419 | - | May 14, 02:20 UTC | May 14, 04:45 UTC | 2h 25m |
| 2026-05-10 | CBJ420 | - | May 10, 06:10 UTC | May 10, 08:25 UTC | 2h 15m |
| 2026-05-10 | CBJ419 | - | May 10, 02:20 UTC | May 10, 04:39 UTC | 2h 20m |
| 2026-05-09 | CBJ419 | - | May 9, 08:15 UTC | May 10, 04:39 UTC | 20h 25m |
| 2026-05-09 | CBJ419 | - | May 9, 06:10 UTC | May 10, 04:39 UTC | 22h 30m |
| 2026-05-09 | CBJ419 | - | May 9, 01:45 UTC | May 9, 04:40 UTC | 2h 55m |
| 2026-05-08 | CBJ419 | - | May 8, 08:14 UTC | May 9, 04:40 UTC | 20h 25m |
| 2026-05-08 | CBJ419 | - | May 8, 06:09 UTC | May 9, 04:40 UTC | 22h 30m |
| 2026-05-08 | CBJ419 | - | May 8, 02:35 UTC | May 8, 04:44 UTC | 2h 10m |
| 2026-05-02 | CBJ420 | - | May 2, 06:05 UTC | May 2, 08:15 UTC | 2h 10m |
| 2026-05-01 | CBJ419 | - | May 1, 09:20 UTC | May 2, 04:30 UTC | 19h 10m |
| 2026-05-01 | CBJ420 | - | May 1, 07:20 UTC | May 2, 04:30 UTC | 21h 10m |
| 2026-05-01 | CBJ420 | - | May 1, 07:10 UTC | May 2, 04:30 UTC | 21h 20m |
| 2026-05-01 | CBJ419 | - | May 1, 02:30 UTC | May 1, 05:15 UTC | 2h 45m |
| 2026-04-30 | CBJ419 | - | Apr 30, 08:40 UTC | May 1, 05:15 UTC | 20h 35m |
| 2026-04-30 | CBJ419 | - | Apr 30, 06:30 UTC | May 1, 05:15 UTC | 22h 45m |
| 2026-04-30 | CBJ419 | - | Apr 30, 02:15 UTC | Apr 30, 04:50 UTC | 2h 35m |
| 2026-04-29 | CBJ419 | - | Apr 29, 08:30 UTC | Apr 30, 04:50 UTC | 20h 20m |
| 2026-04-29 | CBJ419 | - | Apr 29, 06:19 UTC | Apr 30, 04:50 UTC | 22h 30m |
| 2026-04-29 | CBJ419 | - | Apr 29, 02:35 UTC | Apr 29, 04:49 UTC | 2h 15m |
| 2026-04-28 | CBJ419 | - | Apr 28, 08:30 UTC | Apr 29, 04:49 UTC | 20h 20m |
| 2026-04-28 | CBJ420 | BKK → BKK | Apr 28, 06:40 UTC | Apr 29, 04:49 UTC | 22h 10m |
| 2026-04-28 | CBJ419 | - | Apr 28, 02:40 UTC | Apr 28, 05:05 UTC | 2h 25m |
| 2026-04-27 | CBJ419 | - | Apr 27, 08:40 UTC | Apr 28, 05:05 UTC | 20h 25m |
| 2026-04-27 | CBJ419 | BKK → BKK | Apr 27, 06:25 UTC | Apr 28, 05:05 UTC | 22h 40m |
| 2026-04-27 | CBJ419 | - | Apr 27, 02:20 UTC | Apr 27, 05:00 UTC | 2h 40m |
| 2026-04-26 | CBJ419 | - | Apr 26, 08:35 UTC | Apr 27, 05:00 UTC | 20h 25m |
| 2026-04-26 | CBJ419 | - | Apr 26, 06:25 UTC | Apr 27, 05:00 UTC | 22h 35m |
| 2026-04-26 | CBJ419 | - | Apr 26, 02:15 UTC | Apr 26, 04:35 UTC | 2h 20m |
| 2026-04-25 | CBJ419 | - | Apr 25, 08:35 UTC | Apr 26, 04:35 UTC | 20h 0m |
| 2026-04-25 | CBJ420 | - | Apr 25, 06:35 UTC | Apr 26, 04:35 UTC | 22h 0m |
| 2026-04-25 | CBJ419 | - | Apr 25, 02:20 UTC | Apr 25, 04:50 UTC | 2h 30m |
| 2026-04-24 | CBJ419 | - | Apr 24, 08:45 UTC | Apr 25, 04:50 UTC | 20h 5m |
| 2026-04-24 | CBJ419 | BKK → BKK | Apr 24, 06:35 UTC | Apr 25, 04:50 UTC | 22h 15m |
| 2026-04-24 | CBJ419 | - | Apr 24, 02:40 UTC | Apr 24, 05:10 UTC | 2h 30m |
| 2026-04-23 | CBJ419 | - | Apr 23, 08:30 UTC | Apr 24, 05:10 UTC | 20h 39m |
| 2026-04-23 | CBJ419 | - | Apr 23, 06:20 UTC | Apr 24, 05:10 UTC | 22h 49m |
| 2026-04-23 | CBJ419 | - | Apr 23, 01:45 UTC | Apr 23, 04:45 UTC | 3h 0m |
| 2026-04-21 | CBJ420 | - | Apr 21, 06:10 UTC | Apr 21, 08:30 UTC | 2h 20m |
| 2026-04-21 | CBJ419 | - | Apr 21, 02:25 UTC | Apr 21, 04:50 UTC | 2h 25m |
| 2026-04-20 | CBJ419 | - | Apr 20, 08:30 UTC | Apr 21, 04:50 UTC | 20h 20m |
| 2026-04-20 | CBJ419 | - | Apr 20, 06:20 UTC | Apr 21, 04:50 UTC | 22h 30m |
| 2026-04-20 | CBJ419 | - | Apr 20, 03:55 UTC | Apr 20, 04:55 UTC | 1h 0m |
| 2026-04-18 | CBJ5378 | - | Apr 18, 06:25 UTC | Apr 18, 07:15 UTC | 50m |
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-1248 page for operator, model, and routing details .