sensors Mode-S transponder
E0B052
ICAO 24-bit transponder address · allocated to Argentina
Currently assigned to LV-KAR · CIRRUS SR-22
- Hex
- E0B052
- Octal
- 70130122
- Decimal
- 14,725,202
- Country
- AR
- Tail
- LV-KAR
- Type
- SR22
- Flights observed
- 39
- Distinct callsigns
- 1
- Country
- AR
- Last broadcast
- Jul 24, 21:20 UTC
Last known position
Country allocation
The ICAO 24-bit address E0B052 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 1 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| LVKAR | - | 39 | 2026-07-24 |
Recent flights last 39
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-24 | LVKAR | - | Jul 24, 21:05 UTC | Jul 24, 21:20 UTC | 15m |
| 2026-07-24 | LVKAR | - | Jul 24, 11:50 UTC | Jul 24, 12:15 UTC | 25m |
| 2026-07-18 | LVKAR | - | Jul 18, 12:45 UTC | Jul 18, 14:00 UTC | 1h 15m |
| 2026-07-13 | LVKAR | - | Jul 13, 19:35 UTC | Jul 13, 19:55 UTC | 20m |
| 2026-07-13 | LVKAR | - | Jul 13, 18:30 UTC | Jul 13, 18:45 UTC | 15m |
| 2026-07-12 | LVKAR | - | Jul 12, 23:00 UTC | Jul 12, 23:50 UTC | 50m |
| 2026-07-12 | LVKAR | - | Jul 12, 21:45 UTC | Jul 12, 22:20 UTC | 35m |
| 2026-07-12 | LVKAR | - | Jul 12, 19:01 UTC | Jul 12, 19:10 UTC | 10m |
| 2026-07-12 | LVKAR | - | Jul 12, 17:01 UTC | Jul 12, 18:01 UTC | 1h 0m |
| 2026-07-10 | LVKAR | - | Jul 10, 20:50 UTC | Jul 10, 21:35 UTC | 45m |
| 2026-07-10 | LVKAR | - | Jul 10, 11:40 UTC | Jul 10, 12:15 UTC | 35m |
| 2026-07-09 | LVKAR | - | Jul 9, 17:25 UTC | Jul 9, 18:10 UTC | 45m |
| 2026-07-09 | LVKAR | - | Jul 9, 16:15 UTC | Jul 9, 16:50 UTC | 35m |
| 2026-07-09 | LVKAR | - | Jul 9, 15:20 UTC | Jul 9, 15:40 UTC | 20m |
| 2026-07-09 | LVKAR | - | Jul 9, 13:40 UTC | Jul 9, 14:40 UTC | 1h 0m |
| 2026-07-06 | LVKAR | - | Jul 6, 20:30 UTC | Jul 6, 20:45 UTC | 15m |
| 2026-07-06 | LVKAR | - | Jul 6, 18:25 UTC | Jul 6, 18:40 UTC | 15m |
| 2026-06-27 | LVKAR | - | Jun 27, 20:44 UTC | Jun 27, 21:40 UTC | 55m |
| 2026-06-27 | LVKAR | - | Jun 27, 14:39 UTC | Jun 27, 15:24 UTC | 45m |
| 2026-06-15 | LVKAR | - | Jun 15, 18:20 UTC | Jun 15, 18:40 UTC | 20m |
| 2026-06-15 | LVKAR | - | Jun 15, 15:35 UTC | Jun 15, 16:04 UTC | 30m |
| 2026-06-14 | LVKAR | - | Jun 14, 20:55 UTC | Jun 14, 21:10 UTC | 15m |
| 2026-06-14 | LVKAR | - | Jun 14, 13:40 UTC | Jun 14, 13:55 UTC | 15m |
| 2026-05-31 | LVKAR | - | May 31, 18:00 UTC | May 31, 18:20 UTC | 20m |
| 2026-05-31 | LVKAR | - | May 31, 15:25 UTC | May 31, 16:10 UTC | 45m |
| 2026-05-25 | LVKAR | - | May 25, 19:15 UTC | May 25, 19:35 UTC | 20m |
| 2026-05-25 | LVKAR | - | May 25, 16:15 UTC | May 25, 16:45 UTC | 30m |
| 2026-05-21 | LVKAR | - | May 21, 21:15 UTC | May 21, 22:10 UTC | 55m |
| 2026-05-21 | LVKAR | - | May 21, 19:05 UTC | May 21, 19:35 UTC | 30m |
| 2026-05-16 | LVKAR | - | May 16, 12:01 UTC | May 16, 12:16 UTC | 15m |
| 2026-05-12 | LVKAR | - | May 12, 17:25 UTC | May 12, 17:45 UTC | 20m |
| 2026-05-12 | LVKAR | - | May 12, 15:10 UTC | May 12, 15:40 UTC | 30m |
| 2026-05-10 | LVKAR | - | May 10, 21:40 UTC | May 10, 21:54 UTC | 15m |
| 2026-05-10 | LVKAR | - | May 10, 14:14 UTC | May 10, 14:30 UTC | 15m |
| 2026-05-01 | LVKAR | - | May 1, 22:30 UTC | May 1, 22:45 UTC | 15m |
| 2026-05-01 | LVKAR | - | May 1, 11:30 UTC | May 1, 11:55 UTC | 25m |
| 2026-04-25 | LVKAR | - | Apr 25, 19:45 UTC | Apr 25, 19:55 UTC | 10m |
| 2026-04-25 | LVKAR | - | Apr 25, 13:35 UTC | Apr 25, 13:50 UTC | 15m |
| 2026-04-18 | LVKAR | - | Apr 18, 14:25 UTC | Apr 18, 14:45 UTC | 20m |
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-KAR page for operator, model, and routing details .