sensors Mode-S transponder
0D82E1
ICAO 24-bit transponder address · allocated to Venezuela
Currently assigned to YV3332 · LEARJET 31
- Hex
- 0D82E1
- Octal
- 03301341
- Decimal
- 885,473
- Country
- VE
- Tail
- YV3332
- Type
- LJ31
- Flights observed
- 25
- Distinct callsigns
- 2
- Country
- VE
- Last broadcast
- 13d ago
Last known position
Country allocation
The ICAO 24-bit address 0D82E1 falls within the block assigned to Venezuela (VE) by ICAO Annex 10, Volume III. Every aircraft registered in Venezuela 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 2 distinct
Recent flights last 25
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-23 | AXH3332 | - | Jul 23, 16:55 UTC | Jul 23, 17:10 UTC | 15m |
| 2026-07-23 | AXH3332 | - | Jul 23, 15:45 UTC | Jul 23, 15:55 UTC | 10m |
| 2026-07-21 | AXH3332 | - | Jul 21, 18:20 UTC | Jul 21, 18:30 UTC | 10m |
| 2026-07-21 | AXH3332 | - | Jul 21, 16:00 UTC | Jul 21, 16:10 UTC | 10m |
| 2026-07-16 | AXH3332 | - | Jul 16, 13:10 UTC | Jul 16, 15:25 UTC | 2h 15m |
| 2026-07-16 | AXH3332 | - | Jul 16, 12:20 UTC | Jul 16, 12:34 UTC | 15m |
| 2026-07-15 | AXH3332 | - | Jul 15, 15:15 UTC | Jul 15, 15:25 UTC | 10m |
| 2026-07-15 | AXH3332 | - | Jul 15, 12:55 UTC | Jul 15, 13:20 UTC | 25m |
| 2026-07-14 | AXH3332 | - | Jul 14, 16:50 UTC | Jul 15, 13:20 UTC | 20h 29m |
| 2026-07-07 | AXH3332 | - | Jul 7, 14:55 UTC | Jul 7, 15:25 UTC | 30m |
| 2026-07-07 | AXH3332 | - | Jul 7, 12:15 UTC | Jul 7, 12:50 UTC | 35m |
| 2026-06-26 | AXH3332 | - | Jun 26, 17:50 UTC | Jun 26, 17:59 UTC | 10m |
| 2026-06-10 | AXH3332 | - | Jun 10, 22:10 UTC | Jun 10, 22:45 UTC | 35m |
| 2026-06-10 | AXH3332 | - | Jun 10, 11:25 UTC | Jun 10, 11:50 UTC | 25m |
| 2026-05-17 | YV3332 | - | May 17, 17:25 UTC | May 17, 17:35 UTC | 10m |
| 2026-05-17 | AXH3332 | - | May 17, 15:50 UTC | May 17, 16:15 UTC | 25m |
| 2026-05-10 | AXH3332 | - | May 10, 21:04 UTC | May 10, 21:35 UTC | 30m |
| 2026-05-10 | AXH3332 | - | May 10, 16:00 UTC | May 10, 19:45 UTC | 3h 45m |
| 2026-05-10 | AXH3332 | - | May 10, 11:50 UTC | May 10, 12:19 UTC | 30m |
| 2026-05-07 | AXH3332 | - | May 7, 16:10 UTC | May 7, 20:40 UTC | 4h 30m |
| 2026-05-07 | AXH3332 | - | May 7, 15:00 UTC | May 7, 15:25 UTC | 25m |
| 2026-04-17 | AXH3332 | - | Apr 17, 16:15 UTC | Apr 17, 16:45 UTC | 30m |
| 2026-04-17 | YV3332 | - | Apr 17, 13:40 UTC | Apr 17, 15:15 UTC | 1h 35m |
| 2026-04-16 | YV3332 | - | Apr 16, 23:30 UTC | Apr 17, 00:05 UTC | 35m |
| 2026-04-16 | YV3332 | - | Apr 16, 22:00 UTC | Apr 16, 22:20 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 YV3332 page for operator, model, and routing details .