sensors Mode-S transponder
78184A
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-30CP · AIRBUS A-320
- Hex
- 78184A
- Octal
- 36014112
- Decimal
- 7,870,538
- Country
- CN
- Tail
- B-30CP
- Type
- A320
- Flights observed
- 61
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 4h ago
Last known position
Country allocation
The ICAO 24-bit address 78184A 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 |
|---|---|---|---|
| UEA2713 | - | 17 | 2026-06-21 |
| UEA2714 | - | 7 | 2026-06-21 |
| UEA2227 | - | 5 | 2026-06-29 |
| UEA2250 | - | 3 | 2026-07-14 |
| UEA2249 | - | 3 | 2026-07-14 |
| UEA1822 | - | 3 | 2026-05-16 |
| UEA2264 | United Eagle Airlines | 2 | 2026-05-21 |
| UEA2254 | - | 2 | 2026-07-03 |
| UEA2253 | - | 2 | 2026-07-03 |
| UEA2244 | - | 2 | 2026-06-14 |
| UEA1870 | - | 2 | 2026-06-29 |
| UEA1869 | - | 2 | 2026-06-29 |
| UEA2868 | - | 1 | 2026-07-04 |
| UEA2867 | - | 1 | 2026-07-04 |
| UEA2817 | United Eagle Airlines | 1 | 2026-06-20 |
| UEA2720 | United Eagle Airlines | 1 | 2026-06-13 |
| UEA2442 | United Eagle Airlines | 1 | 2026-04-30 |
| UEA2413 | United Eagle Airlines | 1 | 2026-06-13 |
| UEA2288 | - | 1 | 2026-05-01 |
| UEA2242 | - | 1 | 2026-07-12 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | UEA2250 | - | Jul 14, 11:35 UTC | Jul 14, 12:00 UTC | 25m |
| 2026-07-14 | UEA2249 | - | Jul 14, 04:25 UTC | Jul 14, 04:40 UTC | 15m |
| 2026-07-12 | UEA2242 | - | Jul 12, 08:45 UTC | Jul 12, 08:55 UTC | 10m |
| 2026-07-10 | UEA2250 | - | Jul 10, 12:45 UTC | Jul 10, 12:55 UTC | 10m |
| 2026-07-10 | UEA2249 | - | Jul 10, 04:10 UTC | Jul 10, 04:30 UTC | 20m |
| 2026-07-09 | UEA2250 | - | Jul 9, 09:15 UTC | Jul 9, 09:25 UTC | 10m |
| 2026-07-09 | UEA2249 | - | Jul 9, 04:25 UTC | Jul 9, 04:45 UTC | 20m |
| 2026-07-04 | UEA2868 | - | Jul 4, 14:40 UTC | Jul 4, 16:10 UTC | 1h 30m |
| 2026-07-04 | UEA2867 | - | Jul 4, 03:30 UTC | Jul 4, 12:55 UTC | 9h 25m |
| 2026-07-03 | UEA2254 | - | Jul 3, 07:15 UTC | Jul 4, 03:40 UTC | 20h 25m |
| 2026-07-03 | UEA2254 | - | Jul 3, 04:55 UTC | Jul 3, 05:15 UTC | 20m |
| 2026-07-03 | UEA2253 | - | Jul 3, 03:05 UTC | Jul 3, 03:20 UTC | 15m |
| 2026-07-03 | UEA2253 | - | Jul 3, 00:30 UTC | Jul 3, 00:50 UTC | 20m |
| 2026-06-30 | UEA2228 | - | Jun 30, 08:55 UTC | Jun 30, 12:55 UTC | 4h 0m |
| 2026-06-29 | UEA2227 | - | Jun 29, 12:45 UTC | Jun 30, 06:00 UTC | 17h 16m |
| 2026-06-29 | UEA2227 | - | Jun 29, 09:10 UTC | Jun 30, 06:00 UTC | 20h 51m |
| 2026-06-29 | UEA1870 | - | Jun 29, 05:30 UTC | Jun 30, 01:45 UTC | 20h 16m |
| 2026-06-29 | UEA1869 | - | Jun 29, 01:05 UTC | Jun 29, 13:00 UTC | 11h 55m |
| 2026-06-21 | UEA2714 | - | Jun 21, 13:24 UTC | Jun 22, 06:35 UTC | 17h 10m |
| 2026-06-21 | UEA2714 | - | Jun 21, 09:20 UTC | Jun 22, 06:35 UTC | 21h 15m |
| 2026-06-21 | UEA2713 | - | Jun 21, 01:39 UTC | Jun 21, 13:34 UTC | 11h 55m |
| 2026-06-20 | UEA2713 | - | Jun 20, 09:24 UTC | Jun 21, 06:19 UTC | 20h 55m |
| 2026-06-20 | UEA2817 | SHE → WUT | Jun 20, 00:29 UTC | Jun 20, 00:49 UTC | 20m |
| 2026-06-16 | UEA2227 | - | Jun 16, 01:04 UTC | Jun 16, 13:19 UTC | 12h 15m |
| 2026-06-14 | UEA2244 | - | Jun 14, 06:25 UTC | Jun 14, 06:45 UTC | 20m |
| 2026-06-13 | UEA2720 | ZUH → TFU | Jun 13, 13:05 UTC | Jun 13, 13:25 UTC | 20m |
| 2026-06-13 | UEA2413 | TFU → HAK | Jun 13, 03:55 UTC | Jun 13, 06:20 UTC | 2h 24m |
| 2026-06-02 | UEA2714 | SYX → HFE | Jun 2, 08:35 UTC | Jun 2, 13:20 UTC | 4h 45m |
| 2026-05-31 | UEA1848 | - | May 31, 00:35 UTC | May 31, 00:45 UTC | 10m |
| 2026-05-30 | UEA2714 | SYX → HFE | May 30, 08:45 UTC | May 30, 13:15 UTC | 4h 30m |
| 2026-05-30 | UEA2713 | SHE → HFE | May 30, 06:15 UTC | May 30, 06:30 UTC | 15m |
| 2026-05-28 | UEA2713 | SHE → HFE | May 28, 01:50 UTC | May 28, 13:20 UTC | 11h 30m |
| 2026-05-27 | UEA2713 | SHE → HFE | May 27, 13:45 UTC | May 28, 09:30 UTC | 19h 45m |
| 2026-05-26 | UEA2713 | SHE → HFE | May 26, 05:34 UTC | May 26, 09:35 UTC | 4h 0m |
| 2026-05-26 | UEA2713 | SHE → HFE | May 26, 01:40 UTC | May 26, 01:49 UTC | 10m |
| 2026-05-24 | UEA2713 | SHE → HFE | May 24, 05:55 UTC | May 24, 09:50 UTC | 3h 55m |
| 2026-05-21 | UEA2264 | HGH → HAK | May 21, 07:20 UTC | May 21, 07:35 UTC | 15m |
| 2026-05-18 | UEA2264 | HGH → HAK | May 18, 07:00 UTC | May 18, 11:45 UTC | 4h 45m |
| 2026-05-16 | UEA1822 | - | May 16, 12:50 UTC | May 16, 14:51 UTC | 2h 0m |
| 2026-05-14 | UEA1822 | - | May 14, 14:55 UTC | May 14, 15:10 UTC | 15m |
| 2026-05-12 | UEA1822 | - | May 12, 12:55 UTC | May 12, 15:05 UTC | 2h 10m |
| 2026-05-01 | UEA2288 | - | May 1, 03:10 UTC | May 1, 07:15 UTC | 4h 5m |
| 2026-04-30 | UEA2442 | CSX → SHE | Apr 30, 06:20 UTC | May 1, 03:10 UTC | 20h 50m |
| 2026-04-28 | UEA2227 | - | Apr 28, 01:00 UTC | Apr 28, 06:25 UTC | 5h 25m |
| 2026-04-27 | UEA2244 | - | Apr 27, 06:25 UTC | Apr 27, 06:35 UTC | 10m |
| 2026-04-25 | UEA2714 | SYX → HFE | Apr 25, 13:25 UTC | Apr 26, 06:35 UTC | 17h 10m |
| 2026-04-25 | UEA2714 | SYX → HFE | Apr 25, 09:30 UTC | Apr 26, 06:35 UTC | 21h 5m |
| 2026-04-25 | UEA2713 | SHE → HFE | Apr 25, 01:35 UTC | Apr 25, 13:30 UTC | 11h 55m |
| 2026-04-24 | UEA2713 | SHE → HFE | Apr 24, 12:20 UTC | Apr 25, 09:30 UTC | 21h 10m |
| 2026-04-23 | UEA1858 | WUH → SHE | Apr 23, 15:00 UTC | Apr 24, 12:30 UTC | 21h 30m |
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-30CP page for operator, model, and routing details .