sensors Mode-S transponder
71BF55
ICAO 24-bit transponder address · allocated to Korea, South
Currently assigned to HL7755 · BOEING 777-200
- Hex
- 71BF55
- Octal
- 34337525
- Decimal
- 7,454,549
- Country
- KR
- Tail
- HL7755
- Type
- B772
- Flights observed
- 103
- Distinct callsigns
- 20
- Country
- KR
- Last broadcast
- 10d ago
Last known position
Country allocation
The ICAO 24-bit address 71BF55 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 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| AAR703 | Asiana Airlines | 12 | 2026-05-10 |
| AAR371 | Asiana Airlines | 12 | 2026-05-14 |
| AAR372 | Asiana Airlines | 11 | 2026-05-14 |
| AAR704 | Asiana Airlines | 10 | 2026-05-10 |
| AAR602 | Asiana Airlines | 9 | 2026-05-02 |
| AAR601 | Asiana Airlines | 9 | 2026-05-02 |
| AAR562 | Asiana Airlines | 6 | 2026-04-22 |
| AAR561 | Asiana Airlines | 4 | 2026-04-21 |
| AAR232 | Asiana Airlines | 4 | 2026-04-24 |
| AAR730 | Asiana Airlines | 3 | 2026-05-17 |
| AAR712 | Asiana Airlines | 2 | 2026-05-19 |
| AAR7113 | Asiana Airlines | 2 | 2026-05-19 |
| AAR370 | Asiana Airlines | 2 | 2026-04-16 |
| AAR334 | Asiana Airlines | 2 | 2026-04-27 |
| AAR301 | - | 2 | 2026-05-15 |
| AAR231 | Asiana Airlines | 2 | 2026-04-24 |
| AAR729 | Asiana Airlines | 1 | 2026-05-13 |
| AAR714 | Asiana Airlines | 1 | 2026-05-12 |
| AAR713 | Asiana Airlines | 1 | 2026-05-12 |
| AAR711 | Asiana Airlines | 1 | 2026-05-16 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-19 | AAR712 | TPE → ICN | May 19, 06:50 UTC | May 19, 08:50 UTC | 2h 0m |
| 2026-05-19 | AAR7113 | ICN → TPE | May 19, 03:40 UTC | May 19, 04:05 UTC | 25m |
| 2026-05-19 | AAR7113 | ICN → TPE | May 19, 02:05 UTC | May 19, 02:30 UTC | 25m |
| 2026-05-17 | AAR730 | SGN → PUS | May 17, 00:45 UTC | May 17, 10:35 UTC | 9h 50m |
| 2026-05-16 | AAR712 | TPE → ICN | May 16, 04:50 UTC | May 16, 07:01 UTC | 2h 11m |
| 2026-05-16 | AAR711 | ICN → TPE | May 16, 00:05 UTC | May 16, 02:05 UTC | 2h 0m |
| 2026-05-15 | AAR302 | - | May 15, 03:55 UTC | May 15, 04:15 UTC | 20m |
| 2026-05-15 | AAR301 | - | May 15, 00:45 UTC | May 15, 01:05 UTC | 20m |
| 2026-05-14 | AAR372 | SZX → ICN | May 14, 09:00 UTC | May 14, 09:35 UTC | 35m |
| 2026-05-14 | AAR372 | SZX → ICN | May 14, 06:35 UTC | May 14, 06:45 UTC | 10m |
| 2026-05-14 | - | - | May 14, 04:25 UTC | May 14, 04:45 UTC | 20m |
| 2026-05-14 | AAR371 | ICN → SZX | May 14, 01:30 UTC | May 14, 02:10 UTC | 40m |
| 2026-05-13 | AAR729 | PUS → SGN | May 13, 00:50 UTC | May 13, 10:20 UTC | 9h 30m |
| 2026-05-12 | AAR714 | TPE → ICN | May 12, 09:20 UTC | May 12, 11:25 UTC | 2h 5m |
| 2026-05-12 | AAR713 | ICN → TPE | May 12, 05:20 UTC | May 12, 07:25 UTC | 2h 5m |
| 2026-05-11 | AAR372 | SZX → ICN | May 11, 08:55 UTC | May 11, 09:40 UTC | 45m |
| 2026-05-11 | AAR372 | SZX → ICN | May 11, 06:50 UTC | May 11, 07:00 UTC | 10m |
| 2026-05-11 | AAR371 | ICN → SZX | May 11, 04:35 UTC | May 11, 04:55 UTC | 20m |
| 2026-05-11 | AAR371 | ICN → SZX | May 11, 01:30 UTC | May 11, 02:10 UTC | 40m |
| 2026-05-10 | AAR704 | MNL → ICN | May 10, 16:34 UTC | May 10, 20:00 UTC | 3h 25m |
| 2026-05-10 | AAR703 | ICN → MNL | May 10, 11:05 UTC | May 10, 14:40 UTC | 3h 35m |
| 2026-05-10 | AAR301 | - | May 10, 00:39 UTC | May 10, 00:55 UTC | 15m |
| 2026-05-09 | AAR704 | MNL → ICN | May 9, 16:25 UTC | May 9, 19:49 UTC | 3h 25m |
| 2026-05-09 | AAR703 | ICN → MNL | May 9, 10:55 UTC | May 9, 14:25 UTC | 3h 30m |
| 2026-05-07 | AAR730 | SGN → PUS | May 7, 00:45 UTC | May 7, 10:25 UTC | 9h 40m |
| 2026-05-06 | AAR704 | MNL → ICN | May 6, 16:05 UTC | May 6, 19:35 UTC | 3h 29m |
| 2026-05-06 | AAR703 | ICN → MNL | May 6, 11:00 UTC | May 6, 14:30 UTC | 3h 30m |
| 2026-05-06 | AAR360 | HGH → ICN | May 6, 04:05 UTC | May 6, 09:05 UTC | 5h 0m |
| 2026-05-05 | AAR372 | SZX → ICN | May 5, 09:10 UTC | May 5, 09:55 UTC | 45m |
| 2026-05-05 | AAR372 | SZX → ICN | May 5, 07:00 UTC | May 5, 07:10 UTC | 10m |
| 2026-05-05 | AAR371 | ICN → SZX | May 5, 04:50 UTC | May 5, 05:00 UTC | 10m |
| 2026-05-05 | AAR371 | ICN → SZX | May 5, 01:45 UTC | May 5, 02:25 UTC | 40m |
| 2026-05-04 | AAR704 | MNL → ICN | May 4, 16:15 UTC | May 4, 19:20 UTC | 3h 6m |
| 2026-05-04 | AAR703 | ICN → MNL | May 4, 10:50 UTC | May 4, 14:30 UTC | 3h 40m |
| 2026-05-04 | AAR363 | ICN → PVG | May 4, 02:10 UTC | May 4, 07:15 UTC | 5h 5m |
| 2026-05-02 | AAR602 | SYD → ICN | May 2, 23:50 UTC | May 3, 09:45 UTC | 9h 54m |
| 2026-05-02 | AAR601 | ICN → SYD | May 2, 11:50 UTC | May 2, 21:45 UTC | 9h 55m |
| 2026-05-01 | AAR602 | SYD → ICN | May 1, 23:45 UTC | May 2, 09:55 UTC | 10h 11m |
| 2026-05-01 | AAR601 | ICN → SYD | May 1, 11:50 UTC | May 1, 21:35 UTC | 9h 45m |
| 2026-05-01 | AAR372 | SZX → ICN | May 1, 09:05 UTC | May 1, 09:50 UTC | 45m |
| 2026-05-01 | AAR371 | ICN → SZX | May 1, 01:30 UTC | May 1, 02:05 UTC | 35m |
| 2026-04-30 | AAR602 | SYD → ICN | Apr 30, 00:20 UTC | Apr 30, 10:25 UTC | 10h 5m |
| 2026-04-29 | AAR601 | ICN → SYD | Apr 29, 12:40 UTC | Apr 29, 22:25 UTC | 9h 45m |
| 2026-04-29 | AAR372 | SZX → ICN | Apr 29, 10:05 UTC | Apr 29, 10:40 UTC | 35m |
| 2026-04-29 | AAR371 | ICN → SZX | Apr 29, 04:55 UTC | Apr 29, 05:20 UTC | 25m |
| 2026-04-29 | AAR371 | ICN → SZX | Apr 29, 01:45 UTC | Apr 29, 02:24 UTC | 40m |
| 2026-04-27 | AAR602 | SYD → ICN | Apr 27, 23:45 UTC | Apr 28, 10:15 UTC | 10h 30m |
| 2026-04-27 | AAR601 | ICN → SYD | Apr 27, 20:25 UTC | Apr 27, 21:35 UTC | 1h 10m |
| 2026-04-27 | AAR601 | ICN → SYD | Apr 27, 11:45 UTC | Apr 27, 12:30 UTC | 45m |
| 2026-04-27 | AAR334 | PEK → ICN | Apr 27, 08:55 UTC | Apr 27, 09:15 UTC | 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 HL7755 page for operator, model, and routing details .