sensors Mode-S transponder
E0B30F
ICAO 24-bit transponder address · allocated to Argentina
Currently assigned to LV-KLO · LEARJET 60
- Hex
- E0B30F
- Octal
- 70131417
- Decimal
- 14,725,903
- Country
- AR
- Tail
- LV-KLO
- Type
- LJ60
- Flights observed
- 25
- Distinct callsigns
- 1
- Country
- AR
- Last broadcast
- Jul 26, 14:40 UTC
Last known position
Country allocation
The ICAO 24-bit address E0B30F 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 |
|---|---|---|---|
| LVKLO | - | 25 | 2026-07-26 |
Recent flights last 25
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | LVKLO | - | Jul 26, 14:15 UTC | Jul 26, 14:40 UTC | 25m |
| 2026-07-25 | LVKLO | - | Jul 25, 19:25 UTC | Jul 25, 20:00 UTC | 35m |
| 2026-07-25 | LVKLO | - | Jul 25, 18:10 UTC | Jul 25, 18:30 UTC | 20m |
| 2026-07-24 | LVKLO | - | Jul 24, 14:15 UTC | Jul 24, 14:30 UTC | 15m |
| 2026-07-24 | LVKLO | - | Jul 24, 13:25 UTC | Jul 24, 13:45 UTC | 20m |
| 2026-07-13 | LVKLO | - | Jul 13, 15:20 UTC | Jul 13, 15:50 UTC | 30m |
| 2026-07-13 | LVKLO | - | Jul 13, 13:40 UTC | Jul 13, 14:05 UTC | 25m |
| 2026-07-08 | LVKLO | - | Jul 8, 14:15 UTC | Jul 8, 14:45 UTC | 30m |
| 2026-07-08 | LVKLO | - | Jul 8, 12:40 UTC | Jul 8, 13:05 UTC | 25m |
| 2026-07-06 | LVKLO | - | Jul 6, 15:25 UTC | Jul 6, 15:50 UTC | 25m |
| 2026-07-06 | LVKLO | - | Jul 6, 13:40 UTC | Jul 6, 14:00 UTC | 20m |
| 2026-07-03 | LVKLO | - | Jul 3, 21:00 UTC | Jul 3, 21:30 UTC | 30m |
| 2026-07-03 | LVKLO | - | Jul 3, 19:40 UTC | Jul 3, 20:05 UTC | 25m |
| 2026-05-28 | LVKLO | - | May 28, 16:45 UTC | May 28, 17:05 UTC | 20m |
| 2026-05-22 | LVKLO | - | May 22, 16:15 UTC | May 22, 16:45 UTC | 30m |
| 2026-05-13 | LVKLO | - | May 13, 14:25 UTC | May 13, 14:55 UTC | 30m |
| 2026-05-13 | LVKLO | - | May 13, 12:10 UTC | May 13, 12:30 UTC | 20m |
| 2026-04-30 | LVKLO | - | Apr 30, 18:35 UTC | Apr 30, 18:55 UTC | 20m |
| 2026-04-28 | LVKLO | - | Apr 28, 11:20 UTC | Apr 28, 11:55 UTC | 35m |
| 2026-04-28 | LVKLO | - | Apr 28, 09:35 UTC | Apr 28, 09:45 UTC | 10m |
| 2026-04-24 | LVKLO | - | Apr 24, 00:55 UTC | Apr 24, 01:15 UTC | 20m |
| 2026-04-21 | LVKLO | - | Apr 21, 21:15 UTC | Apr 21, 21:45 UTC | 30m |
| 2026-04-15 | LVKLO | - | Apr 15, 20:00 UTC | Apr 15, 20:35 UTC | 35m |
| 2026-04-15 | LVKLO | - | Apr 15, 18:10 UTC | Apr 15, 18:30 UTC | 20m |
| 2026-04-13 | LVKLO | - | Apr 13, 20:00 UTC | Apr 13, 22:05 UTC | 2h 5m |
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-KLO page for operator, model, and routing details .