sensors Mode-S transponder

68332A

ICAO 24-bit transponder address · allocated to Kazakhstan

Currently assigned to UP-B3738 · BOEING 737 MAX 9

Hex
68332A
Octal
32031452
Decimal
6,828,842
Country
KZ
Tail
UP-B3738
Type
B39M
No current signal · last broadcast 14h ago
Flights observed
115
Distinct callsigns
20
Country
KZ
Last broadcast
14h ago

Last known position

Most recent position reported by Mode-S 68332A.

Country allocation

The ICAO 24-bit address 68332A 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
VSV5240 - 12 2026-05-07
VSV5273 - 10 2026-05-25
VSV5266 - 8 2026-05-09
VSV5274 - 7 2026-05-24
VSV5212 Scat Air 7 2026-05-13
VSV5275 - 6 2026-05-24
VSV5241 - 6 2026-05-07
VSV5291 Scat Air 5 2026-05-04
VSV5276 - 5 2026-05-27
VSV5265 - 5 2026-05-08
VSV5282 - 4 2026-05-25
VSV828 Scat Air 3 2026-04-16
VSV5268 - 3 2026-05-26
VSV5263 - 3 2026-05-06
VSV5213 Scat Air 3 2026-05-14
VSV5201 - 3 2026-04-15
VSV5200 Scat Air 3 2026-05-09
VSV827 Scat Air 2 2026-04-16
VSV5292 - 2 2026-05-10
VSV5281 Scat Air 2 2026-05-25

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-05-28 VSV482 PRG → FRU May 28, 17:55 UTCMay 29, 11:00 UTC17h 5m
2026-05-28 VSV481 FRU → PRG May 28, 00:50 UTCMay 28, 16:45 UTC15h 55m
2026-05-27 VSV481 FRU → PRG May 27, 19:40 UTCMay 28, 16:45 UTC21h 5m
2026-05-27 VSV5276 - May 27, 09:35 UTCMay 28, 03:45 UTC18h 10m
2026-05-26 VSV5268 - May 26, 19:20 UTCMay 27, 05:40 UTC10h 20m
2026-05-26 VSV5267 AYT → KGF May 26, 18:24 UTCMay 26, 18:34 UTC10m
2026-05-25 VSV5273 - May 25, 14:35 UTCMay 26, 09:40 UTC19h 4m
2026-05-25 VSV5273 - May 25, 13:25 UTCMay 26, 09:40 UTC20h 14m
2026-05-25 VSV5282 - May 25, 10:40 UTCMay 25, 10:55 UTC15m
2026-05-25 VSV5282 - May 25, 03:00 UTCMay 25, 10:00 UTC7h 0m
2026-05-25 VSV5281 AYT → AKX May 25, 02:05 UTCMay 25, 02:20 UTC15m
2026-05-24 VSV5275 - May 24, 23:35 UTCMay 24, 23:46 UTC11m
2026-05-24 VSV5274 - May 24, 09:15 UTCMay 24, 11:20 UTC2h 5m
2026-05-24 VSV5268 - May 24, 05:15 UTCMay 24, 05:35 UTC20m
2026-05-23 VSV5268 - May 23, 18:15 UTCMay 24, 04:30 UTC10h 15m
2026-05-23 VSV5273 - May 23, 09:25 UTCMay 23, 09:45 UTC20m
2026-05-22 VSV5273 - May 22, 14:35 UTCMay 23, 08:45 UTC18h 10m
2026-05-22 VSV5276 - May 22, 12:40 UTCMay 23, 08:45 UTC20h 4m
2026-05-22 VSV5281 AYT → AKX May 22, 01:20 UTCMay 22, 09:40 UTC8h 20m
2026-05-21 VSV5275 - May 21, 22:55 UTCMay 21, 23:15 UTC20m
2026-05-21 VSV5274 - May 21, 11:25 UTCMay 21, 22:15 UTC10h 50m
2026-05-21 VSV5273 - May 21, 09:00 UTCMay 21, 09:15 UTC15m
2026-05-20 VSV5370 - May 20, 16:50 UTCMay 21, 08:15 UTC15h 25m
2026-05-20 VSV5288 - May 20, 03:40 UTCMay 20, 12:55 UTC9h 16m
2026-05-20 VSV5369 - May 20, 00:20 UTCMay 20, 00:40 UTC20m
2026-05-19 VSV5274 - May 19, 13:30 UTCMay 19, 23:35 UTC10h 5m
2026-05-19 VSV5273 - May 19, 09:35 UTCMay 19, 09:55 UTC20m
2026-05-18 VSV5273 - May 18, 14:40 UTCMay 19, 08:50 UTC18h 9m
2026-05-18 VSV5276 - May 18, 13:35 UTCMay 19, 08:50 UTC19h 14m
2026-05-18 VSV5282 - May 18, 12:00 UTCMay 18, 12:20 UTC20m
2026-05-18 VSV5282 - May 18, 03:10 UTCMay 18, 11:10 UTC8h 0m
2026-05-18 VSV5275 - May 18, 01:15 UTCMay 18, 01:35 UTC20m
2026-05-17 VSV5275 - May 17, 09:35 UTCMay 18, 00:30 UTC14h 55m
2026-05-17 VSV5273 - May 17, 07:45 UTCMay 17, 08:00 UTC15m
2026-05-16 VSV5274 - May 16, 12:40 UTCMay 17, 06:45 UTC18h 5m
2026-05-16 VSV5219 - May 16, 10:31 UTCMay 16, 11:01 UTC30m
2026-05-16 VSV5219 - May 16, 08:36 UTCMay 16, 09:40 UTC1h 5m
2026-05-14 VSV5213 GOI → ALA May 14, 09:35 UTCMay 14, 11:20 UTC1h 45m
2026-05-13 VSV5273 - May 13, 13:31 UTCMay 14, 06:45 UTC17h 15m
2026-05-13 VSV5274 - May 13, 12:20 UTCMay 13, 12:35 UTC15m
2026-05-13 VSV5212 ALA → GOI May 13, 08:05 UTCMay 13, 08:45 UTC40m
2026-05-10 VSV5292 - May 10, 14:25 UTCMay 10, 16:59 UTC2h 35m
2026-05-09 VSV5200 SSH → SSH May 9, 21:05 UTCMay 10, 07:50 UTC10h 45m
2026-05-09 VSV5266 - May 9, 03:00 UTCMay 9, 05:45 UTC2h 45m
2026-05-08 VSV5265 - May 8, 18:00 UTCMay 8, 20:40 UTC2h 40m
2026-05-07 VSV5240 - May 7, 18:25 UTCMay 8, 08:49 UTC14h 24m
2026-05-07 VSV5240 - May 7, 12:35 UTCMay 8, 08:49 UTC20h 14m
2026-05-07 VSV5240 - May 7, 10:35 UTCMay 8, 08:49 UTC22h 15m
2026-05-07 VSV5241 - May 7, 04:45 UTCMay 7, 23:29 UTC18h 45m
2026-05-07 VSV5241 - May 7, 03:05 UTCMay 7, 23:29 UTC20h 25m

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

Mode-S 68332A frequently asked

What is Mode-S code 68332A?
68332A is an ICAO 24-bit transponder address. Allocated to Kazakhstan. Assigned to UP-B3738.
Where is Mode-S 68332A registered?
Mode-S code 68332A is allocated to Kazakhstan (KZ). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 68332A broadcasting right now?
No active broadcast right now. Last signal was 14h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 68332A, octal 32031452, decimal 6,828,842.
What flights does 68332A operate?
Mode-S 68332A has broadcast 20 distinct callsigns, including VSV5240, VSV5273, VSV5266, VSV5274, VSV5212.