sensors Mode-S transponder
E0B3C7
ICAO 24-bit transponder address · allocated to Argentina
- Hex
- E0B3C7
- Octal
- 70131707
- Decimal
- 14,726,087
- Country
- AR
- Flights observed
- 46
- Distinct callsigns
- 1
- Country
- AR
- Last broadcast
- Jul 24, 21:15 UTC
Last known position
Country allocation
The ICAO 24-bit address E0B3C7 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 |
|---|---|---|---|
| LVKOG | - | 46 | 2026-07-24 |
Recent flights last 46
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-24 | LVKOG | - | Jul 24, 20:40 UTC | Jul 24, 21:15 UTC | 35m |
| 2026-07-24 | LVKOG | - | Jul 24, 17:15 UTC | Jul 24, 18:05 UTC | 50m |
| 2026-07-22 | LVKOG | - | Jul 22, 21:30 UTC | Jul 22, 23:50 UTC | 2h 20m |
| 2026-07-21 | LVKOG | - | Jul 21, 00:25 UTC | Jul 21, 11:10 UTC | 10h 45m |
| 2026-07-15 | LVKOG | - | Jul 15, 17:30 UTC | Jul 15, 18:05 UTC | 35m |
| 2026-07-15 | LVKOG | - | Jul 15, 14:35 UTC | Jul 15, 16:45 UTC | 2h 10m |
| 2026-07-14 | LVKOG | - | Jul 14, 07:50 UTC | Jul 14, 10:10 UTC | 2h 20m |
| 2026-07-13 | LVKOG | - | Jul 13, 19:30 UTC | Jul 14, 06:45 UTC | 11h 15m |
| 2026-07-13 | LVKOG | - | Jul 13, 12:35 UTC | Jul 13, 12:55 UTC | 20m |
| 2026-07-03 | LVKOG | - | Jul 3, 13:10 UTC | Jul 3, 15:50 UTC | 2h 40m |
| 2026-07-01 | LVKOG | - | Jul 1, 18:55 UTC | Jul 1, 20:50 UTC | 1h 55m |
| 2026-06-29 | LVKOG | - | Jun 29, 18:14 UTC | Jun 29, 18:49 UTC | 35m |
| 2026-06-29 | LVKOG | - | Jun 29, 11:10 UTC | Jun 29, 13:34 UTC | 2h 25m |
| 2026-06-26 | LVKOG | - | Jun 26, 15:39 UTC | Jun 26, 18:09 UTC | 2h 30m |
| 2026-06-25 | LVKOG | - | Jun 25, 11:39 UTC | Jun 25, 12:30 UTC | 50m |
| 2026-06-25 | LVKOG | - | Jun 25, 10:04 UTC | Jun 25, 11:35 UTC | 1h 30m |
| 2026-06-12 | LVKOG | - | Jun 12, 18:01 UTC | Jun 12, 22:05 UTC | 4h 5m |
| 2026-06-05 | LVKOG | - | Jun 5, 20:50 UTC | Jun 5, 21:20 UTC | 30m |
| 2026-06-04 | LVKOG | - | Jun 4, 11:55 UTC | Jun 4, 12:25 UTC | 30m |
| 2026-06-03 | LVKOG | - | Jun 3, 19:35 UTC | Jun 3, 21:15 UTC | 1h 40m |
| 2026-06-03 | LVKOG | - | Jun 3, 17:35 UTC | Jun 3, 18:05 UTC | 30m |
| 2026-06-02 | LVKOG | - | Jun 2, 20:20 UTC | Jun 3, 18:05 UTC | 21h 45m |
| 2026-06-02 | LVKOG | - | Jun 2, 17:20 UTC | Jun 2, 18:45 UTC | 1h 25m |
| 2026-05-26 | LVKOG | - | May 26, 22:54 UTC | May 27, 01:34 UTC | 2h 40m |
| 2026-05-26 | LVKOG | - | May 26, 13:00 UTC | May 26, 15:24 UTC | 2h 25m |
| 2026-05-24 | LVKOG | - | May 24, 00:35 UTC | May 24, 13:00 UTC | 12h 25m |
| 2026-05-20 | LVKOG | - | May 20, 02:50 UTC | May 20, 03:20 UTC | 30m |
| 2026-05-19 | LVKOG | - | May 19, 21:40 UTC | May 19, 22:20 UTC | 40m |
| 2026-05-18 | LVKOG | TPA → IND | May 18, 13:30 UTC | May 18, 15:30 UTC | 2h 0m |
| 2026-05-17 | LVKOG | - | May 17, 23:20 UTC | May 18, 12:05 UTC | 12h 45m |
| 2026-05-12 | LVKOG | - | May 12, 19:35 UTC | May 12, 20:05 UTC | 30m |
| 2026-05-12 | LVKOG | - | May 12, 11:05 UTC | May 12, 11:25 UTC | 20m |
| 2026-05-05 | LVKOG | - | May 5, 23:05 UTC | May 6, 01:55 UTC | 2h 50m |
| 2026-05-04 | LVKOG | - | May 4, 18:30 UTC | May 4, 20:45 UTC | 2h 16m |
| 2026-04-23 | LVKOG | - | Apr 23, 23:00 UTC | Apr 24, 01:45 UTC | 2h 45m |
| 2026-04-23 | LVKOG | - | Apr 23, 20:35 UTC | Apr 23, 21:15 UTC | 40m |
| 2026-04-22 | LVKOG | - | Apr 22, 17:50 UTC | Apr 22, 18:20 UTC | 30m |
| 2026-04-22 | LVKOG | - | Apr 22, 10:05 UTC | Apr 22, 12:15 UTC | 2h 10m |
| 2026-04-15 | LVKOG | - | Apr 15, 01:30 UTC | Apr 15, 01:55 UTC | 25m |
| 2026-04-14 | LVKOG | - | Apr 14, 20:55 UTC | Apr 14, 21:35 UTC | 40m |
| 2026-04-14 | LVKOG | - | Apr 14, 20:35 UTC | Apr 14, 20:50 UTC | 15m |
| 2026-04-14 | LVKOG | - | Apr 14, 14:50 UTC | Apr 14, 16:20 UTC | 1h 30m |
| 2026-04-14 | LVKOG | - | Apr 14, 13:55 UTC | Apr 14, 14:45 UTC | 50m |
| 2026-04-13 | LVKOG | - | Apr 13, 16:15 UTC | Apr 13, 17:10 UTC | 55m |
| 2026-04-13 | LVKOG | - | Apr 13, 15:50 UTC | Apr 13, 17:10 UTC | 1h 20m |
| 2026-04-13 | LVKOG | - | Apr 13, 15:25 UTC | Apr 13, 16:15 UTC | 50m |
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.