sensors Mode-S transponder
E072CF
ICAO 24-bit transponder address · allocated to Argentina
Currently assigned to LV-GKO · AIRBUS A-330-200
- Hex
- E072CF
- Octal
- 70071317
- Decimal
- 14,709,455
- Country
- AR
- Tail
- LV-GKO
- Type
- A332
- Flights observed
- 114
- Distinct callsigns
- 17
- Country
- AR
- Last broadcast
- 3h ago
Last known position
Country allocation
The ICAO 24-bit address E072CF falls within the block assigned to Argentina (AR) by ICAO Annex 10, Volume III. Every aircraft registered in Argentina 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 17 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| ARG1133 | - | 26 | 2026-07-11 |
| ARG1132 | - | 19 | 2026-07-11 |
| ARG1302 | - | 12 | 2026-07-14 |
| ARG1135 | - | 11 | 2026-07-06 |
| ARG1134 | Aerolineas Argentinas | 10 | 2026-07-05 |
| ARG1305 | - | 8 | 2026-07-10 |
| ARG1141 | - | 6 | 2026-06-21 |
| ARG1140 | - | 6 | 2026-06-20 |
| ARG1304 | - | 4 | 2026-07-12 |
| ARG1303 | - | 4 | 2026-07-12 |
| ARG1371 | Aerolineas Argentinas | 2 | 2026-05-01 |
| ARG1779 | - | 1 | 2026-07-13 |
| ARG1778 | - | 1 | 2026-07-13 |
| ARG1370 | Aerolineas Argentinas | 1 | 2026-05-01 |
| ARG1324 | Aerolineas Argentinas | 1 | 2026-05-02 |
| ARG1307 | - | 1 | 2026-07-05 |
| ARG1306 | - | 1 | 2026-07-04 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | ARG1302 | - | Jul 14, 02:10 UTC | Jul 14, 06:50 UTC | 4h 40m |
| 2026-07-13 | ARG1779 | - | Jul 13, 17:20 UTC | Jul 13, 19:00 UTC | 1h 40m |
| 2026-07-13 | ARG1778 | - | Jul 13, 14:10 UTC | Jul 13, 15:25 UTC | 1h 15m |
| 2026-07-12 | ARG1303 | - | Jul 12, 22:35 UTC | Jul 13, 07:20 UTC | 8h 45m |
| 2026-07-12 | ARG1304 | - | Jul 12, 10:30 UTC | Jul 12, 19:01 UTC | 8h 30m |
| 2026-07-11 | ARG1133 | - | Jul 11, 18:30 UTC | Jul 12, 07:10 UTC | 12h 40m |
| 2026-07-11 | ARG1132 | - | Jul 11, 03:05 UTC | Jul 11, 14:20 UTC | 11h 15m |
| 2026-07-10 | ARG1305 | - | Jul 10, 00:30 UTC | Jul 10, 09:00 UTC | 8h 30m |
| 2026-07-09 | ARG1302 | - | Jul 9, 02:00 UTC | Jul 9, 10:45 UTC | 8h 45m |
| 2026-07-08 | ARG1305 | MIA → EZE | Jul 8, 00:45 UTC | Jul 8, 09:15 UTC | 8h 30m |
| 2026-07-07 | ARG1302 | - | Jul 7, 05:50 UTC | Jul 7, 10:40 UTC | 4h 50m |
| 2026-07-07 | ARG1302 | - | Jul 7, 01:55 UTC | Jul 7, 02:40 UTC | 45m |
| 2026-07-06 | ARG1135 | MAD → EZE | Jul 6, 09:30 UTC | Jul 6, 21:40 UTC | 12h 10m |
| 2026-07-05 | ARG1134 | EZE → MAD | Jul 5, 18:25 UTC | Jul 6, 05:40 UTC | 11h 15m |
| 2026-07-05 | ARG1307 | - | Jul 5, 06:10 UTC | Jul 5, 14:10 UTC | 8h 0m |
| 2026-07-04 | ARG1306 | - | Jul 4, 18:30 UTC | Jul 5, 03:20 UTC | 8h 50m |
| 2026-07-03 | ARG1133 | MAD → EZE | Jul 3, 18:40 UTC | Jul 4, 07:15 UTC | 12h 35m |
| 2026-07-03 | ARG1132 | - | Jul 3, 03:35 UTC | Jul 3, 15:05 UTC | 11h 30m |
| 2026-07-01 | ARG1133 | MAD → EZE | Jul 1, 18:35 UTC | Jul 2, 06:55 UTC | 12h 20m |
| 2026-07-01 | ARG1132 | - | Jul 1, 03:15 UTC | Jul 1, 15:10 UTC | 11h 55m |
| 2026-06-29 | ARG1305 | MIA → EZE | Jun 29, 00:20 UTC | Jun 29, 09:00 UTC | 8h 40m |
| 2026-06-28 | ARG1302 | - | Jun 28, 02:05 UTC | Jun 28, 10:55 UTC | 8h 50m |
| 2026-06-26 | ARG1305 | MIA → EZE | Jun 26, 22:44 UTC | Jun 27, 07:19 UTC | 8h 35m |
| 2026-06-26 | ARG1302 | - | Jun 26, 02:00 UTC | Jun 26, 10:44 UTC | 8h 45m |
| 2026-06-24 | ARG1133 | MAD → EZE | Jun 24, 18:29 UTC | Jun 25, 06:44 UTC | 12h 15m |
| 2026-06-24 | ARG1132 | - | Jun 24, 03:15 UTC | Jun 24, 15:05 UTC | 11h 50m |
| 2026-06-23 | ARG1133 | MAD → EZE | Jun 23, 05:54 UTC | Jun 23, 06:29 UTC | 35m |
| 2026-06-22 | ARG1133 | MAD → EZE | Jun 22, 18:19 UTC | Jun 23, 04:55 UTC | 10h 35m |
| 2026-06-22 | ARG1132 | - | Jun 22, 03:10 UTC | Jun 22, 14:59 UTC | 11h 50m |
| 2026-06-21 | ARG1141 | - | Jun 21, 01:49 UTC | Jun 21, 07:00 UTC | 5h 10m |
| 2026-06-20 | ARG1141 | - | Jun 20, 17:34 UTC | Jun 20, 22:50 UTC | 5h 15m |
| 2026-06-20 | ARG1140 | - | Jun 20, 01:50 UTC | Jun 20, 13:44 UTC | 11h 55m |
| 2026-06-18 | ARG1133 | MAD → EZE | Jun 18, 18:30 UTC | Jun 19, 06:24 UTC | 11h 54m |
| 2026-06-18 | ARG1132 | - | Jun 18, 02:55 UTC | Jun 18, 14:10 UTC | 11h 15m |
| 2026-06-16 | ARG1305 | MIA → EZE | Jun 16, 22:50 UTC | Jun 17, 07:05 UTC | 8h 15m |
| 2026-06-16 | ARG1302 | EZE → MIA | Jun 16, 01:55 UTC | Jun 16, 10:25 UTC | 8h 30m |
| 2026-06-15 | ARG1135 | MAD → EZE | Jun 15, 09:25 UTC | Jun 15, 22:05 UTC | 12h 40m |
| 2026-06-14 | ARG1134 | EZE → MAD | Jun 14, 18:20 UTC | Jun 15, 05:55 UTC | 11h 35m |
| 2026-06-13 | ARG1303 | MIA → EZE | Jun 13, 22:20 UTC | Jun 14, 07:15 UTC | 8h 55m |
| 2026-06-13 | ARG1304 | EZE → MIA | Jun 13, 03:05 UTC | Jun 13, 11:40 UTC | 8h 34m |
| 2026-06-11 | ARG1135 | - | Jun 11, 09:20 UTC | Jun 11, 21:35 UTC | 12h 15m |
| 2026-06-10 | ARG1134 | EZE → MAD | Jun 10, 18:30 UTC | Jun 11, 06:00 UTC | 11h 30m |
| 2026-06-09 | ARG1133 | MAD → EZE | Jun 9, 18:35 UTC | Jun 10, 06:50 UTC | 12h 15m |
| 2026-06-09 | ARG1132 | EZE → MAD | Jun 9, 03:05 UTC | Jun 9, 14:25 UTC | 11h 20m |
| 2026-06-08 | ARG1135 | MAD → EZE | Jun 8, 09:10 UTC | Jun 8, 21:55 UTC | 12h 45m |
| 2026-06-07 | ARG1134 | EZE → MAD | Jun 7, 18:25 UTC | Jun 8, 05:55 UTC | 11h 30m |
| 2026-06-05 | ARG1133 | MAD → EZE | Jun 5, 18:30 UTC | Jun 6, 07:05 UTC | 12h 35m |
| 2026-06-05 | ARG1132 | EZE → MAD | Jun 5, 03:15 UTC | Jun 5, 14:45 UTC | 11h 30m |
| 2026-05-25 | ARG1133 | MAD → EZE | May 25, 09:20 UTC | May 25, 10:00 UTC | 40m |
| 2026-05-24 | ARG1133 | MAD → EZE | May 24, 18:25 UTC | May 25, 06:55 UTC | 12h 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 LV-GKO page for operator, model, and routing details .