sensors Mode-S transponder
7BB130
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-5111 · BOEING 737-800
- Hex
- 7BB130
- Octal
- 36730460
- Decimal
- 8,106,288
- Country
- CN
- Tail
- B-5111
- Type
- B738
- Flights observed
- 192
- Distinct callsigns
- 8
- Country
- CN
- Last broadcast
- 16h ago
Last known position
Country allocation
The ICAO 24-bit address 7BB130 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 8 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-20 | CDG2434 | KIX → TAO | Jul 20, 21:45 UTC | Jul 20, 23:15 UTC | 1h 30m |
| 2026-07-20 | CDG2433 | - | Jul 20, 19:20 UTC | Jul 20, 20:20 UTC | 1h 0m |
| 2026-07-19 | CDG2433 | - | Jul 19, 22:20 UTC | Jul 20, 20:20 UTC | 22h 0m |
| 2026-07-19 | CDG2434 | KIX → TAO | Jul 19, 21:30 UTC | Jul 20, 20:00 UTC | 22h 30m |
| 2026-07-19 | CDG2433 | - | Jul 19, 19:20 UTC | Jul 19, 20:20 UTC | 1h 0m |
| 2026-07-18 | CDG2434 | KIX → TAO | Jul 18, 22:05 UTC | Jul 19, 20:20 UTC | 22h 15m |
| 2026-07-18 | CDG2434 | KIX → TAO | Jul 18, 21:50 UTC | Jul 19, 20:00 UTC | 22h 10m |
| 2026-07-18 | CDG2433 | - | Jul 18, 19:20 UTC | Jul 18, 20:20 UTC | 1h 0m |
| 2026-07-18 | CDG2433 | - | Jul 18, 00:04 UTC | Jul 18, 20:20 UTC | 20h 16m |
| 2026-07-17 | CDG2434 | KIX → TAO | Jul 17, 22:20 UTC | Jul 18, 20:20 UTC | 22h 1m |
| 2026-07-17 | CDG2433 | FUJ → KIX | Jul 17, 19:49 UTC | Jul 17, 20:44 UTC | 55m |
| 2026-07-16 | CDG2434 | KIX → TAO | Jul 16, 22:05 UTC | Jul 17, 20:44 UTC | 22h 40m |
| 2026-07-16 | CDG2434 | KIX → TAO | Jul 16, 21:50 UTC | Jul 17, 20:00 UTC | 22h 10m |
| 2026-07-16 | CDG2433 | - | Jul 16, 19:35 UTC | Jul 16, 20:35 UTC | 1h 0m |
| 2026-07-16 | CDG2433 | - | Jul 16, 00:05 UTC | Jul 16, 20:35 UTC | 20h 30m |
| 2026-07-15 | CDG2434 | - | Jul 15, 22:35 UTC | Jul 16, 20:35 UTC | 22h 0m |
| 2026-07-15 | CDG2433 | - | Jul 15, 20:10 UTC | Jul 15, 21:10 UTC | 1h 0m |
| 2026-07-14 | CDG2434 | - | Jul 14, 22:05 UTC | Jul 15, 21:10 UTC | 23h 4m |
| 2026-07-14 | CDG2433 | - | Jul 14, 19:15 UTC | Jul 14, 20:15 UTC | 1h 0m |
| 2026-07-08 | CDG2426 | - | Jul 8, 07:50 UTC | Jul 8, 20:20 UTC | 12h 30m |
| 2026-07-08 | CDG2423 | - | Jul 8, 05:00 UTC | Jul 8, 06:45 UTC | 1h 45m |
| 2026-07-07 | CDG2423 | - | Jul 7, 08:05 UTC | Jul 8, 06:45 UTC | 22h 40m |
| 2026-07-07 | CDG2423 | - | Jul 7, 05:25 UTC | Jul 7, 06:55 UTC | 1h 30m |
| 2026-07-06 | CDG2424 | - | Jul 6, 05:50 UTC | Jul 6, 06:15 UTC | 25m |
| 2026-07-06 | CDG2423 | - | Jul 6, 03:00 UTC | Jul 6, 04:40 UTC | 1h 40m |
| 2026-07-05 | CDG2426 | - | Jul 5, 05:20 UTC | Jul 5, 21:35 UTC | 16h 15m |
| 2026-07-05 | CDG2423 | - | Jul 5, 03:30 UTC | Jul 5, 03:55 UTC | 25m |
| 2026-07-04 | CDG2424 | - | Jul 4, 04:30 UTC | Jul 5, 03:55 UTC | 23h 25m |
| 2026-07-04 | CDG2423 | - | Jul 4, 02:55 UTC | Jul 4, 03:25 UTC | 30m |
| 2026-07-03 | CDG2426 | - | Jul 3, 16:20 UTC | Jul 4, 02:20 UTC | 10h 0m |
| 2026-07-02 | CDG2424 | - | Jul 2, 05:20 UTC | Jul 2, 06:20 UTC | 1h 0m |
| 2026-07-02 | CDG2423 | - | Jul 2, 03:55 UTC | Jul 2, 04:20 UTC | 25m |
| 2026-07-01 | CDG2426 | - | Jul 1, 15:55 UTC | Jul 2, 03:15 UTC | 11h 20m |
| 2026-07-01 | CDG2424 | - | Jul 1, 04:50 UTC | Jul 1, 06:05 UTC | 1h 15m |
| 2026-07-01 | CDG2423 | - | Jul 1, 02:55 UTC | Jul 1, 03:20 UTC | 25m |
| 2026-06-30 | CDG2424 | - | Jun 30, 04:15 UTC | Jun 30, 04:40 UTC | 25m |
| 2026-06-30 | CDG2423 | - | Jun 30, 02:45 UTC | Jun 30, 03:05 UTC | 20m |
| 2026-06-29 | CDG2424 | - | Jun 29, 04:30 UTC | Jun 30, 01:50 UTC | 21h 20m |
| 2026-06-29 | CDG2423 | - | Jun 29, 02:35 UTC | Jun 29, 03:29 UTC | 55m |
| 2026-06-28 | CDG2426 | - | Jun 28, 04:20 UTC | Jun 28, 21:45 UTC | 17h 25m |
| 2026-06-28 | CDG2423 | - | Jun 28, 02:34 UTC | Jun 28, 02:54 UTC | 20m |
| 2026-06-27 | CDG2424 | - | Jun 27, 04:29 UTC | Jun 28, 02:54 UTC | 22h 25m |
| 2026-06-27 | CDG2423 | - | Jun 27, 02:55 UTC | Jun 27, 03:20 UTC | 25m |
| 2026-06-26 | CDG2426 | - | Jun 26, 04:10 UTC | Jun 26, 21:04 UTC | 16h 55m |
| 2026-06-25 | CDG2423 | - | Jun 25, 11:19 UTC | Jun 26, 03:05 UTC | 15h 45m |
| 2026-06-25 | CDG242A | - | Jun 25, 08:45 UTC | Jun 25, 10:20 UTC | 1h 35m |
| 2026-06-25 | CDG2424 | - | Jun 25, 03:15 UTC | Jun 25, 03:59 UTC | 45m |
| 2026-06-25 | CDG2423 | - | Jun 25, 01:24 UTC | Jun 25, 02:10 UTC | 45m |
| 2026-06-24 | CDG2423 | - | Jun 24, 02:30 UTC | Jun 25, 01:59 UTC | 23h 30m |
| 2026-06-23 | CDG2423 | - | Jun 23, 04:14 UTC | Jun 24, 03:35 UTC | 23h 20m |
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-5111 page for operator, model, and routing details .