sensors Mode-S transponder

683324

ICAO 24-bit transponder address · allocated to Kazakhstan

Currently assigned to UP-B3734 · BOEING 737-800

Hex
683324
Octal
32031444
Decimal
6,828,836
Country
KZ
Tail
UP-B3734
Type
B738
No current signal · last broadcast 9d ago
Flights observed
53
Distinct callsigns
9
Country
KZ
Last broadcast
9d ago

Last known position

Most recent position reported by Mode-S 683324.

Country allocation

The ICAO 24-bit address 683324 falls within the block assigned to Kazakhstan (KZ) by ICAO Annex 10, Volume III. Every aircraft registered in Kazakhstan 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 9 distinct

Callsign Airline Flights Last seen
VSV809 Scat Air 21 2026-07-24
VSV810 Scat Air 11 2026-07-25
VSV807 Scat Air 8 2026-07-26
VSV808 Scat Air 7 2026-07-26
VSV486 Scat Air 2 2026-05-17
VSV801 Scat Air 1 2026-05-15
VSV726 - 1 2026-07-02
VSV725 - 1 2026-07-02
VSV485 Scat Air 1 2026-05-17

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-26 VSV808 MSQ → ALA Jul 26, 07:20 UTCJul 26, 07:30 UTC10m
2026-07-26 VSV807 ALA → MSQ Jul 26, 05:25 UTCJul 26, 05:35 UTC10m
2026-07-25 VSV810 VKO → ALA Jul 25, 09:30 UTCJul 25, 10:05 UTC35m
2026-07-24 VSV809 ALA → VKO Jul 24, 04:45 UTCJul 24, 05:05 UTC20m
2026-07-22 VSV807 ALA → MSQ Jul 22, 05:10 UTCJul 22, 05:25 UTC15m
2026-07-20 VSV810 VKO → ALA Jul 20, 08:35 UTCJul 20, 09:10 UTC35m
2026-07-19 VSV808 MSQ → ALA Jul 19, 07:40 UTCJul 19, 07:50 UTC10m
2026-07-15 VSV807 - Jul 15, 03:15 UTCJul 15, 03:55 UTC40m
2026-07-11 VSV810 - Jul 11, 07:45 UTCJul 11, 07:55 UTC10m
2026-07-09 VSV810 - Jul 9, 07:20 UTCJul 9, 07:40 UTC20m
2026-07-02 VSV726 - Jul 2, 23:25 UTCJul 2, 23:45 UTC20m
2026-07-02 VSV725 - Jul 2, 21:35 UTCJul 2, 22:00 UTC25m
2026-06-28 VSV808 - Jun 28, 07:25 UTCJun 28, 07:40 UTC15m
2026-06-25 VSV810 VKO → ALA Jun 25, 07:19 UTCJun 25, 07:30 UTC10m
2026-06-24 VSV808 - Jun 24, 07:10 UTCJun 24, 07:30 UTC20m
2026-06-23 VSV809 - Jun 23, 05:00 UTCJun 23, 05:20 UTC20m
2026-06-17 VSV808 MSQ → ALA Jun 17, 07:15 UTCJun 17, 07:30 UTC15m
2026-06-15 VSV809 - Jun 15, 04:15 UTCJun 15, 09:20 UTC5h 5m
2026-06-13 VSV809 ALA → VKO Jun 13, 04:20 UTCJun 13, 08:35 UTC4h 15m
2026-06-12 VSV809 ALA → VKO Jun 12, 08:20 UTCJun 13, 04:55 UTC20h 34m
2026-06-12 VSV809 ALA → VKO Jun 12, 04:20 UTCJun 12, 08:20 UTC4h 0m
2026-06-11 VSV809 ALA → VKO Jun 11, 09:05 UTCJun 12, 08:20 UTC23h 16m
2026-06-11 VSV809 ALA → VKO Jun 11, 05:05 UTCJun 12, 04:55 UTC23h 51m
2026-06-11 VSV809 ALA → VKO Jun 11, 04:25 UTCJun 11, 09:25 UTC5h 0m
2026-06-10 VSV809 ALA → VKO Jun 10, 09:15 UTCJun 11, 09:00 UTC23h 45m
2026-06-10 VSV809 ALA → VKO Jun 10, 07:20 UTCJun 11, 05:05 UTC21h 45m
2026-06-10 VSV807 ALA → MSQ Jun 10, 03:30 UTCJun 10, 04:00 UTC30m
2026-06-08 VSV810 VKO → ALA Jun 8, 04:05 UTCJun 8, 08:30 UTC4h 25m
2026-06-07 VSV810 VKO → ALA Jun 7, 09:20 UTCJun 8, 08:30 UTC23h 10m
2026-06-07 VSV807 ALA → MSQ Jun 7, 03:25 UTCJun 7, 09:20 UTC5h 55m
2026-06-05 VSV810 VKO → ALA Jun 5, 09:25 UTCJun 6, 04:35 UTC19h 10m
2026-06-05 VSV810 VKO → ALA Jun 5, 04:05 UTCJun 5, 09:55 UTC5h 50m
2026-06-03 VSV807 ALA → MSQ Jun 3, 03:05 UTCJun 3, 03:45 UTC40m
2026-06-02 VSV809 ALA → VKO Jun 2, 04:15 UTCJun 2, 04:45 UTC30m
2026-06-01 VSV809 ALA → VKO Jun 1, 08:35 UTCJun 2, 04:45 UTC20h 10m
2026-06-01 VSV809 ALA → VKO Jun 1, 04:20 UTCJun 1, 08:40 UTC4h 20m
2026-05-30 VSV810 VKO → ALA May 30, 04:15 UTCMay 30, 08:20 UTC4h 5m
2026-05-29 VSV809 ALA → VKO May 29, 04:25 UTCMay 29, 05:00 UTC35m
2026-05-28 VSV809 ALA → VKO May 28, 08:30 UTCMay 29, 05:00 UTC20h 30m
2026-05-27 VSV808 MSQ → ALA May 27, 07:15 UTCMay 27, 07:25 UTC10m
2026-05-27 VSV807 ALA → MSQ May 27, 02:04 UTCMay 27, 03:29 UTC1h 25m
2026-05-26 VSV809 ALA → VKO May 26, 04:15 UTCMay 26, 04:45 UTC30m
2026-05-23 VSV809 ALA → VKO May 23, 04:20 UTCMay 23, 04:50 UTC30m
2026-05-21 VSV809 ALA → VKO May 21, 04:35 UTCMay 21, 05:00 UTC25m
2026-05-20 VSV809 ALA → VKO May 20, 08:50 UTCMay 21, 05:00 UTC20h 10m
2026-05-20 VSV808 MSQ → ALA May 20, 07:05 UTCMay 20, 07:20 UTC15m
2026-05-20 VSV807 ALA → MSQ May 20, 02:15 UTCMay 20, 02:25 UTC10m
2026-05-17 VSV486 IST → CIT May 17, 10:00 UTCMay 17, 11:05 UTC1h 5m
2026-05-17 VSV486 IST → CIT May 17, 09:10 UTCMay 17, 09:20 UTC10m
2026-05-17 VSV485 CIT → IST May 17, 04:55 UTCMay 17, 06:15 UTC1h 20m

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

Mode-S 683324 frequently asked

What is Mode-S code 683324?
683324 is an ICAO 24-bit transponder address. Allocated to Kazakhstan. Assigned to UP-B3734.
Where is Mode-S 683324 registered?
Mode-S code 683324 is allocated to Kazakhstan (KZ). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 683324 broadcasting right now?
No active broadcast right now. Last signal was 9d ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 683324, octal 32031444, decimal 6,828,836.
What flights does 683324 operate?
Mode-S 683324 has broadcast 9 distinct callsigns, including VSV809, VSV810, VSV807, VSV808, VSV486.