sensors Mode-S transponder
E0B215
ICAO 24-bit transponder address · allocated to Argentina
Currently assigned to LV-KHU · AIRBUS A-330-200
- Hex
- E0B215
- Octal
- 70131025
- Decimal
- 14,725,653
- Country
- AR
- Tail
- LV-KHU
- Type
- A332
- Flights observed
- 114
- Distinct callsigns
- 16
- Country
- AR
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address E0B215 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 16 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| ARG1324 | - | 29 | 2026-07-13 |
| ARG1370 | - | 21 | 2026-07-03 |
| ARG1329 | Aerolineas Argentinas | 13 | 2026-05-31 |
| ARG1372 | Aerolineas Argentinas | 10 | 2026-05-30 |
| ARG1325 | Aerolineas Argentinas | 9 | 2026-05-23 |
| ARG1373 | Aerolineas Argentinas | 7 | 2026-05-31 |
| ARG1328 | - | 6 | 2026-07-14 |
| ARG1371 | Aerolineas Argentinas | 5 | 2026-04-24 |
| ARG1304 | - | 4 | 2026-07-11 |
| ARG1303 | - | 2 | 2026-07-11 |
| ARG1141 | - | 2 | 2026-07-08 |
| ARG1140 | - | 2 | 2026-07-08 |
| ARG1793 | - | 1 | 2026-07-13 |
| ARG1792 | - | 1 | 2026-07-12 |
| ARG1787 | Aerolineas Argentinas | 1 | 2026-04-19 |
| ARG1786 | Aerolineas Argentinas | 1 | 2026-04-19 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | ARG1328 | - | Jul 14, 07:30 UTC | Jul 14, 09:15 UTC | 1h 45m |
| 2026-07-13 | ARG1324 | CUN → EZE | Jul 13, 21:10 UTC | Jul 14, 05:30 UTC | 8h 20m |
| 2026-07-13 | ARG1324 | - | Jul 13, 05:50 UTC | Jul 13, 18:55 UTC | 13h 5m |
| 2026-07-13 | ARG1793 | - | Jul 13, 00:45 UTC | Jul 13, 02:30 UTC | 1h 45m |
| 2026-07-12 | ARG1792 | - | Jul 12, 21:15 UTC | Jul 12, 22:40 UTC | 1h 25m |
| 2026-07-11 | ARG1303 | - | Jul 11, 22:50 UTC | Jul 12, 07:25 UTC | 8h 35m |
| 2026-07-11 | ARG1304 | - | Jul 11, 13:40 UTC | Jul 11, 14:00 UTC | 20m |
| 2026-07-11 | ARG1304 | - | Jul 11, 05:01 UTC | Jul 11, 11:00 UTC | 6h 0m |
| 2026-07-08 | ARG1141 | - | Jul 8, 18:00 UTC | Jul 9, 07:20 UTC | 13h 20m |
| 2026-07-08 | ARG1140 | - | Jul 8, 02:05 UTC | Jul 8, 14:50 UTC | 12h 45m |
| 2026-07-07 | ARG1324 | CUN → EZE | Jul 7, 03:10 UTC | Jul 7, 11:30 UTC | 8h 20m |
| 2026-07-06 | ARG1324 | - | Jul 6, 11:00 UTC | Jul 7, 00:45 UTC | 13h 45m |
| 2026-07-05 | ARG1303 | - | Jul 5, 23:00 UTC | Jul 6, 07:05 UTC | 8h 5m |
| 2026-07-05 | ARG1304 | - | Jul 5, 12:20 UTC | Jul 5, 12:40 UTC | 20m |
| 2026-07-05 | ARG1304 | - | Jul 5, 03:55 UTC | Jul 5, 08:50 UTC | 4h 55m |
| 2026-07-04 | ARG1328 | - | Jul 4, 05:40 UTC | Jul 4, 23:20 UTC | 17h 40m |
| 2026-07-03 | ARG1370 | CUN → EZE | Jul 3, 13:40 UTC | Jul 4, 02:55 UTC | 13h 15m |
| 2026-07-03 | ARG1370 | - | Jul 3, 02:55 UTC | Jul 3, 11:30 UTC | 8h 35m |
| 2026-07-01 | ARG1324 | CUN → EZE | Jul 1, 21:15 UTC | Jul 2, 05:15 UTC | 8h 0m |
| 2026-07-01 | ARG1324 | - | Jul 1, 05:55 UTC | Jul 1, 19:15 UTC | 13h 20m |
| 2026-06-29 | ARG1324 | - | Jun 29, 22:30 UTC | Jun 30, 06:30 UTC | 8h 1m |
| 2026-06-29 | ARG1324 | - | Jun 29, 05:40 UTC | Jun 29, 18:49 UTC | 13h 10m |
| 2026-06-28 | ARG1370 | - | Jun 28, 18:44 UTC | Jun 29, 01:55 UTC | 7h 10m |
| 2026-06-28 | ARG1370 | - | Jun 28, 13:04 UTC | Jun 28, 15:09 UTC | 2h 5m |
| 2026-06-28 | ARG1370 | EZE → CUN | Jun 28, 02:29 UTC | Jun 28, 11:09 UTC | 8h 40m |
| 2026-06-26 | ARG1370 | CUN → EZE | Jun 26, 12:55 UTC | Jun 27, 01:35 UTC | 12h 40m |
| 2026-06-26 | ARG1370 | EZE → CUN | Jun 26, 02:34 UTC | Jun 26, 11:00 UTC | 8h 25m |
| 2026-06-24 | ARG1324 | CUN → EZE | Jun 24, 21:09 UTC | Jun 25, 05:15 UTC | 8h 5m |
| 2026-06-24 | ARG1324 | EZE → CUN | Jun 24, 05:44 UTC | Jun 24, 19:24 UTC | 13h 40m |
| 2026-06-21 | ARG1370 | CUN → EZE | Jun 21, 13:15 UTC | Jun 22, 01:19 UTC | 12h 5m |
| 2026-06-21 | ARG1370 | EZE → CUN | Jun 21, 02:45 UTC | Jun 21, 11:10 UTC | 8h 25m |
| 2026-06-19 | ARG1141 | - | Jun 19, 17:44 UTC | Jun 20, 06:54 UTC | 13h 10m |
| 2026-06-19 | ARG1140 | - | Jun 19, 01:59 UTC | Jun 19, 14:54 UTC | 12h 55m |
| 2026-06-17 | ARG1324 | - | Jun 17, 21:55 UTC | Jun 18, 05:05 UTC | 7h 10m |
| 2026-06-17 | ARG1324 | - | Jun 17, 05:40 UTC | Jun 17, 19:00 UTC | 13h 20m |
| 2026-06-16 | ARG1324 | CUN → EZE | Jun 16, 02:50 UTC | Jun 16, 11:00 UTC | 8h 10m |
| 2026-06-15 | ARG1324 | - | Jun 15, 11:19 UTC | Jun 16, 00:45 UTC | 13h 25m |
| 2026-06-14 | ARG1370 | - | Jun 14, 09:50 UTC | Jun 15, 05:15 UTC | 19h 25m |
| 2026-06-14 | ARG1370 | - | Jun 14, 07:20 UTC | Jun 15, 05:15 UTC | 21h 55m |
| 2026-06-14 | ARG1370 | - | Jun 14, 05:50 UTC | Jun 15, 05:15 UTC | 23h 24m |
| 2026-06-12 | ARG1370 | EZE → CUN | Jun 12, 07:20 UTC | Jun 13, 01:45 UTC | 18h 25m |
| 2026-06-12 | ARG1370 | EZE → CUN | Jun 12, 06:35 UTC | Jun 13, 01:45 UTC | 19h 10m |
| 2026-06-12 | ARG1370 | EZE → CUN | Jun 12, 02:40 UTC | Jun 13, 00:15 UTC | 21h 35m |
| 2026-06-10 | ARG1324 | EZE → PUJ | Jun 10, 22:20 UTC | Jun 11, 06:30 UTC | 8h 10m |
| 2026-06-10 | ARG1324 | EZE → PUJ | Jun 10, 06:40 UTC | Jun 10, 20:20 UTC | 13h 40m |
| 2026-06-09 | ARG1328 | EZE → PUJ | Jun 9, 05:25 UTC | Jun 9, 23:30 UTC | 18h 5m |
| 2026-06-06 | ARG1328 | EZE → PUJ | Jun 6, 06:10 UTC | Jun 7, 00:30 UTC | 18h 20m |
| 2026-06-03 | ARG1324 | EZE → PUJ | Jun 3, 11:20 UTC | Jun 4, 07:05 UTC | 19h 45m |
| 2026-06-03 | ARG1324 | EZE → PUJ | Jun 3, 07:20 UTC | Jun 4, 07:05 UTC | 23h 45m |
| 2026-06-03 | ARG1324 | EZE → PUJ | Jun 3, 05:55 UTC | Jun 4, 03:20 UTC | 21h 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-KHU page for operator, model, and routing details .