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