sensors Mode-S transponder
0D8367
ICAO 24-bit transponder address · allocated to Venezuela
Currently assigned to YV3025 · CESSNA 501 Citation 1SP
- Hex
- 0D8367
- Octal
- 03301547
- Decimal
- 885,607
- Country
- VE
- Tail
- YV3025
- Type
- C501
- Flights observed
- 60
- Distinct callsigns
- 1
- Country
- VE
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 0D8367 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 |
|---|---|---|---|
| YV3025 | - | 60 | 2026-05-28 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-28 | YV3025 | - | May 28, 15:10 UTC | May 28, 16:40 UTC | 1h 30m |
| 2026-05-27 | YV3025 | - | May 27, 20:30 UTC | May 28, 14:15 UTC | 17h 45m |
| 2026-05-27 | YV3025 | - | May 27, 14:35 UTC | May 27, 15:05 UTC | 30m |
| 2026-05-22 | YV3025 | - | May 22, 17:20 UTC | May 22, 18:10 UTC | 50m |
| 2026-05-21 | YV3025 | - | May 21, 20:10 UTC | May 22, 14:15 UTC | 18h 5m |
| 2026-05-21 | YV3025 | - | May 21, 17:35 UTC | May 21, 17:55 UTC | 20m |
| 2026-05-21 | YV3025 | - | May 21, 13:20 UTC | May 21, 14:35 UTC | 1h 15m |
| 2026-05-20 | YV3025 | - | May 20, 15:50 UTC | May 21, 14:35 UTC | 22h 45m |
| 2026-05-20 | YV3025 | - | May 20, 14:05 UTC | May 20, 15:50 UTC | 1h 45m |
| 2026-05-19 | YV3025 | - | May 19, 15:50 UTC | May 20, 15:45 UTC | 23h 56m |
| 2026-05-19 | YV3025 | - | May 19, 15:20 UTC | May 19, 16:00 UTC | 40m |
| 2026-05-19 | YV3025 | - | May 19, 14:10 UTC | May 19, 14:30 UTC | 20m |
| 2026-05-19 | YV3025 | - | May 19, 11:25 UTC | May 19, 12:15 UTC | 50m |
| 2026-05-16 | YV3025 | - | May 16, 20:25 UTC | May 16, 20:55 UTC | 30m |
| 2026-05-16 | YV3025 | - | May 16, 19:20 UTC | May 16, 19:40 UTC | 20m |
| 2026-05-11 | YV3025 | - | May 11, 15:05 UTC | May 11, 15:45 UTC | 40m |
| 2026-05-11 | YV3025 | - | May 11, 13:55 UTC | May 11, 14:20 UTC | 25m |
| 2026-05-09 | YV3025 | - | May 9, 17:25 UTC | May 9, 21:50 UTC | 4h 25m |
| 2026-05-07 | YV3025 | - | May 7, 17:55 UTC | May 7, 18:45 UTC | 50m |
| 2026-05-07 | YV3025 | - | May 7, 15:20 UTC | May 7, 16:00 UTC | 40m |
| 2026-05-06 | YV3025 | - | May 6, 17:50 UTC | May 7, 16:00 UTC | 22h 11m |
| 2026-05-06 | YV3025 | - | May 6, 17:10 UTC | May 7, 15:45 UTC | 22h 35m |
| 2026-05-06 | YV3025 | - | May 6, 14:35 UTC | May 6, 16:00 UTC | 1h 25m |
| 2026-05-05 | YV3025 | - | May 5, 11:35 UTC | May 5, 16:15 UTC | 4h 40m |
| 2026-04-30 | YV3025 | - | Apr 30, 21:15 UTC | Apr 30, 21:50 UTC | 35m |
| 2026-04-30 | YV3025 | - | Apr 30, 19:50 UTC | Apr 30, 20:10 UTC | 20m |
| 2026-04-30 | YV3025 | - | Apr 30, 18:55 UTC | Apr 30, 19:10 UTC | 15m |
| 2026-04-30 | YV3025 | - | Apr 30, 12:55 UTC | Apr 30, 17:10 UTC | 4h 15m |
| 2026-04-29 | YV3025 | - | Apr 29, 16:25 UTC | Apr 29, 16:40 UTC | 15m |
| 2026-04-29 | YV3025 | - | Apr 29, 12:30 UTC | Apr 29, 13:20 UTC | 50m |
| 2026-04-26 | YV3025 | - | Apr 26, 19:50 UTC | Apr 26, 20:25 UTC | 35m |
| 2026-04-26 | YV3025 | - | Apr 26, 18:45 UTC | Apr 26, 19:30 UTC | 45m |
| 2026-04-23 | YV3025 | - | Apr 23, 21:55 UTC | Apr 23, 22:45 UTC | 50m |
| 2026-04-23 | YV3025 | - | Apr 23, 15:00 UTC | Apr 23, 19:35 UTC | 4h 35m |
| 2026-04-23 | YV3025 | - | Apr 23, 14:00 UTC | Apr 23, 14:20 UTC | 20m |
| 2026-04-23 | YV3025 | - | Apr 23, 11:45 UTC | Apr 23, 12:10 UTC | 25m |
| 2026-04-23 | YV3025 | - | Apr 23, 02:35 UTC | Apr 23, 03:05 UTC | 30m |
| 2026-04-22 | YV3025 | - | Apr 22, 18:45 UTC | Apr 22, 19:20 UTC | 35m |
| 2026-04-22 | YV3025 | - | Apr 22, 14:40 UTC | Apr 22, 15:15 UTC | 35m |
| 2026-04-21 | YV3025 | - | Apr 21, 17:50 UTC | Apr 22, 15:15 UTC | 21h 25m |
| 2026-04-21 | YV3025 | - | Apr 21, 17:05 UTC | Apr 22, 15:15 UTC | 22h 10m |
| 2026-04-21 | YV3025 | - | Apr 21, 11:55 UTC | Apr 21, 15:35 UTC | 3h 40m |
| 2026-04-20 | YV3025 | - | Apr 20, 22:10 UTC | Apr 20, 22:30 UTC | 20m |
| 2026-04-20 | YV3025 | - | Apr 20, 19:40 UTC | Apr 20, 20:05 UTC | 25m |
| 2026-04-20 | YV3025 | - | Apr 20, 18:25 UTC | Apr 20, 18:55 UTC | 30m |
| 2026-04-17 | YV3025 | - | Apr 17, 22:10 UTC | Apr 17, 22:50 UTC | 40m |
| 2026-04-17 | YV3025 | - | Apr 17, 19:25 UTC | Apr 17, 19:40 UTC | 15m |
| 2026-04-17 | YV3025 | - | Apr 17, 17:25 UTC | Apr 17, 17:35 UTC | 10m |
| 2026-04-17 | YV3025 | - | Apr 17, 16:45 UTC | Apr 17, 17:15 UTC | 30m |
| 2026-04-17 | YV3025 | - | Apr 17, 13:45 UTC | Apr 17, 14:20 UTC | 35m |
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 YV3025 page for operator, model, and routing details .