sensors Mode-S transponder

6832B5

ICAO 24-bit transponder address · allocated to Kazakhstan

Currently assigned to UP-B3746 · BOEING 737 MAX 8

Hex
6832B5
Octal
32031265
Decimal
6,828,725
Country
KZ
Tail
UP-B3746
Type
B38M
No current signal · last broadcast 1d ago
Flights observed
52
Distinct callsigns
11
Country
KZ
Last broadcast
1d ago

Last known position

Most recent position reported by Mode-S 6832B5.

Country allocation

The ICAO 24-bit address 6832B5 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 11 distinct

Callsign Airline Flights Last seen
VSV469 Scat Air 10 2026-05-28
VSV485 Scat Air 7 2026-05-19
VSV470 Scat Air 7 2026-05-28
VSV467 Scat Air 6 2026-05-24
VSV468 Scat Air 5 2026-05-25
VSV844 Scat Air 4 2026-05-24
VSV843 Scat Air 4 2026-05-28
VSV490 Scat Air 3 2026-05-26
VSV486 Scat Air 3 2026-05-19
VSV489 Scat Air 2 2026-05-26
VSV5350 - 1 2026-05-22

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-05-28 VSV470 BKK → CIT May 28, 22:45 UTCMay 29, 03:15 UTC4h 30m
2026-05-28 VSV469 CIT → BKK May 28, 07:10 UTCMay 28, 21:20 UTC14h 10m
2026-05-28 VSV843 CIT → TBS May 28, 05:30 UTCMay 28, 05:50 UTC20m
2026-05-26 VSV490 BUD → CIT May 26, 16:05 UTCMay 26, 19:25 UTC3h 20m
2026-05-26 VSV489 CIT → BUD May 26, 13:00 UTCMay 26, 14:00 UTC1h 0m
2026-05-25 VSV468 ICN → CIT May 25, 03:05 UTCMay 25, 03:35 UTC30m
2026-05-24 VSV467 CIT → ICN May 24, 20:05 UTCMay 24, 20:25 UTC20m
2026-05-24 VSV844 TBS → CIT May 24, 07:00 UTCMay 24, 07:30 UTC30m
2026-05-24 VSV843 CIT → TBS May 24, 04:50 UTCMay 24, 05:25 UTC35m
2026-05-22 VSV5350 - May 22, 20:55 UTCMay 23, 02:20 UTC5h 25m
2026-05-22 VSV468 ICN → CIT May 22, 03:30 UTCMay 23, 02:20 UTC22h 50m
2026-05-21 VSV468 ICN → CIT May 21, 23:35 UTCMay 22, 21:15 UTC21h 40m
2026-05-21 VSV468 ICN → CIT May 21, 22:15 UTCMay 22, 21:15 UTC23h 0m
2026-05-21 VSV467 CIT → ICN May 21, 20:05 UTCMay 21, 20:30 UTC25m
2026-05-21 VSV490 BUD → CIT May 21, 07:30 UTCMay 21, 19:15 UTC11h 45m
2026-05-21 VSV489 CIT → BUD May 21, 05:30 UTCMay 21, 06:15 UTC45m
2026-05-19 VSV486 IST → CIT May 19, 15:45 UTCMay 19, 17:45 UTC2h 0m
2026-05-19 VSV485 CIT → IST May 19, 13:40 UTCMay 19, 13:55 UTC15m
2026-05-19 VSV485 CIT → IST May 19, 11:30 UTCMay 19, 12:45 UTC1h 15m
2026-05-17 VSV468 ICN → CIT May 17, 22:01 UTCMay 17, 23:35 UTC1h 35m
2026-05-17 VSV467 CIT → ICN May 17, 18:40 UTCMay 17, 20:20 UTC1h 40m
2026-05-15 VSV844 TBS → CIT May 15, 12:15 UTCMay 15, 12:40 UTC25m
2026-05-14 VSV470 BKK → CIT May 14, 22:50 UTCMay 15, 10:25 UTC11h 35m
2026-05-14 VSV469 CIT → BKK May 14, 17:10 UTCMay 14, 21:10 UTC4h 0m
2026-05-11 VSV467 CIT → ICN May 11, 20:45 UTCMay 11, 20:55 UTC10m
2026-05-08 VSV844 TBS → CIT May 8, 12:04 UTCMay 8, 12:30 UTC25m
2026-05-07 VSV470 BKK → CIT May 7, 22:50 UTCMay 8, 10:25 UTC11h 35m
2026-05-07 VSV469 CIT → BKK May 7, 17:25 UTCMay 7, 21:15 UTC3h 50m
2026-05-04 VSV470 BKK → CIT May 4, 23:05 UTCMay 5, 03:25 UTC4h 20m
2026-05-04 VSV469 CIT → BKK May 4, 17:20 UTCMay 4, 21:30 UTC4h 11m
2026-04-29 VSV485 CIT → IST Apr 29, 03:30 UTCApr 29, 11:45 UTC8h 16m
2026-04-28 VSV485 CIT → IST Apr 28, 15:55 UTCApr 29, 11:45 UTC19h 51m
2026-04-28 VSV490 BUD → CIT Apr 28, 13:50 UTCApr 29, 11:45 UTC21h 55m
2026-04-27 VSV470 BKK → CIT Apr 27, 22:50 UTCApr 28, 12:35 UTC13h 45m
2026-04-27 VSV469 CIT → BKK Apr 27, 17:25 UTCApr 27, 21:15 UTC3h 50m
2026-04-26 VSV469 CIT → BKK Apr 26, 23:30 UTCApr 27, 21:15 UTC21h 45m
2026-04-26 VSV469 CIT → BKK Apr 26, 22:00 UTCApr 27, 21:15 UTC23h 15m
2026-04-26 VSV467 CIT → ICN Apr 26, 19:45 UTCApr 26, 20:00 UTC15m
2026-04-26 VSV467 CIT → ICN Apr 26, 18:35 UTCApr 26, 18:50 UTC15m
2026-04-23 VSV470 BKK → CIT Apr 23, 22:55 UTCApr 24, 03:15 UTC4h 20m
2026-04-23 VSV469 CIT → BKK Apr 23, 17:20 UTCApr 23, 21:20 UTC3h 59m
2026-04-20 VSV485 CIT → IST Apr 20, 16:50 UTCApr 20, 22:55 UTC6h 5m
2026-04-17 VSV486 IST → CIT Apr 17, 21:40 UTCApr 17, 22:45 UTC1h 5m
2026-04-17 VSV486 IST → CIT Apr 17, 20:45 UTCApr 17, 20:55 UTC10m
2026-04-17 VSV485 CIT → IST Apr 17, 17:25 UTCApr 17, 17:55 UTC30m
2026-04-17 VSV485 CIT → IST Apr 17, 16:15 UTCApr 17, 17:15 UTC1h 0m
2026-04-13 VSV470 - Apr 13, 22:50 UTCApr 13, 23:10 UTC20m
2026-04-13 VSV469 CIT → BKK Apr 13, 20:35 UTCApr 13, 21:00 UTC25m
2026-04-13 VSV469 CIT → BKK Apr 13, 17:15 UTCApr 13, 19:40 UTC2h 25m
2026-04-13 VSV844 - Apr 13, 10:10 UTCApr 13, 10:40 UTC30m

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

Mode-S 6832B5 frequently asked

What is Mode-S code 6832B5?
6832B5 is an ICAO 24-bit transponder address. Allocated to Kazakhstan. Assigned to UP-B3746.
Where is Mode-S 6832B5 registered?
Mode-S code 6832B5 is allocated to Kazakhstan (KZ). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 6832B5 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 6832B5, octal 32031265, decimal 6,828,725.
What flights does 6832B5 operate?
Mode-S 6832B5 has broadcast 11 distinct callsigns, including VSV469, VSV485, VSV470, VSV467, VSV468.