Apparatus

Try JFK, AAL1290, BAW, or N225AN.

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
Broadcasting now · callsign VSV5265 · 34,000 ft
Flights observed
159
Distinct callsigns
20
Country
KZ
Last broadcast
Jul 26, 17:30 UTC

Current position

68332B is currently broadcasting. Map zoomed to live position.

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 20 distinct

Callsign Airline Flights Last seen
VSV481 Scat Air 27 2026-07-26
VSV482 Scat Air 20 2026-07-26
VSV5380 Scat Air 18 2026-07-21
VSV5381 - 13 2026-07-25
VSV5342 - 9 2026-06-21
VSV5369 - 7 2026-06-23
VSV5350 - 7 2026-06-20
VSV5273 - 7 2026-07-04
VSV479 - 5 2026-07-14
VSV475 - 5 2026-06-27
VSV5370 - 4 2026-06-24
VSV5382 - 3 2026-07-14
VSV5348 - 3 2026-04-15
VSV5288 - 3 2026-06-24
VSV5274 - 3 2026-06-11
VSV5240 - 3 2026-07-23
VSV473 Scat Air 3 2026-06-26
VSV5321 Scat Air 2 2026-04-24
VSV5320 - 2 2026-04-23
VSV5287 - 2 2026-06-10

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-26 VSV482 PRG → FRU Jul 26, 16:00 UTCJul 26, 17:30 UTC1h 30m
2026-07-26 VSV481 FRU → PRG Jul 26, 13:15 UTCJul 26, 14:25 UTC1h 10m
2026-07-25 VSV5381 - Jul 25, 07:30 UTCJul 25, 20:20 UTC12h 50m
2026-07-24 VSV5266 - Jul 24, 18:05 UTCJul 25, 05:40 UTC11h 35m
2026-07-23 VSV5240 - Jul 23, 13:50 UTCJul 24, 03:25 UTC13h 35m
2026-07-23 VSV5240 - Jul 23, 06:50 UTCJul 24, 03:25 UTC20h 35m
2026-07-23 VSV5240 - Jul 23, 04:50 UTCJul 24, 03:25 UTC22h 35m
2026-07-23 VSV5241 - Jul 23, 04:35 UTCJul 24, 02:45 UTC22h 10m
2026-07-21 VSV5264 - Jul 21, 17:20 UTCJul 22, 04:45 UTC11h 25m
2026-07-21 VSV5380 ALA → DOH Jul 21, 01:35 UTCJul 21, 04:15 UTC2h 40m
2026-07-19 VSV482 - Jul 19, 16:05 UTCJul 19, 17:25 UTC1h 20m
2026-07-19 VSV481 - Jul 19, 14:00 UTCJul 19, 14:45 UTC45m
2026-07-18 VSV481 - Jul 18, 14:55 UTCJul 19, 14:45 UTC23h 50m
2026-07-18 VSV5381 - Jul 18, 06:40 UTCJul 18, 15:15 UTC8h 35m
2026-07-18 VSV5380 ALA → DOH Jul 18, 01:45 UTCJul 18, 04:40 UTC2h 56m
2026-07-16 VSV482 - Jul 16, 15:55 UTCJul 16, 17:25 UTC1h 30m
2026-07-15 VSV481 - Jul 15, 19:55 UTCJul 16, 14:45 UTC18h 50m
2026-07-15 VSV481 - Jul 15, 14:55 UTCJul 16, 14:45 UTC23h 50m
2026-07-14 VSV479 - Jul 14, 23:10 UTCJul 15, 20:00 UTC20h 50m
2026-07-14 VSV5382 - Jul 14, 18:25 UTCJul 15, 15:15 UTC20h 49m
2026-07-14 VSV5381 - Jul 14, 06:50 UTCJul 15, 04:35 UTC21h 44m
2026-07-14 VSV5381 - Jul 14, 05:05 UTCJul 15, 04:35 UTC23h 29m
2026-07-13 VSV5380 - Jul 13, 23:20 UTCJul 14, 02:15 UTC2h 55m
2026-07-12 VSV482 - Jul 12, 16:15 UTCJul 12, 17:55 UTC1h 40m
2026-07-12 VSV481 - Jul 12, 13:50 UTCJul 12, 15:05 UTC1h 15m
2026-07-11 VSV481 - Jul 11, 15:05 UTCJul 12, 14:45 UTC23h 40m
2026-07-11 VSV5381 - Jul 11, 06:35 UTCJul 11, 15:25 UTC8h 50m
2026-07-11 VSV5380 - Jul 11, 01:25 UTCJul 11, 04:15 UTC2h 50m
2026-07-09 VSV482 - Jul 9, 16:00 UTCJul 9, 17:30 UTC1h 30m
2026-07-09 VSV481 - Jul 9, 13:35 UTCJul 9, 14:45 UTC1h 10m
2026-07-08 VSV479 - Jul 8, 04:05 UTCJul 8, 20:10 UTC16h 5m
2026-07-07 VSV479 - Jul 7, 22:50 UTCJul 8, 20:10 UTC21h 20m
2026-07-07 VSV479 - Jul 7, 22:40 UTCJul 8, 20:10 UTC21h 30m
2026-07-07 VSV5382 - Jul 7, 18:10 UTCJul 8, 15:30 UTC21h 20m
2026-07-07 VSV5382 - Jul 7, 06:55 UTCJul 8, 04:20 UTC21h 25m
2026-07-07 VSV5381 - Jul 7, 05:05 UTCJul 8, 04:20 UTC23h 15m
2026-07-06 VSV5380 - Jul 6, 13:10 UTCJul 7, 02:15 UTC13h 5m
2026-07-06 VSV5282 - Jul 6, 02:15 UTCJul 6, 11:25 UTC9h 10m
2026-07-05 VSV5275 - Jul 5, 09:25 UTCJul 5, 23:50 UTC14h 25m
2026-07-04 VSV5268 - Jul 4, 18:25 UTCJul 5, 05:30 UTC11h 5m
2026-07-04 VSV5273 - Jul 4, 08:55 UTCJul 4, 11:30 UTC2h 35m
2026-07-02 VSV482 - Jul 2, 16:35 UTCJul 3, 05:35 UTC13h 0m
2026-07-01 VSV481 - Jul 1, 21:55 UTCJul 2, 15:20 UTC17h 25m
2026-07-01 VSV481 - Jul 1, 17:10 UTCJul 2, 15:20 UTC22h 10m
2026-07-01 VSV5276 - Jul 1, 09:20 UTCJul 2, 01:15 UTC15h 55m
2026-06-30 VSV5268 AYT → AYT Jun 30, 18:25 UTCJul 1, 05:20 UTC10h 55m
2026-06-30 VSV5273 - Jun 30, 09:30 UTCJun 30, 12:05 UTC2h 35m
2026-06-29 VSV476 SYX → NQZ Jun 29, 10:20 UTCJun 29, 10:40 UTC20m
2026-06-28 VSV482 - Jun 28, 16:19 UTCJun 28, 17:50 UTC1h 30m
2026-06-27 VSV475 - Jun 27, 18:04 UTCJun 27, 23:10 UTC5h 5m

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?
Yes. Mode-S 68332B is currently airborne.
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 20 distinct callsigns, including VSV481, VSV482, VSV5380, VSV5381, VSV5342.