sensors Mode-S transponder
781DF2
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-221T · BOEING 757-200
- Hex
- 781DF2
- Octal
- 36016762
- Decimal
- 7,871,986
- Country
- CN
- Tail
- B-221T
- Type
- B752
- Flights observed
- 133
- Distinct callsigns
- 10
- Country
- CN
- Last broadcast
- 17d ago
Last known position
Country allocation
The ICAO 24-bit address 781DF2 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 10 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| HYT9129 | - | 21 | 2026-06-29 |
| HYT9103 | - | 19 | 2026-06-12 |
| HYT9157 | - | 18 | 2026-06-24 |
| HYT9068 | - | 15 | 2026-06-11 |
| HYT9130 | - | 14 | 2026-06-23 |
| HYT9089 | YTO Cargo Ltd | 14 | 2026-05-30 |
| HYT9104 | YTO Cargo Ltd | 11 | 2026-06-12 |
| HYT9090 | YTO Cargo Ltd | 8 | 2026-05-30 |
| HYT9067 | YTO Cargo Ltd | 7 | 2026-06-02 |
| HYT9158 | - | 6 | 2026-06-24 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-29 | HYT9129 | - | Jun 29, 23:54 UTC | Jun 30, 07:55 UTC | 8h 1m |
| 2026-06-29 | HYT9129 | - | Jun 29, 05:20 UTC | Jun 30, 02:05 UTC | 20h 46m |
| 2026-06-29 | HYT9129 | - | Jun 29, 00:34 UTC | Jun 30, 00:30 UTC | 23h 55m |
| 2026-06-28 | HYT9129 | - | Jun 28, 23:54 UTC | Jun 29, 07:30 UTC | 7h 35m |
| 2026-06-28 | HYT9129 | - | Jun 28, 06:34 UTC | Jun 29, 06:29 UTC | 23h 55m |
| 2026-06-28 | HYT9129 | - | Jun 28, 05:29 UTC | Jun 29, 02:05 UTC | 20h 35m |
| 2026-06-28 | HYT9129 | - | Jun 28, 00:45 UTC | Jun 29, 00:29 UTC | 23h 45m |
| 2026-06-26 | HYT9129 | - | Jun 26, 00:20 UTC | Jun 26, 07:50 UTC | 7h 30m |
| 2026-06-24 | HYT9158 | - | Jun 24, 06:55 UTC | Jun 24, 09:15 UTC | 2h 20m |
| 2026-06-24 | HYT9157 | - | Jun 24, 03:00 UTC | Jun 24, 05:15 UTC | 2h 15m |
| 2026-06-23 | HYT9157 | - | Jun 23, 06:34 UTC | Jun 24, 05:15 UTC | 22h 40m |
| 2026-06-23 | HYT9130 | - | Jun 23, 00:24 UTC | Jun 23, 07:25 UTC | 7h 0m |
| 2026-06-16 | HYT9129 | - | Jun 16, 00:45 UTC | Jun 16, 07:15 UTC | 6h 30m |
| 2026-06-15 | HYT9129 | - | Jun 15, 08:35 UTC | Jun 16, 07:15 UTC | 22h 40m |
| 2026-06-15 | HYT9158 | DEL → KMG | Jun 15, 06:45 UTC | Jun 16, 06:30 UTC | 23h 45m |
| 2026-06-15 | HYT9157 | - | Jun 15, 02:10 UTC | Jun 15, 04:50 UTC | 2h 40m |
| 2026-06-14 | HYT9157 | - | Jun 14, 06:35 UTC | Jun 15, 04:50 UTC | 22h 14m |
| 2026-06-14 | HYT9130 | - | Jun 14, 06:00 UTC | Jun 15, 04:30 UTC | 22h 29m |
| 2026-06-14 | HYT9130 | - | Jun 14, 00:35 UTC | Jun 14, 07:55 UTC | 7h 20m |
| 2026-06-12 | HYT9104 | BOM → KMG | Jun 12, 07:45 UTC | Jun 12, 10:10 UTC | 2h 25m |
| 2026-06-12 | HYT9103 | - | Jun 12, 05:25 UTC | Jun 12, 05:45 UTC | 20m |
| 2026-06-11 | HYT9068 | - | Jun 11, 09:05 UTC | Jun 12, 03:40 UTC | 18h 36m |
| 2026-06-11 | HYT9068 | - | Jun 11, 06:50 UTC | Jun 12, 03:40 UTC | 20h 51m |
| 2026-06-11 | HYT9068 | - | Jun 11, 01:35 UTC | Jun 11, 10:05 UTC | 8h 30m |
| 2026-06-09 | HYT9068 | - | Jun 9, 01:50 UTC | Jun 9, 09:40 UTC | 7h 50m |
| 2026-06-08 | HYT9068 | - | Jun 8, 10:35 UTC | Jun 9, 09:40 UTC | 23h 5m |
| 2026-06-08 | HYT9104 | BOM → KMG | Jun 8, 09:55 UTC | Jun 9, 08:30 UTC | 22h 35m |
| 2026-06-08 | HYT9103 | KMG → BOM | Jun 8, 06:00 UTC | Jun 8, 06:40 UTC | 40m |
| 2026-06-07 | HYT9104 | BOM → KMG | Jun 7, 09:30 UTC | Jun 8, 04:20 UTC | 18h 50m |
| 2026-06-07 | HYT9104 | BOM → KMG | Jun 7, 07:40 UTC | Jun 8, 04:20 UTC | 20h 40m |
| 2026-06-07 | HYT9103 | KMG → BOM | Jun 7, 05:35 UTC | Jun 7, 05:55 UTC | 20m |
| 2026-06-07 | HYT9103 | KMG → BOM | Jun 7, 03:10 UTC | Jun 7, 03:50 UTC | 40m |
| 2026-06-05 | HYT9104 | BOM → KMG | Jun 5, 07:45 UTC | Jun 5, 10:35 UTC | 2h 50m |
| 2026-06-05 | HYT9103 | KMG → BOM | Jun 5, 05:45 UTC | Jun 5, 06:05 UTC | 20m |
| 2026-06-04 | HYT9130 | MAA → KMG | Jun 4, 06:35 UTC | Jun 5, 04:05 UTC | 21h 30m |
| 2026-06-04 | HYT9129 | - | Jun 4, 00:45 UTC | Jun 4, 08:15 UTC | 7h 30m |
| 2026-06-03 | HYT9129 | - | Jun 3, 08:50 UTC | Jun 4, 08:15 UTC | 23h 25m |
| 2026-06-03 | HYT9068 | - | Jun 3, 06:45 UTC | Jun 4, 02:25 UTC | 19h 40m |
| 2026-06-03 | HYT9068 | - | Jun 3, 04:00 UTC | Jun 4, 02:25 UTC | 22h 25m |
| 2026-06-03 | HYT9068 | - | Jun 3, 01:40 UTC | Jun 3, 09:50 UTC | 8h 10m |
| 2026-06-02 | HYT9067 | KMG → KHI | Jun 2, 06:35 UTC | Jun 3, 04:10 UTC | 21h 35m |
| 2026-06-02 | HYT9130 | MAA → KMG | Jun 2, 05:35 UTC | Jun 3, 04:10 UTC | 22h 35m |
| 2026-06-02 | HYT9129 | - | Jun 2, 00:20 UTC | Jun 2, 07:30 UTC | 7h 10m |
| 2026-06-01 | HYT9129 | - | Jun 1, 08:35 UTC | Jun 2, 07:30 UTC | 22h 55m |
| 2026-06-01 | HYT9130 | MAA → KMG | Jun 1, 06:45 UTC | Jun 2, 05:50 UTC | 23h 5m |
| 2026-06-01 | HYT9129 | - | Jun 1, 03:15 UTC | Jun 2, 02:10 UTC | 22h 55m |
| 2026-06-01 | HYT9130 | MAA → KMG | Jun 1, 02:00 UTC | Jun 2, 00:25 UTC | 22h 25m |
| 2026-05-31 | HYT9130 | MAA → KMG | May 31, 08:45 UTC | Jun 1, 08:30 UTC | 23h 45m |
| 2026-05-30 | HYT9090 | LHE → KMG | May 30, 06:40 UTC | May 30, 09:45 UTC | 3h 5m |
| 2026-05-30 | HYT9089 | KMG → LHE | May 30, 02:06 UTC | May 30, 05:00 UTC | 2h 54m |
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-221T page for operator, model, and routing details .