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
- 59
- Distinct callsigns
- 10
- Country
- AR
- Last broadcast
- 28m 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 10 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| ARG1324 | Aerolineas Argentinas | 10 | 2026-05-26 |
| ARG1372 | Aerolineas Argentinas | 9 | 2026-05-18 |
| ARG1329 | Aerolineas Argentinas | 9 | 2026-05-24 |
| ARG1325 | Aerolineas Argentinas | 9 | 2026-05-23 |
| ARG1373 | Aerolineas Argentinas | 6 | 2026-05-18 |
| ARG1370 | Aerolineas Argentinas | 6 | 2026-04-24 |
| ARG1371 | Aerolineas Argentinas | 5 | 2026-04-24 |
| ARG1328 | Aerolineas Argentinas | 3 | 2026-05-29 |
| 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-05-29 | ARG1328 | EZE → PUJ | May 29, 12:10 UTC | May 30, 01:10 UTC | 13h 0m |
| 2026-05-26 | ARG1324 | EZE → PUJ | May 26, 02:24 UTC | May 26, 20:09 UTC | 17h 45m |
| 2026-05-24 | ARG1329 | PUJ → EZE | May 24, 13:20 UTC | May 25, 07:45 UTC | 18h 25m |
| 2026-05-24 | ARG1328 | EZE → PUJ | May 24, 12:15 UTC | May 25, 07:45 UTC | 19h 30m |
| 2026-05-23 | ARG1325 | PUJ → EZE | May 23, 02:30 UTC | May 23, 20:25 UTC | 17h 55m |
| 2026-05-20 | ARG1325 | PUJ → EZE | May 20, 02:30 UTC | May 20, 20:30 UTC | 18h 1m |
| 2026-05-18 | ARG1373 | CUN → EZE | May 18, 23:20 UTC | May 19, 07:20 UTC | 8h 0m |
| 2026-05-18 | ARG1372 | EZE → CUN | May 18, 11:55 UTC | May 18, 20:55 UTC | 8h 59m |
| 2026-05-16 | ARG1325 | PUJ → EZE | May 16, 02:10 UTC | May 16, 20:20 UTC | 18h 11m |
| 2026-05-09 | ARG1325 | PUJ → EZE | May 9, 02:20 UTC | May 9, 20:05 UTC | 17h 45m |
| 2026-05-06 | ARG1325 | PUJ → EZE | May 6, 02:15 UTC | May 6, 20:00 UTC | 17h 44m |
| 2026-05-04 | ARG1373 | CUN → EZE | May 4, 23:40 UTC | May 5, 07:05 UTC | 7h 25m |
| 2026-05-04 | ARG1372 | EZE → CUN | May 4, 11:55 UTC | May 4, 19:25 UTC | 7h 31m |
| 2026-05-03 | ARG1329 | PUJ → EZE | May 3, 11:40 UTC | May 4, 07:15 UTC | 19h 35m |
| 2026-05-02 | ARG1373 | CUN → EZE | May 2, 23:05 UTC | May 3, 07:25 UTC | 8h 19m |
| 2026-05-02 | ARG1372 | EZE → CUN | May 2, 11:35 UTC | May 2, 20:25 UTC | 8h 50m |
| 2026-05-01 | ARG1329 | PUJ → EZE | May 1, 11:45 UTC | May 2, 07:05 UTC | 19h 20m |
| 2026-04-29 | ARG1324 | EZE → PUJ | Apr 29, 02:20 UTC | Apr 29, 19:45 UTC | 17h 26m |
| 2026-04-28 | ARG1324 | EZE → PUJ | Apr 28, 02:15 UTC | Apr 28, 20:05 UTC | 17h 50m |
| 2026-04-26 | ARG1329 | PUJ → EZE | Apr 26, 13:20 UTC | Apr 27, 07:35 UTC | 18h 15m |
| 2026-04-26 | ARG1329 | PUJ → EZE | Apr 26, 12:05 UTC | Apr 27, 07:35 UTC | 19h 30m |
| 2026-04-25 | ARG1325 | PUJ → EZE | Apr 25, 02:15 UTC | Apr 25, 19:55 UTC | 17h 40m |
| 2026-04-24 | ARG1371 | CUN → EZE | Apr 24, 14:00 UTC | Apr 24, 22:10 UTC | 8h 10m |
| 2026-04-24 | ARG1370 | EZE → CUN | Apr 24, 02:40 UTC | Apr 24, 11:15 UTC | 8h 35m |
| 2026-04-22 | ARG1371 | CUN → EZE | Apr 22, 22:55 UTC | Apr 22, 23:20 UTC | 25m |
| 2026-04-22 | ARG1370 | EZE → CUN | Apr 22, 04:15 UTC | Apr 22, 19:30 UTC | 15h 15m |
| 2026-04-20 | ARG1373 | CUN → EZE | Apr 20, 22:55 UTC | Apr 21, 06:50 UTC | 7h 55m |
| 2026-04-20 | ARG1372 | EZE → CUN | Apr 20, 11:45 UTC | Apr 20, 20:20 UTC | 8h 35m |
| 2026-04-19 | ARG1787 | IGR → AEP | Apr 19, 21:45 UTC | Apr 19, 23:15 UTC | 1h 30m |
| 2026-04-19 | ARG1786 | EZE → IGR | Apr 19, 18:15 UTC | Apr 19, 19:30 UTC | 1h 15m |
| 2026-04-18 | ARG1324 | EZE → PUJ | Apr 18, 07:45 UTC | Apr 18, 09:20 UTC | 1h 35m |
| 2026-04-18 | ARG1324 | EZE → PUJ | Apr 18, 04:45 UTC | Apr 18, 05:25 UTC | 40m |
| 2026-04-18 | ARG1324 | EZE → PUJ | Apr 18, 03:25 UTC | Apr 18, 05:20 UTC | 1h 55m |
| 2026-04-18 | ARG1324 | EZE → PUJ | Apr 18, 02:20 UTC | Apr 18, 19:50 UTC | 17h 30m |
| 2026-04-17 | ARG1371 | CUN → EZE | Apr 17, 21:35 UTC | Apr 17, 21:55 UTC | 20m |
| 2026-04-17 | ARG1371 | CUN → EZE | Apr 17, 17:30 UTC | Apr 17, 18:15 UTC | 45m |
| 2026-04-17 | ARG1371 | CUN → EZE | Apr 17, 13:55 UTC | Apr 17, 14:25 UTC | 30m |
| 2026-04-17 | ARG1370 | EZE → CUN | Apr 17, 11:20 UTC | Apr 17, 11:30 UTC | 10m |
| 2026-04-17 | ARG1370 | EZE → CUN | Apr 17, 10:45 UTC | Apr 17, 11:15 UTC | 30m |
| 2026-04-17 | ARG1370 | EZE → CUN | Apr 17, 03:20 UTC | Apr 17, 03:55 UTC | 35m |
| 2026-04-17 | ARG1370 | EZE → CUN | Apr 17, 02:50 UTC | Apr 17, 03:15 UTC | 25m |
| 2026-04-15 | ARG1325 | PUJ → EZE | Apr 15, 19:05 UTC | Apr 15, 20:10 UTC | 1h 5m |
| 2026-04-15 | ARG1325 | PUJ → EZE | Apr 15, 17:05 UTC | Apr 15, 19:00 UTC | 1h 55m |
| 2026-04-15 | ARG1325 | PUJ → EZE | Apr 15, 13:10 UTC | Apr 15, 14:45 UTC | 1h 34m |
| 2026-04-15 | ARG1324 | EZE → PUJ | Apr 15, 08:05 UTC | Apr 15, 08:20 UTC | 15m |
| 2026-04-15 | ARG1324 | EZE → PUJ | Apr 15, 02:55 UTC | Apr 15, 03:35 UTC | 40m |
| 2026-04-15 | ARG1324 | EZE → PUJ | Apr 15, 02:25 UTC | Apr 15, 02:50 UTC | 25m |
| 2026-04-14 | ARG1373 | CUN → EZE | Apr 14, 06:25 UTC | Apr 14, 06:55 UTC | 30m |
| 2026-04-13 | ARG1373 | CUN → EZE | Apr 13, 22:50 UTC | Apr 13, 23:45 UTC | 55m |
| 2026-04-13 | ARG1372 | - | Apr 13, 19:50 UTC | Apr 13, 20:20 UTC | 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-KHU page for operator, model, and routing details .