sensors Mode-S transponder
0AC424
ICAO 24-bit transponder address · allocated to Costa Rica
Currently assigned to HK-5313 · ATR-42-600
- Hex
- 0AC424
- Octal
- 02542044
- Decimal
- 705,572
- Country
- CR
- Tail
- HK-5313
- Type
- AT46
- Flights observed
- 35
- Distinct callsigns
- 19
- Country
- CR
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 0AC424 falls within the block assigned to Costa Rica (CR) by ICAO Annex 10, Volume III. Every aircraft registered in Costa Rica 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 19 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| EFY7820 | EasyFly | 6 | 2026-05-29 |
| EFY7821 | EasyFly | 5 | 2026-05-29 |
| EFY7772 | EasyFly | 3 | 2026-05-21 |
| EFY9127 | EasyFly | 2 | 2026-05-30 |
| EFY9114 | EasyFly | 2 | 2026-06-01 |
| EFY9113 | EasyFly | 2 | 2026-06-01 |
| EFY9110 | EasyFly | 2 | 2026-06-01 |
| EFY7773 | EasyFly | 2 | 2026-05-16 |
| EFY9128 | EasyFly | 1 | 2026-05-23 |
| EFY9126 | EasyFly | 1 | 2026-05-30 |
| EFY9125 | EasyFly | 1 | 2026-05-30 |
| EFY9109 | - | 1 | 2026-04-13 |
| EFY9045 | EasyFly | 1 | 2026-05-31 |
| EFY9044 | EasyFly | 1 | 2026-05-31 |
| EFY9027 | EasyFly | 1 | 2026-06-01 |
| EFY9026 | EasyFly | 1 | 2026-05-31 |
| EFY9021 | EasyFly | 1 | 2026-05-31 |
| EFY9020 | EasyFly | 1 | 2026-05-31 |
| EFY7838 | EasyFly | 1 | 2026-05-30 |
Recent flights last 35
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-01 | EFY9114 | BOG → EOH | Jun 1, 16:15 UTC | Jun 1, 16:30 UTC | 15m |
| 2026-06-01 | EFY9113 | EOH → BOG | Jun 1, 15:05 UTC | Jun 1, 15:25 UTC | 20m |
| 2026-06-01 | EFY9110 | BOG → EOH | Jun 1, 13:25 UTC | Jun 1, 13:45 UTC | 20m |
| 2026-06-01 | EFY9027 | EYP → BOG | Jun 1, 00:35 UTC | Jun 1, 00:55 UTC | 20m |
| 2026-05-31 | EFY9026 | BOG → EYP | May 31, 23:00 UTC | May 31, 23:15 UTC | 15m |
| 2026-05-31 | EFY9021 | EYP → BOG | May 31, 21:40 UTC | May 31, 22:10 UTC | 30m |
| 2026-05-31 | EFY9020 | BOG → EYP | May 31, 20:00 UTC | May 31, 20:10 UTC | 10m |
| 2026-05-31 | EFY9045 | NVA → BOG | May 31, 18:35 UTC | May 31, 19:00 UTC | 25m |
| 2026-05-31 | EFY9044 | BOG → NVA | May 31, 16:40 UTC | May 31, 16:50 UTC | 10m |
| 2026-05-30 | EFY7838 | BOG → MZL | May 30, 21:45 UTC | May 30, 22:00 UTC | 15m |
| 2026-05-30 | EFY9127 | EOH → BOG | May 30, 20:20 UTC | May 30, 20:35 UTC | 15m |
| 2026-05-30 | EFY9126 | BOG → EOH | May 30, 18:35 UTC | May 30, 18:50 UTC | 15m |
| 2026-05-30 | EFY9125 | EOH → BOG | May 30, 17:30 UTC | May 30, 17:45 UTC | 15m |
| 2026-05-29 | EFY7821 | VVC → EOH | May 29, 19:45 UTC | May 29, 20:10 UTC | 25m |
| 2026-05-29 | EFY7820 | EOH → VVC | May 29, 18:30 UTC | May 29, 18:50 UTC | 20m |
| 2026-05-24 | EFY7820 | EOH → VVC | May 24, 15:30 UTC | May 24, 15:50 UTC | 20m |
| 2026-05-23 | EFY9128 | BOG → EOH | May 23, 21:50 UTC | May 23, 22:10 UTC | 20m |
| 2026-05-23 | EFY9127 | EOH → BOG | May 23, 20:40 UTC | May 23, 20:55 UTC | 15m |
| 2026-05-21 | EFY7772 | CLO → VVC | May 21, 16:25 UTC | May 21, 16:45 UTC | 20m |
| 2026-05-16 | EFY7773 | VVC → CLO | May 16, 22:20 UTC | May 16, 22:35 UTC | 15m |
| 2026-05-16 | EFY7772 | CLO → VVC | May 16, 20:05 UTC | May 16, 20:20 UTC | 15m |
| 2026-05-14 | EFY7773 | VVC → CLO | May 14, 18:05 UTC | May 14, 18:15 UTC | 10m |
| 2026-05-14 | EFY7772 | CLO → VVC | May 14, 16:35 UTC | May 14, 16:55 UTC | 20m |
| 2026-04-26 | EFY7821 | VVC → EOH | Apr 26, 16:40 UTC | Apr 26, 17:05 UTC | 25m |
| 2026-04-26 | EFY7820 | EOH → VVC | Apr 26, 15:20 UTC | Apr 26, 15:40 UTC | 20m |
| 2026-04-24 | EFY7821 | VVC → EOH | Apr 24, 20:15 UTC | Apr 24, 20:40 UTC | 25m |
| 2026-04-24 | EFY7820 | EOH → VVC | Apr 24, 19:00 UTC | Apr 24, 19:20 UTC | 20m |
| 2026-04-22 | EFY9114 | BOG → EOH | Apr 22, 15:35 UTC | Apr 22, 16:00 UTC | 25m |
| 2026-04-22 | EFY9113 | EOH → BOG | Apr 22, 14:20 UTC | Apr 22, 14:30 UTC | 10m |
| 2026-04-20 | EFY7821 | VVC → EOH | Apr 20, 19:10 UTC | Apr 20, 19:35 UTC | 25m |
| 2026-04-20 | EFY7820 | EOH → VVC | Apr 20, 17:55 UTC | Apr 20, 18:15 UTC | 20m |
| 2026-04-13 | EFY7821 | - | Apr 13, 20:20 UTC | Apr 13, 20:40 UTC | 20m |
| 2026-04-13 | EFY7820 | - | Apr 13, 19:05 UTC | Apr 13, 19:25 UTC | 20m |
| 2026-04-13 | EFY9110 | - | Apr 13, 13:00 UTC | Apr 13, 13:20 UTC | 20m |
| 2026-04-13 | EFY9109 | - | Apr 13, 11:40 UTC | Apr 13, 11:50 UTC | 10m |
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 HK-5313 page for operator, model, and routing details .