sensors Mode-S transponder

68332B

ICAO 24-bit transponder address · allocated to Kazakhstan

Currently assigned to UP-B3739 · BOEING 737 MAX 9

Hex
68332B
Octal
32031453
Decimal
6,828,843
Country
KZ
Tail
UP-B3739
Type
B39M
No current signal · last broadcast 1d ago
Flights observed
64
Distinct callsigns
13
Country
KZ
Last broadcast
1d ago

Last known position

Most recent position reported by Mode-S 68332B.

Country allocation

The ICAO 24-bit address 68332B 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 13 distinct

Callsign Airline Flights Last seen
VSV481 Scat Air 17 2026-05-21
VSV5380 Scat Air 13 2026-05-26
VSV482 Scat Air 13 2026-05-24
VSV5381 - 7 2026-05-23
VSV5348 - 3 2026-04-15
VSV5321 Scat Air 2 2026-04-24
VSV5320 - 2 2026-04-23
VSV475 Scat Air 2 2026-05-09
VSV5370 - 1 2026-05-27
VSV5369 - 1 2026-05-26
VSV5287 - 1 2026-05-27
VSV5274 - 1 2026-05-28
VSV479 Scat Air 1 2026-04-15

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-05-28 VSV5274 - May 28, 11:25 UTCMay 29, 02:00 UTC14h 35m
2026-05-27 VSV5370 - May 27, 16:20 UTCMay 28, 09:25 UTC17h 5m
2026-05-27 VSV5287 - May 27, 03:39 UTCMay 27, 13:00 UTC9h 21m
2026-05-26 VSV5369 - May 26, 08:10 UTCMay 27, 00:25 UTC16h 15m
2026-05-26 VSV5380 ALA → DOH May 26, 01:34 UTCMay 26, 04:24 UTC2h 50m
2026-05-24 VSV482 PRG → FRU May 24, 16:05 UTCMay 24, 17:40 UTC1h 35m
2026-05-23 VSV5381 - May 23, 07:45 UTCMay 23, 16:25 UTC8h 40m
2026-05-23 VSV5380 ALA → DOH May 23, 01:45 UTCMay 23, 04:30 UTC2h 44m
2026-05-21 VSV482 PRG → FRU May 21, 18:05 UTCMay 21, 19:45 UTC1h 40m
2026-05-21 VSV481 FRU → PRG May 21, 15:45 UTCMay 21, 17:00 UTC1h 15m
2026-05-19 VSV5381 - May 19, 07:25 UTCMay 19, 22:05 UTC14h 40m
2026-05-19 VSV5380 ALA → DOH May 19, 01:35 UTCMay 19, 04:15 UTC2h 40m
2026-05-17 VSV482 PRG → FRU May 17, 16:10 UTCMay 17, 17:40 UTC1h 30m
2026-05-17 VSV481 FRU → PRG May 17, 13:20 UTCMay 17, 14:30 UTC1h 10m
2026-05-16 VSV481 FRU → PRG May 16, 16:05 UTCMay 17, 14:30 UTC22h 25m
2026-05-16 VSV5381 - May 16, 07:31 UTCMay 16, 16:31 UTC9h 0m
2026-05-16 VSV5380 ALA → DOH May 16, 00:25 UTCMay 16, 03:55 UTC3h 30m
2026-05-14 VSV482 PRG → FRU May 14, 18:00 UTCMay 14, 20:20 UTC2h 20m
2026-05-14 VSV481 FRU → PRG May 14, 15:05 UTCMay 14, 16:20 UTC1h 15m
2026-05-13 VSV481 FRU → PRG May 13, 19:00 UTCMay 14, 16:20 UTC21h 20m
2026-05-12 VSV5381 - May 12, 03:10 UTCMay 12, 11:10 UTC8h 0m
2026-05-10 VSV482 PRG → FRU May 10, 16:34 UTCMay 10, 19:05 UTC2h 30m
2026-05-10 VSV481 FRU → PRG May 10, 14:25 UTCMay 10, 15:19 UTC55m
2026-05-09 VSV475 NQZ → SYX May 9, 16:20 UTCMay 10, 14:45 UTC22h 25m
2026-05-09 VSV5380 ALA → DOH May 9, 01:45 UTCMay 9, 16:40 UTC14h 55m
2026-05-08 VSV5380 ALA → DOH May 8, 19:10 UTCMay 9, 16:40 UTC21h 30m
2026-05-07 VSV482 PRG → FRU May 7, 18:05 UTCMay 7, 19:45 UTC1h 40m
2026-05-07 VSV481 FRU → PRG May 7, 15:15 UTCMay 7, 16:30 UTC1h 15m
2026-05-06 VSV481 FRU → PRG May 6, 19:20 UTCMay 7, 16:30 UTC21h 11m
2026-05-05 VSV5381 - May 5, 07:50 UTCMay 5, 10:30 UTC2h 40m
2026-05-05 VSV5380 ALA → DOH May 5, 01:30 UTCMay 5, 04:20 UTC2h 50m
2026-05-03 VSV482 PRG → FRU May 3, 15:45 UTCMay 3, 17:35 UTC1h 50m
2026-05-03 VSV481 FRU → PRG May 3, 13:05 UTCMay 3, 14:10 UTC1h 5m
2026-05-02 VSV481 FRU → PRG May 2, 15:55 UTCMay 3, 14:10 UTC22h 14m
2026-05-02 VSV5380 ALA → DOH May 2, 01:30 UTCMay 2, 16:20 UTC14h 51m
2026-04-30 VSV482 PRG → FRU Apr 30, 18:10 UTCApr 30, 20:45 UTC2h 35m
2026-04-30 VSV481 FRU → PRG Apr 30, 15:15 UTCApr 30, 16:15 UTC1h 0m
2026-04-29 VSV481 FRU → PRG Apr 29, 18:50 UTCApr 30, 16:15 UTC21h 25m
2026-04-28 VSV5381 - Apr 28, 02:10 UTCApr 28, 18:00 UTC15h 50m
2026-04-26 VSV482 PRG → FRU Apr 26, 16:55 UTCApr 26, 19:05 UTC2h 10m
2026-04-26 VSV481 FRU → PRG Apr 26, 14:30 UTCApr 26, 15:45 UTC1h 15m
2026-04-25 VSV475 NQZ → SYX Apr 25, 15:45 UTCApr 26, 14:45 UTC23h 0m
2026-04-25 VSV5380 ALA → DOH Apr 25, 01:45 UTCApr 25, 16:05 UTC14h 20m
2026-04-24 VSV5380 ALA → DOH Apr 24, 06:50 UTCApr 25, 04:50 UTC22h 0m
2026-04-24 VSV5321 ALA → ALA Apr 24, 04:50 UTCApr 25, 04:45 UTC23h 55m
2026-04-24 VSV5321 ALA → ALA Apr 24, 04:10 UTCApr 25, 02:35 UTC22h 25m
2026-04-23 VSV5320 - Apr 23, 23:00 UTCApr 24, 00:10 UTC1h 10m
2026-04-23 VSV5320 - Apr 23, 20:00 UTCApr 23, 22:25 UTC2h 25m
2026-04-19 VSV482 PRG → FRU Apr 19, 16:35 UTCApr 19, 18:50 UTC2h 15m
2026-04-19 VSV481 FRU → PRG Apr 19, 14:05 UTCApr 19, 15:25 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-B3739 page for operator, model, and routing details .

Mode-S 68332B frequently asked

What is Mode-S code 68332B?
68332B is an ICAO 24-bit transponder address. Allocated to Kazakhstan. Assigned to UP-B3739.
Where is Mode-S 68332B registered?
Mode-S code 68332B is allocated to Kazakhstan (KZ). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 68332B 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 68332B, octal 32031453, decimal 6,828,843.
What flights does 68332B operate?
Mode-S 68332B has broadcast 13 distinct callsigns, including VSV481, VSV5380, VSV482, VSV5381, VSV5348.