sensors Mode-S transponder

78213B

ICAO 24-bit transponder address · allocated to China

Currently assigned to B-226L · BOEING 737 MAX 8

Hex
78213B
Octal
36020473
Decimal
7,872,827
Country
CN
Tail
B-226L
Type
B38M
No current signal · last broadcast 1d ago
Flights observed
55
Distinct callsigns
15
Country
CN
Last broadcast
1d ago

Last known position

Most recent position reported by Mode-S 78213B.

Country allocation

The ICAO 24-bit address 78213B 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 15 distinct

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-05-28 CSN8012 MEL → CAN May 28, 11:20 UTCMay 28, 11:35 UTC15m
2026-05-28 CSN8012 MEL → CAN May 28, 08:50 UTCMay 28, 09:00 UTC10m
2026-05-28 CSN8011 CAN → MEL May 28, 03:50 UTCMay 28, 07:15 UTC3h 25m
2026-05-26 CSN8020 BKK → CAN May 26, 13:04 UTCMay 26, 13:45 UTC40m
2026-05-26 CSN8019 CAN → BKK May 26, 10:44 UTCMay 26, 11:30 UTC45m
2026-05-25 CSN8020 BKK → CAN May 25, 13:20 UTCMay 25, 14:00 UTC40m
2026-05-25 CSN8019 CAN → BKK May 25, 10:45 UTCMay 25, 11:25 UTC40m
2026-05-24 CSN8302 KUL → CAN May 24, 10:30 UTCMay 24, 10:40 UTC10m
2026-05-24 CSN8301 CAN → KUL May 24, 07:40 UTCMay 24, 08:20 UTC40m
2026-05-21 CSN8302 KUL → CAN May 21, 10:05 UTCMay 21, 10:15 UTC10m
2026-05-21 CSN8301 CAN → KUL May 21, 05:25 UTCMay 21, 09:00 UTC3h 35m
2026-05-17 CSN5096 BKK → CAN May 17, 08:10 UTCMay 17, 08:40 UTC30m
2026-05-17 CSN5095 CAN → BKK May 17, 06:10 UTCMay 17, 06:40 UTC30m
2026-05-08 CSN8302 KUL → CAN May 8, 10:14 UTCMay 8, 10:35 UTC20m
2026-05-08 CSN8301 CAN → KUL May 8, 08:14 UTCMay 8, 08:59 UTC45m
2026-05-08 CSN3724 - May 8, 03:19 UTCMay 8, 03:49 UTC30m
2026-05-07 CSN8020 BKK → CAN May 7, 13:00 UTCMay 7, 13:45 UTC45m
2026-05-07 CSN8019 CAN → BKK May 7, 09:30 UTCMay 7, 11:40 UTC2h 10m
2026-05-05 CSN8302 KUL → CAN May 5, 10:25 UTCMay 5, 10:35 UTC10m
2026-05-05 CSN8301 CAN → KUL May 5, 05:20 UTCMay 5, 08:55 UTC3h 35m
2026-05-04 CSN8302 KUL → CAN May 4, 10:15 UTCMay 4, 10:25 UTC10m
2026-05-04 CSN8301 CAN → KUL May 4, 08:15 UTCMay 4, 08:50 UTC35m
2026-05-03 CSN8302 KUL → CAN May 3, 10:45 UTCMay 3, 11:00 UTC15m
2026-05-02 CSN8301 CAN → KUL May 2, 17:45 UTCMay 3, 09:10 UTC15h 24m
2026-05-02 CSN5035 CAN → LAX May 2, 15:35 UTCMay 2, 16:00 UTC25m
2026-05-01 CSN8020 BKK → CAN May 1, 13:35 UTCMay 1, 14:05 UTC30m
2026-05-01 CSN8019 CAN → BKK May 1, 09:35 UTCMay 1, 11:55 UTC2h 20m
2026-04-30 CSN8302 KUL → CAN Apr 30, 10:15 UTCApr 30, 10:25 UTC10m
2026-04-30 CSN8301 CAN → KUL Apr 30, 08:20 UTCApr 30, 09:00 UTC40m
2026-04-30 CSN8301 CAN → KUL Apr 30, 05:30 UTCApr 30, 05:40 UTC10m
2026-04-29 CSN3844 NKG → CAN Apr 29, 08:25 UTCApr 29, 08:34 UTC10m
2026-04-28 CSN3533 CAN → SHA Apr 28, 00:05 UTCApr 28, 00:25 UTC20m
2026-04-27 CSN3109 CAN → PEK Apr 27, 06:20 UTCApr 27, 06:30 UTC10m
2026-04-26 CSN5096 BKK → CAN Apr 26, 08:30 UTCApr 26, 09:00 UTC30m
2026-04-26 CSN5095 CAN → BKK Apr 26, 04:25 UTCApr 26, 06:45 UTC2h 20m
2026-04-24 CSN5096 BKK → CAN Apr 24, 09:20 UTCApr 24, 10:05 UTC45m
2026-04-24 CSN5095 CAN → BKK Apr 24, 05:25 UTCApr 24, 07:50 UTC2h 25m
2026-04-22 CSN8302 KUL → CAN Apr 22, 11:10 UTCApr 22, 11:30 UTC20m
2026-04-22 CSN8302 KUL → CAN Apr 22, 10:05 UTCApr 22, 10:15 UTC10m
2026-04-22 CSN8301 CAN → KUL Apr 22, 06:45 UTCApr 22, 08:20 UTC1h 35m
2026-04-20 CSN8020 BKK → CAN Apr 20, 13:15 UTCApr 20, 13:55 UTC40m
2026-04-20 CSN8019 CAN → BKK Apr 20, 10:45 UTCApr 20, 11:45 UTC1h 0m
2026-04-19 CSN5036 LAX → CAN Apr 19, 18:50 UTCApr 19, 19:10 UTC20m
2026-04-19 CSN5036 LAX → CAN Apr 19, 17:45 UTCApr 19, 18:00 UTC15m
2026-04-19 CSN5035 CAN → LAX Apr 19, 14:40 UTCApr 19, 16:15 UTC1h 35m
2026-04-19 CSN5035 CAN → LAX Apr 19, 12:50 UTCApr 19, 13:00 UTC10m
2026-04-18 CSN8302 KUL → CAN Apr 18, 11:45 UTCApr 18, 12:00 UTC15m
2026-04-18 CSN8302 KUL → CAN Apr 18, 10:35 UTCApr 18, 10:50 UTC15m
2026-04-18 CSN8301 CAN → KUL Apr 18, 07:25 UTCApr 18, 08:55 UTC1h 30m
2026-04-18 CSN8301 CAN → KUL Apr 18, 05:20 UTCApr 18, 08:55 UTC3h 35m

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-226L page for operator, model, and routing details .

Mode-S 78213B frequently asked

What is Mode-S code 78213B?
78213B is an ICAO 24-bit transponder address. Allocated to China. Assigned to B-226L.
Where is Mode-S 78213B registered?
Mode-S code 78213B is allocated to China (CN). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 78213B broadcasting right now?
No active broadcast right now. Last signal was 1d ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 78213B, octal 36020473, decimal 7,872,827.
What flights does 78213B operate?
Mode-S 78213B has broadcast 15 distinct callsigns, including CSN8302, CSN8301, CSN8019, CSN8020, CSN5096.