sensors Mode-S transponder
E0B04E
ICAO 24-bit transponder address · allocated to Argentina
Currently assigned to LV-KAN · AIRBUS A-330-200
- Hex
- E0B04E
- Octal
- 70130116
- Decimal
- 14,725,198
- Country
- AR
- Tail
- LV-KAN
- Type
- A332
- Flights observed
- 146
- Distinct callsigns
- 20
- Country
- AR
- Last broadcast
- Jul 24, 02:05 UTC
Last known position
Country allocation
The ICAO 24-bit address E0B04E 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 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| ARG1305 | - | 30 | 2026-07-14 |
| ARG1302 | - | 29 | 2026-07-15 |
| ARG1304 | - | 25 | 2026-07-16 |
| ARG1303 | Aerolineas Argentinas | 25 | 2026-07-16 |
| ARG1141 | - | 7 | 2026-07-06 |
| ARG1140 | Aerolineas Argentinas | 7 | 2026-07-24 |
| ARG1132 | Aerolineas Argentinas | 5 | 2026-07-22 |
| ARG1133 | Aerolineas Argentinas | 4 | 2026-07-22 |
| ARG1916 | - | 2 | 2026-07-19 |
| ARG1978 | Aerolineas Argentinas | 1 | 2026-05-31 |
| ARG1971 | Aerolineas Argentinas | 1 | 2026-07-20 |
| ARG1909 | - | 1 | 2026-06-28 |
| ARG1908 | - | 1 | 2026-06-26 |
| ARG1907 | - | 1 | 2026-06-23 |
| ARG1904 | - | 1 | 2026-06-21 |
| ARG1903 | - | 1 | 2026-06-17 |
| ARG1902 | - | 1 | 2026-06-14 |
| ARG1900 | Aerolineas Argentinas | 1 | 2026-06-15 |
| ARG1079 | Aerolineas Argentinas | 1 | 2026-06-01 |
| ARG1073 | Aerolineas Argentinas | 1 | 2026-06-14 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-24 | ARG1140 | EZE → FCO | Jul 24, 01:40 UTC | Jul 24, 02:05 UTC | 25m |
| 2026-07-22 | ARG1133 | MAD → EZE | Jul 22, 18:50 UTC | Jul 23, 07:05 UTC | 12h 15m |
| 2026-07-22 | ARG1132 | EZE → MAD | Jul 22, 03:20 UTC | Jul 22, 14:55 UTC | 11h 35m |
| 2026-07-20 | ARG1971 | SCL → EZE | Jul 20, 11:20 UTC | Jul 20, 21:20 UTC | 10h 0m |
| 2026-07-19 | ARG1916 | IAD → JFK | Jul 19, 05:00 UTC | Jul 19, 05:55 UTC | 55m |
| 2026-07-18 | ARG1916 | - | Jul 18, 13:05 UTC | Jul 19, 00:35 UTC | 11h 30m |
| 2026-07-16 | ARG1303 | MIA → EZE | Jul 16, 23:29 UTC | Jul 17, 08:00 UTC | 8h 30m |
| 2026-07-16 | ARG1304 | - | Jul 16, 12:00 UTC | Jul 16, 20:55 UTC | 8h 55m |
| 2026-07-15 | ARG1303 | - | Jul 15, 23:35 UTC | Jul 16, 07:45 UTC | 8h 10m |
| 2026-07-15 | ARG1302 | - | Jul 15, 02:00 UTC | Jul 15, 10:40 UTC | 8h 40m |
| 2026-07-14 | ARG1305 | - | Jul 14, 01:15 UTC | Jul 14, 09:45 UTC | 8h 30m |
| 2026-07-13 | ARG1302 | - | Jul 13, 02:05 UTC | Jul 13, 10:20 UTC | 8h 15m |
| 2026-07-12 | ARG1305 | - | Jul 12, 13:20 UTC | Jul 12, 22:00 UTC | 8h 40m |
| 2026-07-12 | ARG1302 | - | Jul 12, 02:01 UTC | Jul 12, 10:35 UTC | 8h 35m |
| 2026-07-11 | ARG1305 | - | Jul 11, 01:05 UTC | Jul 11, 09:30 UTC | 8h 25m |
| 2026-07-10 | ARG1302 | - | Jul 10, 02:10 UTC | Jul 10, 11:00 UTC | 8h 50m |
| 2026-07-08 | ARG1133 | - | Jul 8, 18:40 UTC | Jul 9, 06:55 UTC | 12h 15m |
| 2026-07-08 | ARG1132 | - | Jul 8, 03:15 UTC | Jul 8, 14:55 UTC | 11h 40m |
| 2026-07-06 | ARG1141 | - | Jul 6, 17:30 UTC | Jul 7, 07:10 UTC | 13h 40m |
| 2026-07-06 | ARG1140 | - | Jul 6, 02:00 UTC | Jul 6, 14:25 UTC | 12h 25m |
| 2026-07-04 | ARG1141 | - | Jul 4, 19:45 UTC | Jul 5, 09:40 UTC | 13h 55m |
| 2026-07-04 | ARG1140 | EZE → FCO | Jul 4, 04:30 UTC | Jul 4, 17:10 UTC | 12h 40m |
| 2026-07-02 | ARG1303 | - | Jul 2, 23:00 UTC | Jul 3, 07:20 UTC | 8h 20m |
| 2026-07-02 | ARG1304 | - | Jul 2, 12:25 UTC | Jul 2, 12:50 UTC | 25m |
| 2026-07-02 | ARG1304 | - | Jul 2, 03:50 UTC | Jul 2, 08:50 UTC | 5h 0m |
| 2026-07-01 | ARG1305 | MIA → EZE | Jul 1, 13:30 UTC | Jul 1, 21:50 UTC | 8h 20m |
| 2026-07-01 | ARG1302 | - | Jul 1, 02:00 UTC | Jul 1, 10:45 UTC | 8h 45m |
| 2026-06-30 | ARG1305 | MIA → EZE | Jun 30, 00:49 UTC | Jun 30, 09:10 UTC | 8h 21m |
| 2026-06-29 | ARG1302 | - | Jun 29, 02:50 UTC | Jun 29, 11:25 UTC | 8h 35m |
| 2026-06-28 | ARG1909 | DFW → EZE | Jun 28, 11:55 UTC | Jun 28, 21:59 UTC | 10h 5m |
| 2026-06-26 | ARG1908 | - | Jun 26, 02:44 UTC | Jun 26, 13:04 UTC | 10h 20m |
| 2026-06-23 | ARG1907 | DFW → EZE | Jun 23, 13:29 UTC | Jun 23, 23:39 UTC | 10h 10m |
| 2026-06-21 | ARG1904 | EZE → DFW | Jun 21, 03:19 UTC | Jun 21, 13:39 UTC | 10h 20m |
| 2026-06-20 | ARG1049 | EZE → AEP | Jun 20, 04:14 UTC | Jun 20, 12:14 UTC | 8h 0m |
| 2026-06-17 | ARG1903 | - | Jun 17, 15:25 UTC | Jun 17, 18:10 UTC | 2h 45m |
| 2026-06-15 | ARG1900 | AEP → USH | Jun 15, 04:30 UTC | Jun 15, 15:15 UTC | 10h 45m |
| 2026-06-14 | ARG1073 | SEA → EZE | Jun 14, 14:00 UTC | Jun 15, 01:00 UTC | 10h 59m |
| 2026-06-14 | ARG1902 | - | Jun 14, 00:05 UTC | Jun 14, 10:55 UTC | 10h 51m |
| 2026-06-12 | ARG1305 | MIA → EZE | Jun 12, 22:30 UTC | Jun 13, 07:05 UTC | 8h 34m |
| 2026-06-12 | ARG1302 | - | Jun 12, 02:00 UTC | Jun 12, 10:45 UTC | 8h 45m |
| 2026-06-11 | ARG1305 | MIA → EZE | Jun 11, 13:20 UTC | Jun 11, 21:40 UTC | 8h 20m |
| 2026-06-11 | ARG1302 | EZE → MIA | Jun 11, 02:00 UTC | Jun 11, 10:55 UTC | 8h 55m |
| 2026-06-10 | ARG1305 | MIA → EZE | Jun 10, 13:25 UTC | Jun 10, 21:40 UTC | 8h 15m |
| 2026-06-10 | ARG1302 | EZE → MIA | Jun 10, 01:55 UTC | Jun 10, 10:45 UTC | 8h 50m |
| 2026-06-09 | ARG1305 | MIA → EZE | Jun 9, 13:20 UTC | Jun 9, 21:20 UTC | 8h 0m |
| 2026-06-09 | ARG1302 | EZE → MIA | Jun 9, 02:00 UTC | Jun 9, 11:00 UTC | 9h 0m |
| 2026-06-08 | ARG1305 | MIA → EZE | Jun 8, 13:55 UTC | Jun 8, 22:05 UTC | 8h 10m |
| 2026-06-08 | ARG1302 | EZE → MIA | Jun 8, 02:05 UTC | Jun 8, 11:05 UTC | 9h 0m |
| 2026-06-07 | ARG1305 | MIA → EZE | Jun 7, 13:20 UTC | Jun 7, 21:35 UTC | 8h 15m |
| 2026-06-07 | ARG1302 | EZE → MIA | Jun 7, 02:04 UTC | Jun 7, 11:10 UTC | 9h 5m |
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-KAN page for operator, model, and routing details .