sensors Mode-S transponder
E2008A
ICAO 24-bit transponder address · allocated to Argentina
Currently assigned to LV-S074 · BRM AERO NG-5/6 Bristell
- Hex
- E2008A
- Octal
- 70400212
- Decimal
- 14,811,274
- Country
- AR
- Tail
- LV-S074
- Type
- NG5
- Flights observed
- 62
- Distinct callsigns
- 1
- Country
- AR
- Last broadcast
- Jul 26, 21:15 UTC
Last known position
Country allocation
The ICAO 24-bit address E2008A 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 |
|---|---|---|---|
| LVS074 | - | 61 | 2026-07-26 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | LVS074 | - | Jul 26, 20:40 UTC | Jul 26, 21:15 UTC | 35m |
| 2026-07-26 | LVS074 | - | Jul 26, 19:30 UTC | Jul 26, 19:40 UTC | 10m |
| 2026-07-26 | LVS074 | - | Jul 26, 18:00 UTC | Jul 26, 18:15 UTC | 15m |
| 2026-07-26 | LVS074 | - | Jul 26, 16:55 UTC | Jul 26, 17:20 UTC | 25m |
| 2026-07-26 | LVS074 | - | Jul 26, 15:10 UTC | Jul 26, 15:55 UTC | 45m |
| 2026-07-25 | LVS074 | - | Jul 25, 17:55 UTC | Jul 25, 18:20 UTC | 25m |
| 2026-07-14 | LVS074 | - | Jul 14, 19:10 UTC | Jul 14, 19:40 UTC | 30m |
| 2026-07-14 | LVS074 | - | Jul 14, 18:20 UTC | Jul 14, 18:30 UTC | 10m |
| 2026-07-14 | LVS074 | - | Jul 14, 16:15 UTC | Jul 14, 17:05 UTC | 50m |
| 2026-07-14 | LVS074 | - | Jul 14, 14:30 UTC | Jul 14, 15:10 UTC | 40m |
| 2026-07-12 | LVS074 | - | Jul 12, 20:40 UTC | Jul 12, 21:10 UTC | 30m |
| 2026-07-12 | LVS074 | - | Jul 12, 17:45 UTC | Jul 12, 18:10 UTC | 25m |
| 2026-07-10 | LVS074 | - | Jul 10, 19:25 UTC | Jul 10, 20:00 UTC | 35m |
| 2026-07-09 | LVS074 | - | Jul 9, 20:50 UTC | Jul 9, 21:05 UTC | 15m |
| 2026-07-09 | LVS074 | - | Jul 9, 19:20 UTC | Jul 9, 19:45 UTC | 25m |
| 2026-07-09 | LVS074 | - | Jul 9, 17:50 UTC | Jul 9, 18:25 UTC | 35m |
| 2026-07-04 | LVS074 | - | Jul 4, 14:50 UTC | Jul 4, 15:05 UTC | 15m |
| 2026-07-01 | LVS074 | - | Jul 1, 20:15 UTC | Jul 1, 21:00 UTC | 45m |
| 2026-07-01 | LVS074 | - | Jul 1, 18:10 UTC | Jul 1, 18:50 UTC | 40m |
| 2026-07-01 | LVS074 | - | Jul 1, 16:20 UTC | Jul 1, 17:15 UTC | 55m |
| 2026-06-30 | LVS074 | - | Jun 30, 20:00 UTC | Jun 30, 20:40 UTC | 40m |
| 2026-06-30 | LVS074 | - | Jun 30, 18:00 UTC | Jun 30, 19:05 UTC | 1h 5m |
| 2026-06-24 | LVS074 | - | Jun 24, 12:44 UTC | Jun 24, 13:40 UTC | 55m |
| 2026-06-23 | LVS074 | - | Jun 23, 16:24 UTC | Jun 23, 16:54 UTC | 30m |
| 2026-06-21 | - | - | Jun 21, 17:24 UTC | Jun 21, 17:35 UTC | 10m |
| 2026-06-20 | LVS074 | - | Jun 20, 21:00 UTC | Jun 20, 21:10 UTC | 10m |
| 2026-06-17 | LVS074 | - | Jun 17, 20:50 UTC | Jun 17, 21:10 UTC | 20m |
| 2026-06-17 | LVS074 | - | Jun 17, 16:15 UTC | Jun 17, 16:25 UTC | 10m |
| 2026-06-17 | LVS074 | - | Jun 17, 15:15 UTC | Jun 17, 15:40 UTC | 25m |
| 2026-06-15 | LVS074 | - | Jun 15, 19:00 UTC | Jun 15, 19:25 UTC | 25m |
| 2026-06-15 | LVS074 | - | Jun 15, 13:40 UTC | Jun 15, 14:20 UTC | 40m |
| 2026-06-14 | LVS074 | - | Jun 14, 20:30 UTC | Jun 14, 21:05 UTC | 35m |
| 2026-06-14 | LVS074 | - | Jun 14, 18:40 UTC | Jun 14, 19:15 UTC | 35m |
| 2026-06-12 | LVS074 | - | Jun 12, 16:30 UTC | Jun 12, 17:10 UTC | 40m |
| 2026-06-11 | LVS074 | - | Jun 11, 19:30 UTC | Jun 11, 20:10 UTC | 40m |
| 2026-05-30 | LVS074 | - | May 30, 16:35 UTC | May 30, 17:00 UTC | 25m |
| 2026-05-23 | LVS074 | - | May 23, 14:55 UTC | May 23, 16:50 UTC | 1h 55m |
| 2026-05-22 | LVS074 | - | May 22, 16:00 UTC | May 22, 16:10 UTC | 10m |
| 2026-05-22 | LVS074 | - | May 22, 14:45 UTC | May 22, 15:25 UTC | 40m |
| 2026-05-05 | LVS074 | - | May 5, 12:20 UTC | May 5, 12:35 UTC | 15m |
| 2026-05-01 | LVS074 | - | May 1, 11:20 UTC | May 1, 11:35 UTC | 15m |
| 2026-04-26 | LVS074 | - | Apr 26, 15:35 UTC | Apr 26, 16:05 UTC | 30m |
| 2026-04-26 | LVS074 | - | Apr 26, 14:50 UTC | Apr 26, 15:05 UTC | 15m |
| 2026-04-25 | LVS074 | - | Apr 25, 14:10 UTC | Apr 25, 14:20 UTC | 10m |
| 2026-04-24 | LVS074 | - | Apr 24, 20:50 UTC | Apr 24, 21:15 UTC | 25m |
| 2026-04-24 | LVS074 | - | Apr 24, 19:20 UTC | Apr 24, 20:00 UTC | 40m |
| 2026-04-24 | LVS074 | - | Apr 24, 16:20 UTC | Apr 24, 17:05 UTC | 45m |
| 2026-04-19 | LVS074 | - | Apr 19, 17:10 UTC | Apr 19, 17:30 UTC | 20m |
| 2026-04-19 | LVS074 | - | Apr 19, 14:10 UTC | Apr 19, 15:05 UTC | 55m |
| 2026-04-18 | LVS074 | - | Apr 18, 15:00 UTC | Apr 18, 16:20 UTC | 1h 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-S074 page for operator, model, and routing details .