Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

0D82BE

ICAO 24-bit transponder address · allocated to Venezuela

Currently assigned to YV621T · BOEING 737-400

Hex
0D82BE
Octal
03301276
Decimal
885,438
Country
VE
Tail
YV621T
Type
B734
No current signal · last broadcast 11h ago
Flights observed
62
Distinct callsigns
6
Country
VE
Last broadcast
11h ago

Last known position

Most recent position reported by Mode-S 0D82BE.

Country allocation

The ICAO 24-bit address 0D82BE 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 6 distinct

Callsign Airline Flights Last seen
VTU6310 Turpial Airlines 21 2026-07-17
VTU6311 Turpial Airlines 15 2026-07-17
VTU880 - 12 2026-07-13
VTU881 - 10 2026-07-13
VTU8930 - 3 2026-04-18
VTU8931 - 1 2026-04-18

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-17 VTU6311 PZO → VLN Jul 17, 14:24 UTCJul 17, 14:55 UTC30m
2026-07-17 VTU6310 VLN → PZO Jul 17, 12:15 UTCJul 17, 12:50 UTC35m
2026-07-16 VTU6310 VLN → PZO Jul 16, 15:55 UTCJul 17, 12:50 UTC20h 55m
2026-07-13 VTU6311 PZO → VLN Jul 13, 14:05 UTCJul 13, 14:35 UTC30m
2026-07-13 VTU6310 VLN → PZO Jul 13, 12:20 UTCJul 13, 12:55 UTC35m
2026-07-13 VTU881 - Jul 13, 02:45 UTCJul 13, 02:55 UTC10m
2026-07-13 VTU880 - Jul 13, 01:01 UTCJul 13, 01:20 UTC20m
2026-07-10 VTU6311 PZO → VLN Jul 10, 14:35 UTCJul 10, 15:05 UTC30m
2026-07-10 VTU6310 VLN → PZO Jul 10, 12:40 UTCJul 10, 13:15 UTC35m
2026-07-09 VTU881 BOG → VLN Jul 9, 16:00 UTCJul 10, 13:15 UTC21h 15m
2026-07-09 VTU880 VLN → BOG Jul 9, 13:50 UTCJul 9, 14:20 UTC30m
2026-07-06 VTU6311 PZO → VLN Jul 6, 14:10 UTCJul 6, 14:40 UTC30m
2026-07-06 VTU6310 VLN → PZO Jul 6, 00:05 UTCJul 6, 12:55 UTC12h 50m
2026-07-03 VTU6311 PZO → VLN Jul 3, 14:25 UTCJul 3, 14:55 UTC30m
2026-07-03 VTU6310 VLN → PZO Jul 3, 12:35 UTCJul 3, 13:10 UTC35m
2026-06-26 VTU6311 PZO → VLN Jun 26, 14:19 UTCJun 26, 14:44 UTC25m
2026-06-26 VTU6310 VLN → PZO Jun 26, 12:39 UTCJun 26, 13:10 UTC30m
2026-06-19 VTU6311 PZO → VLN Jun 19, 14:09 UTCJun 19, 14:34 UTC25m
2026-06-19 VTU6310 VLN → PZO Jun 19, 12:14 UTCJun 19, 12:49 UTC35m
2026-06-18 VTU6310 VLN → PZO Jun 18, 15:35 UTCJun 19, 12:49 UTC21h 14m
2026-06-18 VTU6310 VLN → PZO Jun 18, 15:20 UTCJun 19, 12:49 UTC21h 29m
2026-06-18 VTU880 VLN → BOG Jun 18, 13:40 UTCJun 18, 14:05 UTC25m
2026-06-12 VTU6311 PZO → VLN Jun 12, 14:20 UTCJun 12, 14:45 UTC25m
2026-06-12 VTU6310 VLN → PZO Jun 12, 12:30 UTCJun 12, 13:05 UTC35m
2026-06-05 VTU6311 PZO → VLN Jun 5, 14:40 UTCJun 5, 15:00 UTC20m
2026-06-05 VTU6310 VLN → PZO Jun 5, 12:15 UTCJun 5, 13:10 UTC55m
2026-06-04 VTU881 BOG → VLN Jun 4, 15:25 UTCJun 4, 15:35 UTC10m
2026-06-04 VTU880 VLN → BOG Jun 4, 13:25 UTCJun 4, 13:50 UTC25m
2026-06-01 VTU881 BOG → VLN Jun 1, 00:10 UTCJun 1, 00:25 UTC15m
2026-05-31 VTU880 VLN → BOG May 31, 22:20 UTCMay 31, 22:40 UTC20m
2026-05-29 VTU6311 PZO → VLN May 29, 14:10 UTCMay 29, 14:35 UTC25m
2026-05-29 VTU6310 VLN → PZO May 29, 12:25 UTCMay 29, 12:55 UTC30m
2026-05-28 VTU6310 VLN → PZO May 28, 15:45 UTCMay 29, 12:55 UTC21h 10m
2026-05-28 VTU880 VLN → BOG May 28, 13:30 UTCMay 28, 13:55 UTC25m
2026-05-22 VTU6311 PZO → VLN May 22, 14:25 UTCMay 22, 14:55 UTC30m
2026-05-22 VTU6310 VLN → PZO May 22, 12:35 UTCMay 22, 13:05 UTC30m
2026-05-21 VTU881 BOG → VLN May 21, 15:55 UTCMay 22, 13:05 UTC21h 10m
2026-05-21 VTU880 VLN → BOG May 21, 13:40 UTCMay 21, 14:05 UTC25m
2026-05-17 VTU881 BOG → VLN May 17, 23:45 UTCMay 18, 00:00 UTC15m
2026-05-17 VTU880 VLN → BOG May 17, 22:01 UTCMay 17, 22:20 UTC20m
2026-05-15 VTU6311 PZO → VLN May 15, 14:10 UTCMay 15, 14:40 UTC30m
2026-05-15 VTU6310 VLN → PZO May 15, 12:30 UTCMay 15, 13:00 UTC30m
2026-05-08 VTU6311 PZO → VLN May 8, 14:20 UTCMay 8, 14:50 UTC30m
2026-05-08 VTU6310 VLN → PZO May 8, 12:20 UTCMay 8, 12:49 UTC30m
2026-05-01 VTU6311 PZO → VLN May 1, 14:30 UTCMay 1, 15:00 UTC30m
2026-05-01 VTU6310 VLN → PZO May 1, 12:40 UTCMay 1, 13:10 UTC30m
2026-04-26 VTU881 BOG → VLN Apr 26, 23:50 UTCApr 27, 00:05 UTC15m
2026-04-26 VTU880 VLN → BOG Apr 26, 22:05 UTCApr 26, 22:30 UTC25m
2026-04-24 VTU6311 - Apr 24, 14:20 UTCApr 24, 14:45 UTC25m
2026-04-24 VTU6310 VLN → PZO Apr 24, 12:15 UTCApr 24, 12:45 UTC30m

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 YV621T page for operator, model, and routing details .

Mode-S 0D82BE frequently asked

What is Mode-S code 0D82BE?
0D82BE is an ICAO 24-bit transponder address. Allocated to Venezuela. Assigned to YV621T.
Where is Mode-S 0D82BE registered?
Mode-S code 0D82BE is allocated to Venezuela (VE). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 0D82BE broadcasting right now?
No active broadcast right now. Last signal was 11h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 0D82BE, octal 03301276, decimal 885,438.
What flights does 0D82BE operate?
Mode-S 0D82BE has broadcast 6 distinct callsigns, including VTU6310, VTU6311, VTU880, VTU881, VTU8930.