sensors Mode-S transponder

683296

ICAO 24-bit transponder address · allocated to Kazakhstan

Currently assigned to UP-B3730 · BOEING 737-800

Hex
683296
Octal
32031226
Decimal
6,828,694
Country
KZ
Tail
UP-B3730
Type
B738
No current signal · last broadcast Jul 26, 09:55 UTC
Flights observed
82
Distinct callsigns
16
Country
KZ
Last broadcast
Jul 26, 09:55 UTC

Last known position

Most recent position reported by Mode-S 683296.

Country allocation

The ICAO 24-bit address 683296 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 16 distinct

Callsign Airline Flights Last seen
VSV803 - 21 2026-07-21
VSV804 Scat Air 16 2026-07-25
VSV822 Scat Air 14 2026-07-26
VSV821 Scat Air 7 2026-07-24
VSV813 Scat Air 5 2026-06-03
VSV818 Scat Air 3 2026-04-22
VSV784 Scat Air 3 2026-06-13
VSV783 Scat Air 2 2026-06-14
VSV732 Scat Air 2 2026-05-18
VSV731 Scat Air 2 2026-05-17
VSV725 Scat Air 2 2026-05-28
VSV817 Scat Air 1 2026-04-22
VSV730D - 1 2026-05-17
VSV730 Scat Air 1 2026-05-15
VSV703 Scat Air 1 2026-04-17
VS784 - 1 2026-06-14

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-26 VSV822 LED → NQZ Jul 26, 09:40 UTCJul 26, 09:55 UTC15m
2026-07-25 VSV804 DME → AKX Jul 25, 11:50 UTCJul 25, 13:30 UTC1h 40m
2026-07-24 VSV821 NQZ → LED Jul 24, 06:05 UTCJul 24, 06:40 UTC35m
2026-07-21 VSV804 - Jul 21, 11:25 UTCJul 21, 14:55 UTC3h 30m
2026-07-21 VSV803 - Jul 21, 08:30 UTCJul 21, 09:10 UTC40m
2026-07-20 VSV822 LED → NQZ Jul 20, 09:45 UTCJul 20, 09:55 UTC10m
2026-07-18 VSV804 - Jul 18, 11:40 UTCJul 18, 15:00 UTC3h 20m
2026-07-18 VSV803 - Jul 18, 06:25 UTCJul 18, 07:00 UTC35m
2026-07-17 VSV803 - Jul 17, 07:40 UTCJul 18, 07:00 UTC23h 21m
2026-07-17 VSV821 NQZ → LED Jul 17, 06:29 UTCJul 17, 08:10 UTC1h 40m
2026-07-10 VSV821 - Jul 10, 06:55 UTCJul 10, 07:10 UTC15m
2026-07-04 VSV804 - Jul 4, 11:40 UTCJul 4, 13:20 UTC1h 40m
2026-07-04 VSV803 - Jul 4, 08:30 UTCJul 4, 09:45 UTC1h 15m
2026-07-03 VSV803 - Jul 3, 10:40 UTCJul 4, 09:30 UTC22h 50m
2026-06-27 VSV804 - Jun 27, 11:39 UTCJun 27, 13:24 UTC1h 45m
2026-06-27 VSV803 - Jun 27, 07:24 UTCJun 27, 10:05 UTC2h 40m
2026-06-23 VSV804 - Jun 23, 11:40 UTCJun 23, 13:19 UTC1h 40m
2026-06-23 VSV803 - Jun 23, 08:35 UTCJun 23, 09:14 UTC40m
2026-06-22 VSV821 - Jun 22, 07:25 UTCJun 22, 07:34 UTC10m
2026-06-20 VSV804 - Jun 20, 12:14 UTCJun 20, 13:59 UTC1h 45m
2026-06-20 VSV803 - Jun 20, 10:09 UTCJun 20, 10:44 UTC35m
2026-06-16 VSV804 DME → AKX Jun 16, 11:30 UTCJun 16, 13:09 UTC1h 40m
2026-06-16 VSV803 - Jun 16, 08:30 UTCJun 16, 09:10 UTC40m
2026-06-15 VSV822 LED → NQZ Jun 15, 09:40 UTCJun 15, 09:54 UTC15m
2026-06-14 VS784 - Jun 14, 07:35 UTCJun 14, 08:00 UTC25m
2026-06-14 VSV783 NQZ → UKK Jun 14, 05:45 UTCJun 14, 06:05 UTC20m
2026-06-13 VSV784 UKK → NQZ Jun 13, 10:25 UTCJun 14, 06:05 UTC19h 41m
2026-06-13 VSV783 NQZ → UKK Jun 13, 06:05 UTCJun 13, 06:30 UTC25m
2026-06-12 VSV822 LED → NQZ Jun 12, 09:55 UTCJun 12, 10:10 UTC15m
2026-06-11 VSV822 LED → NQZ Jun 11, 09:55 UTCJun 11, 10:10 UTC15m
2026-06-10 VSV822 LED → NQZ Jun 10, 09:55 UTCJun 10, 10:05 UTC10m
2026-06-09 VSV804 DME → AKX Jun 9, 11:50 UTCJun 10, 06:50 UTC19h 0m
2026-06-09 VSV803 AKX → DME Jun 9, 05:10 UTCJun 9, 05:50 UTC40m
2026-06-06 VSV804 DME → AKX Jun 6, 11:39 UTCJun 6, 13:15 UTC1h 35m
2026-06-06 VSV803 AKX → DME Jun 6, 09:39 UTCJun 6, 10:20 UTC40m
2026-06-05 VSV822 LED → NQZ Jun 5, 10:50 UTCJun 5, 11:20 UTC30m
2026-06-05 VSV821 NQZ → LED Jun 5, 07:10 UTCJun 5, 07:25 UTC15m
2026-06-03 VSV813 ALA → TAS Jun 3, 07:35 UTCJun 3, 22:50 UTC15h 15m
2026-06-02 VSV804 DME → AKX Jun 2, 11:35 UTCJun 3, 06:05 UTC18h 30m
2026-06-01 VSV803 AKX → DME Jun 1, 18:05 UTCJun 2, 10:05 UTC16h 0m
2026-06-01 VSV822 LED → NQZ Jun 1, 10:40 UTCJun 2, 09:30 UTC22h 50m
2026-05-29 VSV822 LED → NQZ May 29, 06:00 UTCMay 29, 10:55 UTC4h 55m
2026-05-28 VSV784 UKK → NQZ May 28, 12:55 UTCMay 29, 10:55 UTC22h 0m
2026-05-28 VSV725 ALA → UKK May 28, 09:55 UTCMay 28, 10:15 UTC20m
2026-05-26 VSV804 DME → AKX May 26, 11:09 UTCMay 26, 15:24 UTC4h 15m
2026-05-26 VSV803 AKX → DME May 26, 04:54 UTCMay 26, 09:29 UTC4h 35m
2026-05-23 VSV803 AKX → DME May 23, 05:30 UTCMay 23, 09:55 UTC4h 25m
2026-05-22 VSV803 AKX → DME May 22, 12:25 UTCMay 23, 09:55 UTC21h 29m
2026-05-22 VSV803 AKX → DME May 22, 11:15 UTCMay 23, 09:30 UTC22h 14m
2026-05-22 VSV822 LED → NQZ May 22, 09:45 UTCMay 22, 10:10 UTC25m

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

Mode-S 683296 frequently asked

What is Mode-S code 683296?
683296 is an ICAO 24-bit transponder address. Allocated to Kazakhstan. Assigned to UP-B3730.
Where is Mode-S 683296 registered?
Mode-S code 683296 is allocated to Kazakhstan (KZ). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 683296 broadcasting right now?
No active broadcast right now. Last signal was Jul 26, 09:55 UTC.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 683296, octal 32031226, decimal 6,828,694.
What flights does 683296 operate?
Mode-S 683296 has broadcast 16 distinct callsigns, including VSV803, VSV804, VSV822, VSV821, VSV813.