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