sensors Mode-S transponder
E0F4C4
ICAO 24-bit transponder address · allocated to Argentina
Currently assigned to LV-OSD · DASSAULT Falcon 2000
- Hex
- E0F4C4
- Octal
- 70172304
- Decimal
- 14,742,724
- Country
- AR
- Tail
- LV-OSD
- Type
- F2TH
- Flights observed
- 39
- Distinct callsigns
- 1
- Country
- AR
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address E0F4C4 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 |
|---|---|---|---|
| LVOSD | - | 39 | 2026-07-12 |
Recent flights last 39
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-12 | LVOSD | - | Jul 12, 17:30 UTC | Jul 12, 17:40 UTC | 10m |
| 2026-07-09 | LVOSD | NAS → FLL | Jul 9, 12:00 UTC | Jul 9, 12:40 UTC | 40m |
| 2026-07-09 | LVOSD | - | Jul 9, 11:05 UTC | Jul 9, 11:25 UTC | 20m |
| 2026-07-08 | LVOSD | - | Jul 8, 21:45 UTC | Jul 9, 06:20 UTC | 8h 35m |
| 2026-07-07 | LVOSD | - | Jul 7, 20:55 UTC | Jul 7, 21:30 UTC | 35m |
| 2026-07-07 | LVOSD | - | Jul 7, 14:10 UTC | Jul 7, 14:45 UTC | 35m |
| 2026-07-06 | LVOSD | - | Jul 6, 03:10 UTC | Jul 6, 12:25 UTC | 9h 15m |
| 2026-07-02 | LVOSD | - | Jul 2, 00:45 UTC | Jul 2, 11:25 UTC | 10h 40m |
| 2026-06-30 | LVOSD | - | Jun 30, 14:15 UTC | Jun 30, 14:55 UTC | 40m |
| 2026-06-27 | LVOSD | - | Jun 27, 09:44 UTC | Jun 28, 01:34 UTC | 15h 50m |
| 2026-06-25 | LVOSD | - | Jun 25, 10:09 UTC | Jun 25, 13:00 UTC | 2h 50m |
| 2026-06-25 | LVOSD | SKG → JMK | Jun 25, 08:04 UTC | Jun 25, 09:29 UTC | 1h 25m |
| 2026-06-24 | LVOSD | - | Jun 24, 13:54 UTC | Jun 24, 14:39 UTC | 45m |
| 2026-06-24 | LVOSD | IBZ → JMK | Jun 24, 10:39 UTC | Jun 24, 13:30 UTC | 2h 50m |
| 2026-06-20 | LVOSD | BCN → IBZ | Jun 20, 10:04 UTC | Jun 20, 10:44 UTC | 40m |
| 2026-06-17 | LVOSD | - | Jun 17, 07:25 UTC | Jun 17, 10:05 UTC | 2h 40m |
| 2026-06-17 | LVOSD | SKG → JMK | Jun 17, 06:05 UTC | Jun 17, 07:00 UTC | 55m |
| 2026-06-14 | LVOSD | JMK → SKG | Jun 14, 18:05 UTC | Jun 14, 18:50 UTC | 45m |
| 2026-06-14 | LVOSD | - | Jun 14, 14:50 UTC | Jun 14, 17:20 UTC | 2h 30m |
| 2026-06-12 | LVOSD | - | Jun 12, 12:15 UTC | Jun 12, 12:35 UTC | 20m |
| 2026-06-12 | LVOSD | LPA → BCN | Jun 12, 08:20 UTC | Jun 12, 11:10 UTC | 2h 50m |
| 2026-06-11 | LVOSD | - | Jun 11, 20:50 UTC | Jun 12, 00:15 UTC | 3h 25m |
| 2026-06-07 | LVOSD | - | Jun 7, 15:55 UTC | Jun 7, 16:25 UTC | 30m |
| 2026-06-06 | LVOSD | - | Jun 6, 20:19 UTC | Jun 6, 20:35 UTC | 15m |
| 2026-06-04 | LVOSD | - | Jun 4, 21:05 UTC | Jun 4, 21:35 UTC | 30m |
| 2026-06-02 | LVOSD | - | Jun 2, 12:35 UTC | Jun 2, 12:50 UTC | 15m |
| 2026-06-01 | LVOSD | - | Jun 1, 13:10 UTC | Jun 1, 22:00 UTC | 8h 50m |
| 2026-05-31 | LVOSD | - | May 31, 21:55 UTC | May 31, 23:10 UTC | 1h 15m |
| 2026-05-02 | LVOSD | - | May 2, 17:25 UTC | May 2, 18:40 UTC | 1h 15m |
| 2026-05-01 | LVOSD | - | May 1, 12:20 UTC | May 1, 19:55 UTC | 7h 35m |
| 2026-04-22 | LVOSD | - | Apr 22, 19:45 UTC | Apr 22, 20:15 UTC | 30m |
| 2026-04-21 | LVOSD | - | Apr 21, 14:31 UTC | Apr 21, 14:50 UTC | 20m |
| 2026-04-20 | LVOSD | - | Apr 20, 12:50 UTC | Apr 20, 15:45 UTC | 2h 55m |
| 2026-04-18 | LVOSD | - | Apr 18, 15:20 UTC | Apr 18, 16:05 UTC | 45m |
| 2026-04-17 | LVOSD | - | Apr 17, 19:25 UTC | Apr 17, 19:35 UTC | 10m |
| 2026-04-17 | LVOSD | - | Apr 17, 19:05 UTC | Apr 18, 16:05 UTC | 21h 0m |
| 2026-04-17 | LVOSD | - | Apr 17, 18:55 UTC | Apr 18, 16:05 UTC | 21h 10m |
| 2026-04-17 | LVOSD | - | Apr 17, 15:00 UTC | Apr 17, 15:15 UTC | 15m |
| 2026-04-15 | LVOSD | - | Apr 15, 17:05 UTC | Apr 15, 17:15 UTC | 10m |
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-OSD page for operator, model, and routing details .