sensors Mode-S transponder
E0B058
ICAO 24-bit transponder address · allocated to Argentina
Currently assigned to LV-KAX · GULFSTREAM 5
- Hex
- E0B058
- Octal
- 70130130
- Decimal
- 14,725,208
- Country
- AR
- Tail
- LV-KAX
- Type
- GLF5
- Flights observed
- 48
- Distinct callsigns
- 1
- Country
- AR
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address E0B058 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 |
|---|---|---|---|
| LVKAX | - | 48 | 2026-06-01 |
Recent flights last 48
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-01 | LVKAX | - | Jun 1, 09:50 UTC | Jun 1, 12:20 UTC | 2h 30m |
| 2026-05-31 | LVKAX | - | May 31, 21:50 UTC | Jun 1, 07:50 UTC | 10h 0m |
| 2026-05-31 | LVKAX | PRG → BUD | May 31, 20:25 UTC | May 31, 21:15 UTC | 50m |
| 2026-05-29 | LVKAX | - | May 29, 13:25 UTC | May 29, 14:15 UTC | 50m |
| 2026-05-28 | LVKAX | - | May 28, 21:50 UTC | May 29, 12:50 UTC | 15h 0m |
| 2026-05-28 | LVKAX | - | May 28, 19:25 UTC | May 28, 19:45 UTC | 20m |
| 2026-05-26 | LVKAX | - | May 26, 13:15 UTC | May 26, 16:59 UTC | 3h 45m |
| 2026-05-24 | LVKAX | - | May 24, 13:35 UTC | May 24, 14:30 UTC | 55m |
| 2026-05-24 | LVKAX | - | May 24, 03:15 UTC | May 24, 05:30 UTC | 2h 15m |
| 2026-05-24 | LVKAX | - | May 24, 00:00 UTC | May 24, 01:35 UTC | 1h 35m |
| 2026-05-23 | LVKAX | - | May 23, 16:45 UTC | May 23, 18:05 UTC | 1h 20m |
| 2026-05-22 | LVKAX | - | May 22, 00:05 UTC | May 22, 11:45 UTC | 11h 40m |
| 2026-05-18 | LVKAX | - | May 18, 05:20 UTC | May 18, 16:00 UTC | 10h 40m |
| 2026-05-17 | LVKAX | - | May 17, 10:15 UTC | May 18, 03:05 UTC | 16h 50m |
| 2026-05-16 | LVKAX | - | May 16, 18:45 UTC | May 17, 08:45 UTC | 14h 0m |
| 2026-05-16 | LVKAX | - | May 16, 07:11 UTC | May 16, 16:05 UTC | 8h 55m |
| 2026-05-15 | LVKAX | - | May 15, 20:25 UTC | May 16, 05:46 UTC | 9h 21m |
| 2026-05-15 | LVKAX | - | May 15, 16:30 UTC | May 15, 16:50 UTC | 20m |
| 2026-05-14 | LVKAX | FXE → YYJ | May 14, 19:45 UTC | May 15, 06:05 UTC | 10h 20m |
| 2026-05-11 | LVKAX | - | May 11, 01:45 UTC | May 11, 02:15 UTC | 30m |
| 2026-05-10 | LVKAX | - | May 10, 09:24 UTC | May 10, 16:14 UTC | 6h 50m |
| 2026-05-08 | LVKAX | - | May 8, 06:45 UTC | May 8, 11:34 UTC | 4h 50m |
| 2026-05-07 | LVKAX | - | May 7, 16:15 UTC | May 8, 01:49 UTC | 9h 34m |
| 2026-05-06 | LVKAX | - | May 6, 17:15 UTC | May 6, 22:35 UTC | 5h 19m |
| 2026-05-06 | LVKAX | BJC → FXE | May 6, 06:00 UTC | May 6, 09:10 UTC | 3h 10m |
| 2026-05-04 | LVKAX | - | May 4, 05:50 UTC | May 4, 09:50 UTC | 4h 0m |
| 2026-05-03 | LVKAX | TEB → FXE | May 3, 23:35 UTC | May 4, 02:10 UTC | 2h 35m |
| 2026-05-03 | LVKAX | - | May 3, 20:10 UTC | May 3, 22:49 UTC | 2h 40m |
| 2026-04-30 | LVKAX | - | Apr 30, 14:40 UTC | Apr 30, 17:30 UTC | 2h 50m |
| 2026-04-30 | LVKAX | - | Apr 30, 01:05 UTC | Apr 30, 10:55 UTC | 9h 50m |
| 2026-04-29 | LVKAX | - | Apr 29, 21:40 UTC | Apr 29, 23:45 UTC | 2h 4m |
| 2026-04-29 | LVKAX | TEB → AEP | Apr 29, 05:40 UTC | Apr 29, 16:00 UTC | 10h 21m |
| 2026-04-29 | LVKAX | TMB → TEB | Apr 29, 00:15 UTC | Apr 29, 02:55 UTC | 2h 40m |
| 2026-04-28 | LVKAX | - | Apr 28, 22:15 UTC | Apr 28, 22:35 UTC | 20m |
| 2026-04-27 | LVKAX | - | Apr 27, 06:00 UTC | Apr 27, 06:10 UTC | 10m |
| 2026-04-26 | LVKAX | - | Apr 26, 20:55 UTC | Apr 26, 21:20 UTC | 25m |
| 2026-04-25 | LVKAX | - | Apr 25, 19:05 UTC | Apr 25, 19:15 UTC | 10m |
| 2026-04-24 | LVKAX | - | Apr 24, 05:50 UTC | Apr 24, 06:10 UTC | 20m |
| 2026-04-24 | LVKAX | - | Apr 24, 02:55 UTC | Apr 24, 03:20 UTC | 25m |
| 2026-04-23 | LVKAX | - | Apr 23, 15:25 UTC | Apr 23, 17:50 UTC | 2h 25m |
| 2026-04-23 | LVKAX | AEP → TEB | Apr 23, 02:55 UTC | Apr 23, 14:00 UTC | 11h 5m |
| 2026-04-20 | LVKAX | - | Apr 20, 14:10 UTC | Apr 20, 14:20 UTC | 10m |
| 2026-04-20 | LVKAX | - | Apr 20, 04:45 UTC | Apr 20, 12:55 UTC | 8h 10m |
| 2026-04-20 | LVKAX | - | Apr 20, 03:10 UTC | Apr 20, 03:35 UTC | 25m |
| 2026-04-19 | LVKAX | - | Apr 19, 17:50 UTC | Apr 20, 02:10 UTC | 8h 20m |
| 2026-04-18 | LVKAX | - | Apr 18, 09:05 UTC | Apr 18, 09:20 UTC | 15m |
| 2026-04-18 | LVKAX | - | Apr 18, 02:30 UTC | Apr 18, 10:20 UTC | 7h 50m |
| 2026-04-18 | LVKAX | - | Apr 18, 00:45 UTC | Apr 18, 01:05 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-KAX page for operator, model, and routing details .