sensors Mode-S transponder
71E250
ICAO 24-bit transponder address · allocated to Korea, South
- Hex
- 71E250
- Octal
- 34361120
- Decimal
- 7,463,504
- Country
- KR
- Flights observed
- 58
- Distinct callsigns
- 1
- Country
- KR
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address 71E250 falls within the block assigned to Korea, South (KR) by ICAO Annex 10, Volume III. Every aircraft registered in Korea, South 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 1 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| HLC250 | - | 55 | 2026-07-16 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-16 | HLC250 | - | Jul 16, 03:50 UTC | Jul 16, 04:20 UTC | 30m |
| 2026-07-11 | HLC250 | - | Jul 11, 05:10 UTC | Jul 11, 05:45 UTC | 35m |
| 2026-07-03 | HLC250 | - | Jul 3, 07:35 UTC | Jul 3, 07:55 UTC | 20m |
| 2026-07-03 | - | - | Jul 3, 05:45 UTC | Jul 3, 05:55 UTC | 10m |
| 2026-06-28 | HLC250 | - | Jun 28, 05:15 UTC | Jun 28, 05:55 UTC | 40m |
| 2026-06-27 | HLC250 | - | Jun 27, 02:04 UTC | Jun 27, 02:55 UTC | 50m |
| 2026-06-24 | HLC250 | - | Jun 24, 03:19 UTC | Jun 24, 03:35 UTC | 15m |
| 2026-06-18 | HLC250 | - | Jun 18, 06:50 UTC | Jun 18, 07:20 UTC | 30m |
| 2026-06-14 | HLC250 | - | Jun 14, 07:45 UTC | Jun 14, 08:45 UTC | 1h 0m |
| 2026-06-14 | HLC250 | - | Jun 14, 06:30 UTC | Jun 14, 06:55 UTC | 25m |
| 2026-06-14 | HLC250 | - | Jun 14, 01:00 UTC | Jun 14, 02:25 UTC | 1h 25m |
| 2026-06-13 | HLC250 | - | Jun 13, 07:10 UTC | Jun 13, 07:35 UTC | 25m |
| 2026-06-13 | HLC250 | - | Jun 13, 04:40 UTC | Jun 13, 05:15 UTC | 35m |
| 2026-06-13 | HLC250 | - | Jun 13, 01:35 UTC | Jun 13, 02:30 UTC | 55m |
| 2026-05-14 | HLC250 | - | May 14, 09:35 UTC | May 14, 10:00 UTC | 25m |
| 2026-05-14 | HLC250 | - | May 14, 07:50 UTC | May 14, 08:20 UTC | 30m |
| 2026-05-14 | HLC250 | - | May 14, 01:10 UTC | May 14, 02:20 UTC | 1h 10m |
| 2026-05-13 | HLC250 | - | May 13, 23:45 UTC | May 14, 00:20 UTC | 35m |
| 2026-05-13 | HLC250 | - | May 13, 08:40 UTC | May 13, 09:20 UTC | 40m |
| 2026-05-13 | HLC250 | - | May 13, 05:50 UTC | May 13, 07:05 UTC | 1h 15m |
| 2026-05-13 | HLC250 | - | May 13, 02:30 UTC | May 13, 03:20 UTC | 50m |
| 2026-05-10 | HLC250 | - | May 10, 23:50 UTC | May 11, 00:15 UTC | 25m |
| 2026-05-10 | HLC250 | - | May 10, 21:44 UTC | May 10, 22:49 UTC | 1h 5m |
| 2026-05-10 | HLC250 | - | May 10, 07:04 UTC | May 10, 07:34 UTC | 30m |
| 2026-05-10 | HLC250 | - | May 10, 02:14 UTC | May 10, 02:34 UTC | 20m |
| 2026-05-10 | HLC250 | - | May 10, 00:45 UTC | May 10, 00:55 UTC | 10m |
| 2026-05-09 | HLC250 | - | May 9, 22:55 UTC | May 10, 00:09 UTC | 1h 15m |
| 2026-05-09 | HLC250 | - | May 9, 02:55 UTC | May 9, 03:30 UTC | 35m |
| 2026-05-07 | HLC250 | - | May 7, 22:25 UTC | May 7, 22:54 UTC | 29m |
| 2026-05-07 | HLC250 | - | May 7, 02:45 UTC | May 7, 03:35 UTC | 50m |
| 2026-05-07 | HLC250 | - | May 7, 01:05 UTC | May 7, 01:55 UTC | 50m |
| 2026-05-06 | HLC250 | - | May 6, 23:15 UTC | May 7, 00:00 UTC | 45m |
| 2026-05-05 | HLC250 | - | May 5, 09:20 UTC | May 5, 10:10 UTC | 50m |
| 2026-05-05 | HLC250 | - | May 5, 07:05 UTC | May 5, 07:35 UTC | 30m |
| 2026-05-05 | HLC250 | - | May 5, 05:10 UTC | May 5, 05:35 UTC | 25m |
| 2026-05-05 | HLC250 | - | May 5, 02:45 UTC | May 5, 03:10 UTC | 25m |
| 2026-05-05 | HLC250 | - | May 5, 00:10 UTC | May 5, 01:00 UTC | 50m |
| 2026-05-02 | HLC250 | - | May 2, 07:20 UTC | May 2, 08:05 UTC | 45m |
| 2026-05-02 | HLC250 | - | May 2, 04:15 UTC | May 2, 05:40 UTC | 1h 25m |
| 2026-05-01 | HLC250 | - | May 1, 00:30 UTC | May 1, 01:10 UTC | 40m |
| 2026-04-30 | HLC250 | - | Apr 30, 06:55 UTC | Apr 30, 08:10 UTC | 1h 15m |
| 2026-04-30 | - | - | Apr 30, 02:20 UTC | Apr 30, 02:40 UTC | 20m |
| 2026-04-28 | HLC250 | - | Apr 28, 06:40 UTC | Apr 28, 06:55 UTC | 15m |
| 2026-04-25 | HLC250 | - | Apr 25, 02:25 UTC | Apr 25, 03:05 UTC | 40m |
| 2026-04-24 | HLC250 | - | Apr 24, 09:25 UTC | Apr 24, 09:40 UTC | 15m |
| 2026-04-24 | HLC250 | - | Apr 24, 07:25 UTC | Apr 24, 08:05 UTC | 40m |
| 2026-04-23 | HLC250 | - | Apr 23, 08:25 UTC | Apr 23, 09:30 UTC | 1h 5m |
| 2026-04-21 | HLC250 | - | Apr 21, 05:45 UTC | Apr 21, 06:00 UTC | 15m |
| 2026-04-17 | HLC250 | - | Apr 17, 05:50 UTC | Apr 17, 06:35 UTC | 45m |
| 2026-04-16 | HLC250 | - | Apr 16, 09:10 UTC | Apr 16, 09:35 UTC | 25m |
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.