sensors Mode-S transponder
0D8161
ICAO 24-bit transponder address · allocated to Venezuela
Currently assigned to YV2692 · CESSNA 550 Citation S2
- Hex
- 0D8161
- Octal
- 03300541
- Decimal
- 885,089
- Country
- VE
- Tail
- YV2692
- Type
- C550
- Flights observed
- 49
- Distinct callsigns
- 1
- Country
- VE
- Last broadcast
- 9d ago
Last known position
Country allocation
The ICAO 24-bit address 0D8161 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 1 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| YV2692 | - | 49 | 2026-07-25 |
Recent flights last 49
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-25 | YV2692 | - | Jul 25, 08:00 UTC | Jul 25, 08:25 UTC | 25m |
| 2026-07-25 | YV2692 | - | Jul 25, 05:05 UTC | Jul 25, 06:25 UTC | 1h 20m |
| 2026-07-21 | YV2692 | - | Jul 21, 16:00 UTC | Jul 21, 18:00 UTC | 2h 0m |
| 2026-07-20 | YV2692 | - | Jul 20, 22:25 UTC | Jul 21, 01:45 UTC | 3h 20m |
| 2026-07-19 | YV2692 | - | Jul 19, 15:20 UTC | Jul 19, 16:20 UTC | 1h 0m |
| 2026-07-18 | YV2692 | - | Jul 18, 23:40 UTC | Jul 18, 23:55 UTC | 15m |
| 2026-07-18 | YV2692 | - | Jul 18, 19:50 UTC | Jul 18, 22:45 UTC | 2h 55m |
| 2026-07-17 | YV2692 | - | Jul 17, 22:49 UTC | Jul 17, 23:10 UTC | 20m |
| 2026-07-17 | YV2692 | - | Jul 17, 13:45 UTC | Jul 17, 21:15 UTC | 7h 30m |
| 2026-07-16 | YV2692 | - | Jul 16, 15:30 UTC | Jul 17, 00:20 UTC | 8h 50m |
| 2026-07-15 | YV2692 | - | Jul 15, 23:35 UTC | Jul 16, 00:15 UTC | 40m |
| 2026-07-14 | YV2692 | - | Jul 14, 12:50 UTC | Jul 14, 13:25 UTC | 35m |
| 2026-07-13 | YV2692 | - | Jul 13, 18:10 UTC | Jul 13, 23:55 UTC | 5h 45m |
| 2026-07-13 | YV2692 | - | Jul 13, 15:30 UTC | Jul 13, 16:00 UTC | 30m |
| 2026-07-13 | YV2692 | - | Jul 13, 12:45 UTC | Jul 13, 13:15 UTC | 30m |
| 2026-07-09 | YV2692 | - | Jul 9, 14:55 UTC | Jul 9, 21:45 UTC | 6h 50m |
| 2026-07-01 | YV2692 | - | Jul 1, 16:30 UTC | Jul 1, 18:15 UTC | 1h 45m |
| 2026-06-30 | YV2692 | - | Jun 30, 13:40 UTC | Jun 30, 16:45 UTC | 3h 5m |
| 2026-06-29 | YV2692 | - | Jun 29, 22:10 UTC | Jun 30, 01:25 UTC | 3h 15m |
| 2026-06-22 | YV2692 | - | Jun 22, 22:19 UTC | Jun 23, 01:10 UTC | 2h 50m |
| 2026-06-21 | YV2692 | - | Jun 21, 12:40 UTC | Jun 22, 03:05 UTC | 14h 25m |
| 2026-06-20 | YV2692 | - | Jun 20, 03:19 UTC | Jun 20, 09:09 UTC | 5h 50m |
| 2026-06-19 | YV2692 | - | Jun 19, 22:39 UTC | Jun 20, 01:50 UTC | 3h 10m |
| 2026-06-17 | YV2692 | - | Jun 17, 16:45 UTC | Jun 17, 17:10 UTC | 25m |
| 2026-06-17 | YV2692 | - | Jun 17, 13:50 UTC | Jun 17, 14:15 UTC | 25m |
| 2026-06-03 | YV2692 | - | Jun 3, 16:00 UTC | Jun 3, 16:40 UTC | 40m |
| 2026-06-03 | YV2692 | - | Jun 3, 14:05 UTC | Jun 3, 14:30 UTC | 25m |
| 2026-05-31 | YV2692 | - | May 31, 14:50 UTC | May 31, 15:35 UTC | 45m |
| 2026-05-30 | YV2692 | - | May 30, 21:05 UTC | May 31, 13:50 UTC | 16h 45m |
| 2026-05-29 | YV2692 | - | May 29, 20:40 UTC | May 30, 16:00 UTC | 19h 20m |
| 2026-05-29 | YV2692 | - | May 29, 15:20 UTC | May 29, 15:25 UTC | 5m |
| 2026-05-29 | YV2692 | - | May 29, 13:05 UTC | May 29, 13:25 UTC | 20m |
| 2026-05-22 | YV2692 | - | May 22, 02:20 UTC | May 22, 02:55 UTC | 35m |
| 2026-05-21 | YV2692 | - | May 21, 23:10 UTC | May 21, 23:40 UTC | 30m |
| 2026-05-18 | YV2692 | - | May 18, 21:50 UTC | May 18, 22:55 UTC | 1h 5m |
| 2026-05-14 | YV2692 | - | May 14, 15:05 UTC | May 14, 21:00 UTC | 5h 55m |
| 2026-05-10 | YV2692 | - | May 10, 22:20 UTC | May 10, 23:00 UTC | 40m |
| 2026-05-10 | YV2692 | - | May 10, 17:59 UTC | May 10, 21:00 UTC | 3h 0m |
| 2026-05-09 | YV2692 | - | May 9, 22:30 UTC | May 10, 15:39 UTC | 17h 10m |
| 2026-05-09 | YV2692 | - | May 9, 16:00 UTC | May 9, 16:30 UTC | 30m |
| 2026-05-07 | YV2692 | - | May 7, 22:45 UTC | May 7, 23:24 UTC | 40m |
| 2026-05-07 | YV2692 | - | May 7, 21:35 UTC | May 7, 22:10 UTC | 35m |
| 2026-05-05 | YV2692 | - | May 5, 13:55 UTC | May 5, 16:55 UTC | 3h 0m |
| 2026-05-05 | YV2692 | - | May 5, 07:25 UTC | May 5, 08:00 UTC | 35m |
| 2026-05-05 | YV2692 | - | May 5, 04:35 UTC | May 5, 06:00 UTC | 1h 25m |
| 2026-05-02 | YV2692 | - | May 2, 20:10 UTC | May 2, 20:45 UTC | 35m |
| 2026-05-02 | YV2692 | - | May 2, 13:00 UTC | May 2, 13:30 UTC | 30m |
| 2026-04-24 | YV2692 | - | Apr 24, 20:50 UTC | Apr 24, 22:15 UTC | 1h 25m |
| 2026-04-18 | YV2692 | - | Apr 18, 19:30 UTC | Apr 18, 19:45 UTC | 15m |
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 YV2692 page for operator, model, and routing details .