sensors Mode-S transponder
781F14
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-223H · BOEING 737-800
- Hex
- 781F14
- Octal
- 36017424
- Decimal
- 7,872,276
- Country
- CN
- Tail
- B-223H
- Type
- B738
- Flights observed
- 57
- Distinct callsigns
- 4
- Country
- CN
- Last broadcast
- 1d ago
Current position
Country allocation
The ICAO 24-bit address 781F14 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 4 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-01 | CTJ3868 | - | Jun 1, 19:20 UTC | Jun 1, 20:10 UTC | 50m |
| 2026-06-01 | CTJ3867 | - | Jun 1, 17:15 UTC | Jun 1, 18:20 UTC | 1h 5m |
| 2026-05-29 | CTJ3868 | - | May 29, 19:05 UTC | May 29, 19:55 UTC | 50m |
| 2026-05-29 | CTJ3867 | - | May 29, 17:15 UTC | May 29, 17:55 UTC | 40m |
| 2026-05-28 | CTJ3868 | - | May 28, 19:05 UTC | May 29, 17:55 UTC | 22h 50m |
| 2026-05-28 | CTJ3867 | - | May 28, 17:20 UTC | May 28, 18:05 UTC | 45m |
| 2026-05-27 | CTJ3868 | KIX → KIX | May 27, 19:10 UTC | May 28, 18:05 UTC | 22h 55m |
| 2026-05-27 | CTJ3867 | - | May 27, 17:15 UTC | May 27, 18:00 UTC | 45m |
| 2026-05-26 | CTJ3868 | - | May 26, 19:10 UTC | May 27, 18:00 UTC | 22h 50m |
| 2026-05-26 | CTJ3867 | - | May 26, 17:25 UTC | May 26, 18:05 UTC | 40m |
| 2026-05-25 | CTJ3868 | KIX → KIX | May 25, 21:24 UTC | May 26, 18:05 UTC | 20h 40m |
| 2026-05-25 | CTJ3867 | - | May 25, 19:30 UTC | May 25, 20:15 UTC | 45m |
| 2026-05-22 | CTJ3868 | - | May 22, 18:55 UTC | May 22, 19:45 UTC | 50m |
| 2026-05-22 | CTJ3867 | - | May 22, 17:10 UTC | May 22, 17:50 UTC | 40m |
| 2026-05-21 | CTJ3868 | KIX → KIX | May 21, 20:00 UTC | May 22, 17:50 UTC | 21h 50m |
| 2026-05-21 | CTJ3867 | - | May 21, 18:10 UTC | May 21, 18:55 UTC | 45m |
| 2026-05-20 | CTJ3868 | KIX → KIX | May 20, 19:05 UTC | May 21, 18:55 UTC | 23h 50m |
| 2026-05-20 | CTJ3867 | - | May 20, 17:20 UTC | May 20, 18:05 UTC | 45m |
| 2026-05-19 | CTJ3867 | - | May 19, 19:05 UTC | May 20, 18:05 UTC | 23h 1m |
| 2026-05-19 | CTJ3868 | KIX → KIX | May 19, 03:10 UTC | May 19, 18:00 UTC | 14h 50m |
| 2026-05-19 | CTJ3867 | - | May 19, 01:10 UTC | May 19, 01:55 UTC | 45m |
| 2026-05-15 | CTJ3868 | - | May 15, 19:20 UTC | May 15, 20:00 UTC | 40m |
| 2026-05-15 | CTJ3867 | - | May 15, 17:20 UTC | May 15, 18:10 UTC | 50m |
| 2026-05-14 | CTJ3867 | KIX → KIX | May 14, 19:10 UTC | May 15, 18:10 UTC | 22h 59m |
| 2026-05-14 | CTJ3867 | - | May 14, 17:30 UTC | May 14, 18:15 UTC | 45m |
| 2026-05-13 | CTJ3868 | - | May 13, 19:15 UTC | May 14, 18:15 UTC | 23h 0m |
| 2026-05-13 | CTJ3867 | - | May 13, 17:20 UTC | May 13, 18:00 UTC | 40m |
| 2026-05-12 | CTJ3868 | KIX → KIX | May 12, 19:25 UTC | May 13, 18:00 UTC | 22h 35m |
| 2026-05-12 | CTJ3867 | - | May 12, 17:25 UTC | May 12, 18:10 UTC | 45m |
| 2026-05-11 | CTJ3868 | KIX → KIX | May 11, 19:15 UTC | May 12, 18:10 UTC | 22h 55m |
| 2026-05-11 | CTJ3867 | - | May 11, 17:25 UTC | May 11, 18:05 UTC | 40m |
| 2026-05-09 | CTJ3805 | - | May 9, 19:45 UTC | May 9, 20:00 UTC | 15m |
| 2026-05-09 | - | - | May 9, 00:55 UTC | May 9, 01:05 UTC | 10m |
| 2026-05-08 | CTJ3805 | - | May 8, 19:40 UTC | May 8, 19:50 UTC | 10m |
| 2026-05-06 | CTJ3805 | - | May 6, 19:55 UTC | May 6, 20:10 UTC | 15m |
| 2026-04-30 | CTJ3805 | - | Apr 30, 19:40 UTC | Apr 30, 19:50 UTC | 10m |
| 2026-04-29 | CTJ3805 | - | Apr 29, 20:00 UTC | Apr 29, 20:10 UTC | 10m |
| 2026-04-29 | CTJ3806 | - | Apr 29, 02:09 UTC | Apr 29, 02:24 UTC | 15m |
| 2026-04-28 | CTJ3805 | - | Apr 28, 19:55 UTC | Apr 28, 20:10 UTC | 15m |
| 2026-04-27 | CTJ3805 | - | Apr 27, 19:55 UTC | Apr 27, 20:05 UTC | 10m |
| 2026-04-25 | CTJ3806 | - | Apr 25, 01:20 UTC | Apr 25, 01:50 UTC | 30m |
| 2026-04-23 | CTJ3868 | - | Apr 23, 21:50 UTC | Apr 23, 22:40 UTC | 50m |
| 2026-04-23 | CTJ3867 | - | Apr 23, 17:25 UTC | Apr 23, 17:50 UTC | 25m |
| 2026-04-22 | CTJ3868 | - | Apr 22, 19:05 UTC | Apr 23, 17:50 UTC | 22h 45m |
| 2026-04-22 | CTJ3867 | - | Apr 22, 17:10 UTC | Apr 22, 17:35 UTC | 25m |
| 2026-04-21 | CTJ3868 | - | Apr 21, 19:10 UTC | Apr 22, 17:35 UTC | 22h 25m |
| 2026-04-21 | CTJ3867 | - | Apr 21, 17:10 UTC | Apr 21, 17:35 UTC | 25m |
| 2026-04-20 | CTJ3868 | - | Apr 20, 19:30 UTC | Apr 21, 17:35 UTC | 22h 5m |
| 2026-04-20 | CTJ3867 | - | Apr 20, 17:30 UTC | Apr 20, 17:55 UTC | 25m |
| 2026-04-17 | CTJ3868 | - | Apr 17, 03:25 UTC | Apr 17, 04:10 UTC | 45m |
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-223H page for operator, model, and routing details .