Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

A83DD0

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N630AV · operated by CIRRUS DESIGN CORP

Hex
A83DD0
Octal
52036720
Decimal
11,025,872
Country
US
Tail
N630AV
Type
SR20
No current signal · last broadcast 1d ago
Flights observed
206
Distinct callsigns
1
Country
US
Last broadcast
1d ago

Last known position

Most recent position reported by Mode-S A83DD0.

Country allocation

The ICAO 24-bit address A83DD0 falls within the block assigned to United States (US) by ICAO Annex 10, Volume III. Every aircraft registered in United States 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
VAR630 - 206 2026-07-17

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-17 VAR630 GYR → GYR Jul 17, 01:29 UTCJul 17, 03:20 UTC1h 50m
2026-07-16 VAR630 GYR → GYR Jul 16, 19:10 UTCJul 16, 20:39 UTC1h 30m
2026-07-16 VAR630 GYR → GYR Jul 16, 16:15 UTCJul 16, 18:05 UTC1h 50m
2026-07-15 VAR630 GYR → GYR Jul 15, 19:20 UTCJul 15, 20:30 UTC1h 10m
2026-07-15 VAR630 GYR → GYR Jul 15, 16:30 UTCJul 15, 17:20 UTC50m
2026-07-15 VAR630 - Jul 15, 06:10 UTCJul 15, 06:15 UTC5m
2026-07-15 VAR630 GYR → GYR Jul 15, 05:45 UTCJul 15, 05:50 UTC5m
2026-07-11 VAR630 GYR → GYR Jul 11, 19:00 UTCJul 11, 20:45 UTC1h 45m
2026-07-09 VAR630 GYR → GYR Jul 9, 16:05 UTCJul 9, 17:35 UTC1h 30m
2026-07-09 VAR630 GYR → GYR Jul 9, 00:15 UTCJul 9, 03:20 UTC3h 5m
2026-07-08 VAR630 - Jul 8, 18:10 UTCJul 8, 20:15 UTC2h 5m
2026-07-08 VAR630 - Jul 8, 14:30 UTCJul 8, 16:50 UTC2h 20m
2026-07-07 VAR630 GYR → GYR Jul 7, 13:55 UTCJul 7, 15:20 UTC1h 25m
2026-07-06 VAR630 GYR → GYR Jul 6, 17:15 UTCJul 6, 19:05 UTC1h 50m
2026-07-05 VAR630 GYR → GYR Jul 5, 02:05 UTCJul 5, 02:55 UTC50m
2026-07-04 VAR630 GYR → GYR Jul 4, 17:10 UTCJul 4, 19:00 UTC1h 50m
2026-07-04 VAR630 GYR → GYR Jul 4, 13:50 UTCJul 4, 15:30 UTC1h 40m
2026-07-03 VAR630 GYR → GYR Jul 3, 15:25 UTCJul 3, 17:15 UTC1h 50m
2026-07-03 VAR630 GYR → GYR Jul 3, 01:35 UTCJul 3, 03:35 UTC2h 0m
2026-07-02 VAR630 GYR → GYR Jul 2, 19:35 UTCJul 2, 20:50 UTC1h 15m
2026-07-02 VAR630 GYR → GYR Jul 2, 16:00 UTCJul 2, 17:35 UTC1h 35m
2026-07-02 VAR630 - Jul 2, 00:35 UTCJul 2, 02:40 UTC2h 5m
2026-07-01 VAR630 GYR → GYR Jul 1, 21:15 UTCJul 1, 23:00 UTC1h 45m
2026-07-01 VAR630 GYR → GYR Jul 1, 18:00 UTCJul 1, 20:05 UTC2h 5m
2026-07-01 VAR630 GYR → GYR Jul 1, 14:55 UTCJul 1, 16:20 UTC1h 25m
2026-07-01 VAR630 GYR → GYR Jul 1, 00:10 UTCJul 1, 01:55 UTC1h 45m
2026-06-30 VAR630 GYR → GYR Jun 30, 19:25 UTCJun 30, 20:35 UTC1h 10m
2026-06-30 VAR630 GYR → GYR Jun 30, 15:25 UTCJun 30, 17:30 UTC2h 5m
2026-06-28 VAR630 - Jun 28, 20:45 UTCJun 28, 22:20 UTC1h 35m
2026-06-28 VAR630 GYR → GYR Jun 28, 15:40 UTCJun 28, 17:30 UTC1h 50m
2026-06-27 VAR630 - Jun 27, 22:25 UTCJun 27, 22:40 UTC15m
2026-06-27 VAR630 - Jun 27, 19:05 UTCJun 27, 21:04 UTC2h 0m
2026-06-27 VAR630 GYR → GYR Jun 27, 14:05 UTCJun 27, 16:24 UTC2h 20m
2026-06-26 VAR630 GYR → GYR Jun 26, 23:25 UTCJun 27, 00:14 UTC50m
2026-06-26 VAR630 GYR → GYR Jun 26, 19:55 UTCJun 26, 21:04 UTC1h 10m
2026-06-26 VAR630 GYR → GYR Jun 26, 15:54 UTCJun 26, 17:00 UTC1h 5m
2026-06-26 VAR630 GYR → GYR Jun 26, 13:34 UTCJun 26, 14:39 UTC1h 5m
2026-06-25 VAR630 GYR → GYR Jun 25, 22:54 UTCJun 25, 23:39 UTC45m
2026-06-25 VAR630 GYR → GYR Jun 25, 20:05 UTCJun 25, 21:15 UTC1h 10m
2026-06-25 VAR630 GYR → GYR Jun 25, 15:20 UTCJun 25, 15:29 UTC10m
2026-06-24 VAR630 GYR → GYR Jun 24, 16:05 UTCJun 24, 17:10 UTC1h 5m
2026-06-24 VAR630 GYR → GYR Jun 24, 13:50 UTCJun 24, 15:05 UTC1h 15m
2026-06-23 VAR630 GYR → GYR Jun 23, 21:39 UTCJun 23, 23:05 UTC1h 25m
2026-06-23 VAR630 GYR → GYR Jun 23, 18:55 UTCJun 23, 20:29 UTC1h 35m
2026-06-23 VAR630 - Jun 23, 15:59 UTCJun 23, 17:20 UTC1h 20m
2026-06-23 VAR630 - Jun 23, 14:44 UTCJun 23, 15:24 UTC40m
2026-06-22 VAR630 GYR → GYR Jun 22, 21:54 UTCJun 22, 23:14 UTC1h 20m
2026-06-22 VAR630 GYR → GYR Jun 22, 17:29 UTCJun 22, 19:00 UTC1h 30m
2026-06-22 VAR630 GYR → GYR Jun 22, 14:10 UTCJun 22, 16:24 UTC2h 15m
2026-06-21 VAR630 - Jun 21, 18:00 UTCJun 21, 19:45 UTC1h 45m

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

Mode-S A83DD0 frequently asked

What is Mode-S code A83DD0?
A83DD0 is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N630AV.
Where is Mode-S A83DD0 registered?
Mode-S code A83DD0 is allocated to United States (US). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is A83DD0 broadcasting right now?
No active broadcast right now. Last signal was 1d ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex A83DD0, octal 52036720, decimal 11,025,872.
What flights does A83DD0 operate?
Mode-S A83DD0 has broadcast 1 distinct callsign, including VAR630.