sensors Mode-S transponder

789260

ICAO 24-bit transponder address · allocated to China

Currently assigned to B-KJB · BOEING 737-800

Hex
789260
Octal
36111140
Decimal
7,901,792
Country
CN
Tail
B-KJB
Type
B738
No current signal · last broadcast 2h ago
Flights observed
388
Distinct callsigns
20
Country
CN
Last broadcast
2h ago

Last known position

Most recent position reported by Mode-S 789260.

Country allocation

The ICAO 24-bit address 789260 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
HGB309 - 43 2026-07-14
HGB308 - 28 2026-07-14
HGB341 - 27 2026-07-04
HGB703 - 23 2026-07-13
HGB323 Greater Bay Airlines 19 2026-06-13
HGB702 - 17 2026-07-13
HGB340 - 17 2026-07-04
HGB705 - 16 2026-07-10
HGB322 Greater Bay Airlines 16 2026-06-13
HGB8236 - 12 2026-07-13
HGB839 - 10 2026-07-14
HGB8235 - 10 2026-07-13
HGB232 Greater Bay Airlines 10 2026-05-18
HGB838 - 9 2026-07-14
HGB704 - 9 2026-07-10
HGB231 Greater Bay Airlines 9 2026-05-18
HGB383 Greater Bay Airlines 8 2026-05-02
HGB296 Greater Bay Airlines 8 2026-05-10
HGB320 - 7 2026-07-11
HGB873 - 6 2026-06-26

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-14 HGB839 - Jul 14, 13:45 UTCJul 14, 14:20 UTC35m
2026-07-14 HGB838 - Jul 14, 10:05 UTCJul 14, 10:20 UTC15m
2026-07-14 HGB309 - Jul 14, 06:45 UTCJul 14, 08:20 UTC1h 35m
2026-07-14 HGB309 - Jul 14, 05:25 UTCJul 14, 05:40 UTC15m
2026-07-14 HGB308 - Jul 14, 00:55 UTCJul 14, 03:50 UTC2h 55m
2026-07-13 HGB8236 - Jul 13, 12:20 UTCJul 13, 16:00 UTC3h 40m
2026-07-13 HGB8235 HKG → ROR Jul 13, 07:20 UTCJul 13, 11:05 UTC3h 45m
2026-07-13 HGB703 - Jul 13, 04:15 UTCJul 13, 05:31 UTC1h 15m
2026-07-13 HGB702 HKG → TPE Jul 13, 01:10 UTCJul 13, 02:40 UTC1h 30m
2026-07-12 HGB851 - Jul 12, 09:15 UTCJul 12, 13:55 UTC4h 40m
2026-07-12 HGB337 - Jul 12, 06:05 UTCJul 12, 07:35 UTC1h 30m
2026-07-12 HGB336 - Jul 12, 03:45 UTCJul 12, 03:55 UTC10m
2026-07-12 HGB336 - Jul 12, 01:45 UTCJul 12, 02:55 UTC1h 10m
2026-07-11 HGB321 - Jul 11, 07:40 UTCJul 11, 12:00 UTC4h 20m
2026-07-11 HGB320 - Jul 11, 03:50 UTCJul 11, 05:45 UTC1h 55m
2026-07-11 HGB320 - Jul 11, 01:25 UTCJul 11, 01:40 UTC15m
2026-07-10 HGB705 - Jul 10, 13:35 UTCJul 10, 14:55 UTC1h 20m
2026-07-10 HGB704 HKG → TPE Jul 10, 10:40 UTCJul 10, 12:00 UTC1h 20m
2026-07-10 HGB309 - Jul 10, 04:45 UTCJul 10, 07:45 UTC3h 0m
2026-07-10 HGB308 - Jul 10, 02:10 UTCJul 10, 02:25 UTC15m
2026-07-09 HGB308 - Jul 9, 23:40 UTCJul 10, 01:30 UTC1h 50m
2026-07-09 HGB851 - Jul 9, 14:35 UTCJul 9, 15:00 UTC25m
2026-07-09 HGB850 - Jul 9, 09:45 UTCJul 9, 09:55 UTC10m
2026-07-09 HGB309 - Jul 9, 05:20 UTCJul 9, 08:10 UTC2h 50m
2026-07-09 HGB308 - Jul 9, 01:00 UTCJul 9, 04:00 UTC3h 0m
2026-07-08 HGB711 - Jul 8, 19:05 UTCJul 8, 20:45 UTC1h 40m
2026-07-08 HGB710 - Jul 8, 15:45 UTCJul 8, 17:00 UTC1h 15m
2026-07-08 HGB321 NRT → HKG Jul 8, 07:30 UTCJul 8, 11:35 UTC4h 5m
2026-07-08 HGB320 HKG → NRT Jul 8, 01:15 UTCJul 8, 05:20 UTC4h 5m
2026-07-07 HGB851 HKG → HKG Jul 7, 08:15 UTCJul 7, 14:05 UTC5h 50m
2026-07-07 HGB866 HKG → HKG Jul 7, 01:20 UTCJul 7, 06:35 UTC5h 15m
2026-07-06 HGB711 TPE → HKG Jul 6, 18:55 UTCJul 6, 20:15 UTC1h 20m
2026-07-06 HGB710 HKG → TPE Jul 6, 15:45 UTCJul 6, 17:10 UTC1h 25m
2026-07-06 HGB321 NRT → HKG Jul 6, 07:15 UTCJul 6, 11:25 UTC4h 10m
2026-07-06 HGB320 HKG → NRT Jul 6, 01:45 UTCJul 6, 05:55 UTC4h 10m
2026-07-05 HGB711 TPE → HKG Jul 5, 19:15 UTCJul 5, 20:30 UTC1h 15m
2026-07-05 HGB710 HKG → TPE Jul 5, 15:10 UTCJul 5, 16:35 UTC1h 25m
2026-07-05 HGB2327 NRT → HKG Jul 5, 08:00 UTCJul 5, 12:00 UTC4h 0m
2026-07-05 HGB2326 HKG → NRT Jul 5, 02:05 UTCJul 5, 06:10 UTC4h 5m
2026-07-04 HGB341 - Jul 4, 08:30 UTCJul 4, 09:20 UTC50m
2026-07-04 HGB341 - Jul 4, 05:25 UTCJul 4, 07:55 UTC2h 30m
2026-07-04 HGB340 HKG → KIX Jul 4, 00:35 UTCJul 4, 04:00 UTC3h 25m
2026-07-03 HGB839 - Jul 3, 14:05 UTCJul 3, 17:30 UTC3h 25m
2026-07-03 HGB321 NRT → HKG Jul 3, 08:05 UTCJul 3, 12:10 UTC4h 5m
2026-07-03 HGB320 - Jul 3, 02:25 UTCJul 3, 06:25 UTC4h 0m
2026-07-02 HGB851 - Jul 2, 14:55 UTCJul 2, 15:30 UTC35m
2026-07-02 HGB850 - Jul 2, 10:10 UTCJul 2, 10:25 UTC15m
2026-07-02 HGB309 - Jul 2, 08:15 UTCJul 2, 08:35 UTC20m
2026-07-02 HGB309 - Jul 2, 07:00 UTCJul 2, 07:40 UTC40m
2026-07-02 HGB308 - Jul 2, 01:00 UTCJul 2, 02:25 UTC1h 25m

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

Mode-S 789260 frequently asked

What is Mode-S code 789260?
789260 is an ICAO 24-bit transponder address. Allocated to China. Assigned to B-KJB.
Where is Mode-S 789260 registered?
Mode-S code 789260 is allocated to China (CN). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 789260 broadcasting right now?
No active broadcast right now. Last signal was 2h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 789260, octal 36111140, decimal 7,901,792.
What flights does 789260 operate?
Mode-S 789260 has broadcast 20 distinct callsigns, including HGB309, HGB308, HGB341, HGB703, HGB323.