sensors Mode-S transponder
78228C
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-32MG · AIRBUS A-330-200
- Hex
- 78228C
- Octal
- 36021214
- Decimal
- 7,873,164
- Country
- CN
- Tail
- B-32MG
- Type
- A332
- Flights observed
- 62
- Distinct callsigns
- 4
- Country
- CN
- Last broadcast
- 6h ago
Last known position
Country allocation
The ICAO 24-bit address 78228C 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 4 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | CBJ666 | - | Jun 2, 12:05 UTC | Jun 2, 13:50 UTC | 1h 45m |
| 2026-06-02 | CBJ665 | - | Jun 2, 03:40 UTC | Jun 2, 09:40 UTC | 6h 0m |
| 2026-05-31 | CBJ666 | - | May 31, 17:10 UTC | May 31, 20:40 UTC | 3h 30m |
| 2026-05-31 | CBJ665 | - | May 31, 08:35 UTC | May 31, 08:55 UTC | 20m |
| 2026-05-29 | CBJ666 | - | May 29, 15:10 UTC | May 29, 18:35 UTC | 3h 25m |
| 2026-05-28 | CBJ666 | - | May 28, 18:10 UTC | May 29, 08:15 UTC | 14h 5m |
| 2026-05-28 | CBJ665 | - | May 28, 13:50 UTC | May 28, 14:05 UTC | 15m |
| 2026-05-28 | CBJ665 | - | May 28, 08:15 UTC | May 28, 11:10 UTC | 2h 55m |
| 2026-05-27 | CBJ665 | - | May 27, 15:05 UTC | May 28, 11:10 UTC | 20h 5m |
| 2026-05-27 | CBJ666 | - | May 27, 14:30 UTC | May 28, 11:10 UTC | 20h 40m |
| 2026-05-26 | CBJ666 | - | May 26, 14:35 UTC | May 27, 07:35 UTC | 17h 0m |
| 2026-05-26 | CBJ665 | - | May 26, 05:45 UTC | May 26, 07:34 UTC | 1h 50m |
| 2026-05-24 | CBJ666 | - | May 24, 16:55 UTC | May 24, 20:25 UTC | 3h 30m |
| 2026-05-23 | CBJ665 | - | May 23, 17:30 UTC | May 24, 11:50 UTC | 18h 20m |
| 2026-05-23 | CBJ666 | - | May 23, 15:05 UTC | May 24, 11:50 UTC | 20h 45m |
| 2026-05-23 | CBJ666 | - | May 23, 14:30 UTC | May 24, 11:50 UTC | 21h 20m |
| 2026-05-22 | CBJ666 | - | May 22, 14:40 UTC | May 23, 07:15 UTC | 16h 35m |
| 2026-05-21 | CBJ666 | - | May 21, 17:35 UTC | May 22, 09:05 UTC | 15h 30m |
| 2026-05-20 | CBJ666 | - | May 20, 14:20 UTC | May 21, 10:20 UTC | 20h 0m |
| 2026-05-19 | CBJ666 | - | May 19, 14:30 UTC | May 20, 08:35 UTC | 18h 6m |
| 2026-05-19 | CBJ665 | - | May 19, 06:10 UTC | May 19, 08:10 UTC | 2h 0m |
| 2026-05-17 | CBJ666 | - | May 17, 18:01 UTC | May 17, 19:40 UTC | 1h 40m |
| 2026-05-16 | CBJ666 | - | May 16, 15:05 UTC | May 17, 10:30 UTC | 19h 25m |
| 2026-05-16 | CBJ666 | - | May 16, 14:11 UTC | May 17, 10:30 UTC | 20h 20m |
| 2026-05-15 | CBJ665 | - | May 15, 15:05 UTC | May 16, 11:55 UTC | 20h 51m |
| 2026-05-15 | CBJ665 | BUD → BUD | May 15, 14:45 UTC | May 16, 11:55 UTC | 21h 10m |
| 2026-05-14 | CBJ666 | BUD → KSN | May 14, 14:05 UTC | May 15, 08:15 UTC | 18h 10m |
| 2026-05-14 | CBJ665 | - | May 14, 05:40 UTC | May 14, 11:55 UTC | 6h 15m |
| 2026-05-11 | CBJ666 | - | May 11, 11:00 UTC | May 11, 14:15 UTC | 3h 15m |
| 2026-05-05 | CBJ666 | - | May 5, 14:35 UTC | May 5, 18:05 UTC | 3h 30m |
| 2026-05-05 | CBJ665 | - | May 5, 07:05 UTC | May 5, 12:10 UTC | 5h 5m |
| 2026-05-03 | CBJ666 | - | May 3, 16:05 UTC | May 3, 21:39 UTC | 5h 35m |
| 2026-05-03 | CBJ665 | - | May 3, 07:25 UTC | May 3, 12:05 UTC | 4h 40m |
| 2026-05-01 | CBJ666 | - | May 1, 14:00 UTC | May 1, 19:50 UTC | 5h 50m |
| 2026-05-01 | CBJ665 | - | May 1, 05:35 UTC | May 1, 11:20 UTC | 5h 45m |
| 2026-04-28 | CBJ666 | - | Apr 28, 14:45 UTC | Apr 28, 20:30 UTC | 5h 45m |
| 2026-04-26 | CBJ666 | - | Apr 26, 14:35 UTC | Apr 26, 18:05 UTC | 3h 30m |
| 2026-04-25 | CBJ664 | - | Apr 25, 13:30 UTC | Apr 25, 18:35 UTC | 5h 5m |
| 2026-04-25 | CBJ663 | - | Apr 25, 10:20 UTC | Apr 25, 11:15 UTC | 55m |
| 2026-04-24 | CBJ666 | - | Apr 24, 15:05 UTC | Apr 24, 17:35 UTC | 2h 30m |
| 2026-04-24 | CBJ665 | - | Apr 24, 06:00 UTC | Apr 24, 08:35 UTC | 2h 35m |
| 2026-04-22 | CBJ664 | - | Apr 22, 13:35 UTC | Apr 22, 18:55 UTC | 5h 20m |
| 2026-04-21 | CBJ666 | - | Apr 21, 14:40 UTC | Apr 22, 08:50 UTC | 18h 10m |
| 2026-04-20 | CBJ664 | - | Apr 20, 18:20 UTC | Apr 21, 09:05 UTC | 14h 45m |
| 2026-04-20 | CBJ664 | - | Apr 20, 13:40 UTC | Apr 21, 09:05 UTC | 19h 25m |
| 2026-04-19 | CBJ666 | - | Apr 19, 15:05 UTC | Apr 20, 09:20 UTC | 18h 15m |
| 2026-04-19 | CBJ666 | - | Apr 19, 14:30 UTC | Apr 20, 09:20 UTC | 18h 50m |
| 2026-04-18 | CBJ664 | - | Apr 18, 14:15 UTC | Apr 19, 06:40 UTC | 16h 25m |
| 2026-04-17 | CBJ666 | - | Apr 17, 19:25 UTC | Apr 17, 20:25 UTC | 1h 0m |
| 2026-04-17 | CBJ666 | - | Apr 17, 18:20 UTC | Apr 17, 19:20 UTC | 1h 0m |
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-32MG page for operator, model, and routing details .