sensors Mode-S transponder
780B4F
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-5842 · BOEING 737-800
- Hex
- 780B4F
- Octal
- 36005517
- Decimal
- 7,867,215
- Country
- CN
- Tail
- B-5842
- Type
- B738
- Flights observed
- 43
- Distinct callsigns
- 15
- Country
- CN
- Last broadcast
- 4d ago
Last known position
Country allocation
The ICAO 24-bit address 780B4F 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
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| OKA2755 | - | 13 | 2026-07-08 |
| OKA3112 | - | 5 | 2026-06-03 |
| OKA2756 | - | 4 | 2026-07-13 |
| OKA2994 | - | 3 | 2026-06-27 |
| OKA2953 | - | 3 | 2026-06-30 |
| OKA2930 | Okay Airways | 3 | 2026-05-31 |
| OKA3111 | - | 2 | 2026-06-03 |
| OKA2954 | Okay Airways | 2 | 2026-06-04 |
| OKA2764 | - | 2 | 2026-06-16 |
| OKA3162 | Okay Airways | 1 | 2026-06-22 |
| OKA3100 | - | 1 | 2026-06-19 |
| OKA3063 | - | 1 | 2026-06-15 |
| OKA2931 | - | 1 | 2026-06-20 |
| OKA2887 | Okay Airways | 1 | 2026-06-07 |
| OKA2763 | - | 1 | 2026-06-16 |
Recent flights last 43
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | OKA2756 | - | Jul 13, 01:20 UTC | Jul 13, 14:20 UTC | 13h 0m |
| 2026-07-08 | OKA2755 | - | Jul 8, 04:00 UTC | Jul 8, 16:05 UTC | 12h 5m |
| 2026-06-30 | OKA2953 | - | Jun 30, 04:45 UTC | Jun 30, 05:00 UTC | 15m |
| 2026-06-27 | OKA2994 | - | Jun 27, 08:14 UTC | Jun 27, 08:35 UTC | 20m |
| 2026-06-25 | OKA2994 | - | Jun 25, 06:14 UTC | Jun 25, 06:25 UTC | 10m |
| 2026-06-23 | OKA2994 | - | Jun 23, 06:15 UTC | Jun 23, 06:29 UTC | 15m |
| 2026-06-22 | OKA3162 | NNG → HAK | Jun 22, 06:05 UTC | Jun 22, 06:15 UTC | 10m |
| 2026-06-20 | OKA2931 | - | Jun 20, 05:44 UTC | Jun 20, 05:59 UTC | 15m |
| 2026-06-19 | OKA3100 | - | Jun 19, 15:04 UTC | Jun 19, 15:24 UTC | 20m |
| 2026-06-16 | OKA2764 | - | Jun 16, 05:15 UTC | Jun 16, 05:25 UTC | 10m |
| 2026-06-16 | OKA2763 | - | Jun 16, 03:10 UTC | Jun 16, 03:20 UTC | 10m |
| 2026-06-15 | OKA3063 | - | Jun 15, 08:20 UTC | Jun 15, 08:35 UTC | 15m |
| 2026-06-11 | OKA2764 | - | Jun 11, 05:00 UTC | Jun 11, 05:10 UTC | 10m |
| 2026-06-07 | OKA2887 | CSX → SYX | Jun 7, 07:10 UTC | Jun 7, 07:20 UTC | 10m |
| 2026-06-04 | OKA2954 | ACX → CKG | Jun 4, 07:30 UTC | Jun 4, 07:40 UTC | 10m |
| 2026-06-03 | OKA3111 | - | Jun 3, 09:50 UTC | Jun 4, 04:55 UTC | 19h 5m |
| 2026-06-03 | OKA3111 | - | Jun 3, 09:35 UTC | Jun 4, 04:55 UTC | 19h 20m |
| 2026-06-03 | OKA3112 | - | Jun 3, 06:45 UTC | Jun 3, 07:05 UTC | 20m |
| 2026-06-02 | OKA2953 | CKG → ACX | Jun 2, 04:55 UTC | Jun 2, 07:20 UTC | 2h 25m |
| 2026-05-31 | OKA2930 | ZUH → KHN | May 31, 09:05 UTC | May 31, 09:15 UTC | 10m |
| 2026-05-30 | OKA2954 | ACX → CKG | May 30, 07:10 UTC | May 30, 07:25 UTC | 15m |
| 2026-05-30 | OKA2953 | CKG → ACX | May 30, 04:40 UTC | May 30, 04:50 UTC | 10m |
| 2026-05-29 | OKA3112 | - | May 29, 07:00 UTC | May 29, 07:20 UTC | 20m |
| 2026-05-26 | OKA2755 | - | May 26, 01:30 UTC | May 26, 14:20 UTC | 12h 50m |
| 2026-05-24 | OKA2755 | - | May 24, 01:25 UTC | May 24, 14:10 UTC | 12h 45m |
| 2026-05-23 | OKA2755 | - | May 23, 14:00 UTC | May 24, 01:30 UTC | 11h 31m |
| 2026-05-20 | OKA2930 | ZUH → KHN | May 20, 08:30 UTC | May 20, 08:40 UTC | 10m |
| 2026-05-18 | OKA2755 | - | May 18, 01:20 UTC | May 18, 14:10 UTC | 12h 50m |
| 2026-05-13 | OKA2930 | ZUH → KHN | May 13, 08:35 UTC | May 13, 08:50 UTC | 15m |
| 2026-05-06 | OKA3112 | - | May 6, 07:01 UTC | May 6, 07:20 UTC | 20m |
| 2026-05-04 | OKA3112 | - | May 4, 07:05 UTC | May 4, 07:25 UTC | 20m |
| 2026-05-01 | OKA3112 | - | May 1, 07:00 UTC | May 1, 07:20 UTC | 20m |
| 2026-04-26 | OKA2756 | TSN → TFU | Apr 26, 01:20 UTC | Apr 26, 14:35 UTC | 13h 15m |
| 2026-04-25 | OKA2755 | - | Apr 25, 01:20 UTC | Apr 25, 14:20 UTC | 13h 0m |
| 2026-04-24 | OKA2755 | - | Apr 24, 14:50 UTC | Apr 25, 01:35 UTC | 10h 45m |
| 2026-04-24 | OKA2755 | - | Apr 24, 02:15 UTC | Apr 25, 01:35 UTC | 23h 20m |
| 2026-04-22 | OKA2755 | - | Apr 22, 03:50 UTC | Apr 22, 04:05 UTC | 15m |
| 2026-04-21 | OKA2755 | - | Apr 21, 03:10 UTC | Apr 21, 15:51 UTC | 12h 40m |
| 2026-04-18 | OKA2755 | - | Apr 18, 01:35 UTC | Apr 18, 14:05 UTC | 12h 30m |
| 2026-04-17 | OKA2756 | TSN → TFU | Apr 17, 14:05 UTC | Apr 17, 14:15 UTC | 10m |
| 2026-04-17 | OKA2755 | - | Apr 17, 01:20 UTC | Apr 17, 01:35 UTC | 15m |
| 2026-04-15 | OKA2756 | TSN → TFU | Apr 15, 14:05 UTC | Apr 15, 14:15 UTC | 10m |
| 2026-04-13 | OKA2755 | - | Apr 13, 02:10 UTC | Apr 13, 02:25 UTC | 15m |
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-5842 page for operator, model, and routing details .