sensors Mode-S transponder
E0B04F
ICAO 24-bit transponder address · allocated to Argentina
Currently assigned to LV-KAO · AIRBUS A-330-200
- Hex
- E0B04F
- Octal
- 70130117
- Decimal
- 14,725,199
- Country
- AR
- Tail
- LV-KAO
- Type
- A332
- Flights observed
- 153
- Distinct callsigns
- 15
- Country
- AR
- Last broadcast
- 2h ago
Last known position
Country allocation
The ICAO 24-bit address E0B04F 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 15 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| ARG1305 | - | 46 | 2026-07-12 |
| ARG1302 | - | 45 | 2026-07-11 |
| ARG1304 | - | 14 | 2026-07-09 |
| ARG1133 | - | 14 | 2026-07-13 |
| ARG1132 | - | 13 | 2026-07-13 |
| ARG1303 | - | 12 | 2026-07-09 |
| ARG1915 | - | 1 | 2026-07-02 |
| ARG1914 | - | 1 | 2026-07-01 |
| ARG1913 | - | 1 | 2026-07-01 |
| ARG1912 | - | 1 | 2026-06-30 |
| ARG1911 | - | 1 | 2026-06-28 |
| ARG1910 | - | 1 | 2026-06-27 |
| ARG1775 | Aerolineas Argentinas | 1 | 2026-05-24 |
| ARG1774 | Aerolineas Argentinas | 1 | 2026-05-24 |
| ARG1324 | Aerolineas Argentinas | 1 | 2026-05-27 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | ARG1133 | - | Jul 13, 18:25 UTC | Jul 14, 05:05 UTC | 10h 40m |
| 2026-07-13 | ARG1132 | - | Jul 13, 03:05 UTC | Jul 13, 14:25 UTC | 11h 20m |
| 2026-07-12 | ARG1305 | - | Jul 12, 00:40 UTC | Jul 12, 09:10 UTC | 8h 30m |
| 2026-07-11 | ARG1302 | - | Jul 11, 02:05 UTC | Jul 11, 11:05 UTC | 9h 0m |
| 2026-07-09 | ARG1303 | - | Jul 9, 22:45 UTC | Jul 10, 06:50 UTC | 8h 5m |
| 2026-07-09 | ARG1304 | - | Jul 9, 03:45 UTC | Jul 9, 12:30 UTC | 8h 45m |
| 2026-07-06 | ARG1305 | MIA → EZE | Jul 6, 01:40 UTC | Jul 6, 09:50 UTC | 8h 10m |
| 2026-07-05 | ARG1302 | - | Jul 5, 02:10 UTC | Jul 5, 10:50 UTC | 8h 40m |
| 2026-07-04 | ARG1305 | MIA → EZE | Jul 4, 13:40 UTC | Jul 4, 21:55 UTC | 8h 15m |
| 2026-07-04 | ARG1302 | - | Jul 4, 02:25 UTC | Jul 4, 11:05 UTC | 8h 40m |
| 2026-07-03 | ARG1305 | MIA → EZE | Jul 3, 13:45 UTC | Jul 3, 21:55 UTC | 8h 10m |
| 2026-07-03 | ARG1302 | - | Jul 3, 11:00 UTC | Jul 3, 11:20 UTC | 20m |
| 2026-07-03 | ARG1302 | - | Jul 3, 02:35 UTC | Jul 3, 07:25 UTC | 4h 50m |
| 2026-07-02 | ARG1915 | - | Jul 2, 04:15 UTC | Jul 2, 12:40 UTC | 8h 25m |
| 2026-07-01 | ARG1914 | - | Jul 1, 15:40 UTC | Jul 2, 00:35 UTC | 8h 55m |
| 2026-07-01 | ARG1913 | - | Jul 1, 03:30 UTC | Jul 1, 12:25 UTC | 8h 55m |
| 2026-06-30 | ARG1912 | - | Jun 30, 15:35 UTC | Jul 1, 00:20 UTC | 8h 45m |
| 2026-06-29 | ARG1133 | MAD → EZE | Jun 29, 18:39 UTC | Jun 30, 06:55 UTC | 12h 16m |
| 2026-06-29 | ARG1132 | - | Jun 29, 03:10 UTC | Jun 29, 15:09 UTC | 12h 0m |
| 2026-06-28 | ARG1911 | DFW → EZE | Jun 28, 13:25 UTC | Jun 28, 23:39 UTC | 10h 15m |
| 2026-06-27 | ARG1910 | - | Jun 27, 01:04 UTC | Jun 27, 09:44 UTC | 8h 40m |
| 2026-06-25 | ARG1303 | - | Jun 25, 23:24 UTC | Jun 26, 08:00 UTC | 8h 35m |
| 2026-06-25 | ARG1304 | - | Jun 25, 03:10 UTC | Jun 25, 11:50 UTC | 8h 40m |
| 2026-06-22 | ARG1305 | MIA → EZE | Jun 22, 22:30 UTC | Jun 23, 06:39 UTC | 8h 10m |
| 2026-06-22 | ARG1302 | - | Jun 22, 01:55 UTC | Jun 22, 10:49 UTC | 8h 55m |
| 2026-06-20 | ARG1305 | MIA → EZE | Jun 20, 22:45 UTC | Jun 21, 07:25 UTC | 8h 40m |
| 2026-06-20 | ARG1302 | - | Jun 20, 02:14 UTC | Jun 20, 10:39 UTC | 8h 25m |
| 2026-06-18 | ARG1305 | MIA → EZE | Jun 18, 23:05 UTC | Jun 19, 07:19 UTC | 8h 14m |
| 2026-06-18 | ARG1302 | - | Jun 18, 01:55 UTC | Jun 18, 10:45 UTC | 8h 50m |
| 2026-06-16 | ARG1133 | MAD → EZE | Jun 16, 18:25 UTC | Jun 17, 07:00 UTC | 12h 36m |
| 2026-06-16 | ARG1132 | EZE → MAD | Jun 16, 03:04 UTC | Jun 16, 14:30 UTC | 11h 25m |
| 2026-06-15 | ARG1305 | MIA → EZE | Jun 15, 06:55 UTC | Jun 15, 07:20 UTC | 25m |
| 2026-06-14 | ARG1305 | MIA → EZE | Jun 14, 22:35 UTC | Jun 15, 03:35 UTC | 4h 59m |
| 2026-06-14 | ARG1302 | - | Jun 14, 02:25 UTC | Jun 14, 10:50 UTC | 8h 25m |
| 2026-06-13 | ARG1305 | MIA → EZE | Jun 13, 13:20 UTC | Jun 13, 21:55 UTC | 8h 35m |
| 2026-06-13 | ARG1302 | - | Jun 13, 02:15 UTC | Jun 13, 10:50 UTC | 8h 34m |
| 2026-06-11 | ARG1133 | MAD → EZE | Jun 11, 18:30 UTC | Jun 12, 07:00 UTC | 12h 31m |
| 2026-06-11 | ARG1132 | EZE → MAD | Jun 11, 03:10 UTC | Jun 11, 14:45 UTC | 11h 35m |
| 2026-06-08 | ARG1303 | MIA → EZE | Jun 8, 22:25 UTC | Jun 9, 06:50 UTC | 8h 25m |
| 2026-06-08 | ARG1304 | EZE → MIA | Jun 8, 03:00 UTC | Jun 8, 12:15 UTC | 9h 15m |
| 2026-06-06 | ARG1303 | MIA → EZE | Jun 6, 23:44 UTC | Jun 7, 07:50 UTC | 8h 5m |
| 2026-06-06 | ARG1304 | EZE → MIA | Jun 6, 20:10 UTC | Jun 6, 20:35 UTC | 25m |
| 2026-06-06 | ARG1304 | EZE → MIA | Jun 6, 11:30 UTC | Jun 6, 17:40 UTC | 6h 10m |
| 2026-06-03 | ARG1305 | MIA → EZE | Jun 3, 13:25 UTC | Jun 3, 21:45 UTC | 8h 20m |
| 2026-06-03 | ARG1302 | EZE → MIA | Jun 3, 02:15 UTC | Jun 3, 10:50 UTC | 8h 35m |
| 2026-06-01 | ARG1303 | MIA → EZE | Jun 1, 23:45 UTC | Jun 2, 08:05 UTC | 8h 20m |
| 2026-06-01 | ARG1304 | EZE → MIA | Jun 1, 11:20 UTC | Jun 1, 20:10 UTC | 8h 50m |
| 2026-05-31 | ARG1303 | MIA → EZE | May 31, 23:20 UTC | Jun 1, 07:40 UTC | 8h 20m |
| 2026-05-31 | ARG1304 | EZE → MIA | May 31, 11:35 UTC | May 31, 20:40 UTC | 9h 5m |
| 2026-05-30 | ARG1305 | MIA → EZE | May 30, 14:00 UTC | May 30, 22:25 UTC | 8h 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.
Prefer a tail-number view? See the LV-KAO page for operator, model, and routing details .