Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

6832B2

ICAO 24-bit transponder address · allocated to Kazakhstan

Currently assigned to UP-B3743 · BOEING 737 MAX 8

Hex
6832B2
Octal
32031262
Decimal
6,828,722
Country
KZ
Tail
UP-B3743
Type
B38M
No current signal · last broadcast Jul 26, 20:55 UTC
Flights observed
133
Distinct callsigns
20
Country
KZ
Last broadcast
Jul 26, 20:55 UTC

Last known position

Most recent position reported by Mode-S 6832B2.

Country allocation

The ICAO 24-bit address 6832B2 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
VSV5350 - 23 2026-07-25
VSV5342 - 19 2026-07-26
VSV486 - 16 2026-07-17
VSV485 - 15 2026-07-14
VSV843 - 14 2026-07-04
VSV844 - 7 2026-07-05
VSV468 - 7 2026-07-06
VSV470 - 6 2026-06-18
VSV469 - 5 2026-06-18
VSV467 - 5 2026-07-06
VSV490 - 4 2026-07-16
VSV724 Scat Air 2 2026-06-10
VSV489 Scat Air 2 2026-06-16
VSV826 Scat Air 1 2026-06-08
VSV821 Scat Air 1 2026-04-13
VSV723 Scat Air 1 2026-06-07
VSV5351 - 1 2026-06-28
VSV484 Scat Air 1 2026-06-23
VSV483 Scat Air 1 2026-06-23
VSV460 Scat Air 1 2026-07-19

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-26 VSV5342 - Jul 26, 00:45 UTCJul 26, 20:55 UTC20h 11m
2026-07-25 VSV5350 - Jul 25, 20:00 UTCJul 26, 01:00 UTC5h 0m
2026-07-24 VSV5350 - Jul 24, 20:35 UTCJul 25, 20:20 UTC23h 45m
2026-07-24 VSV5350 - Jul 24, 20:25 UTCJul 24, 20:45 UTC20m
2026-07-24 VSV5342 - Jul 24, 01:05 UTCJul 24, 20:45 UTC19h 40m
2026-07-23 VSV5342 - Jul 23, 20:35 UTCJul 24, 20:30 UTC23h 55m
2026-07-23 VSV5342 - Jul 23, 07:10 UTCJul 24, 01:25 UTC18h 15m
2026-07-23 VSV5342 - Jul 23, 01:10 UTCJul 23, 20:45 UTC19h 35m
2026-07-22 VSV5350 - Jul 22, 20:35 UTCJul 23, 20:30 UTC23h 55m
2026-07-19 VSV5342 - Jul 19, 21:15 UTCJul 20, 06:25 UTC9h 10m
2026-07-19 VSV5342 - Jul 19, 05:45 UTCJul 20, 01:55 UTC20h 10m
2026-07-19 VSV460 JED → ALA Jul 19, 02:45 UTCJul 20, 01:55 UTC23h 10m
2026-07-18 VSV459 ALA → JED Jul 18, 19:15 UTCJul 18, 21:35 UTC2h 20m
2026-07-17 VSV486 - Jul 17, 20:35 UTCJul 18, 19:15 UTC22h 41m
2026-07-17 VSV486 - Jul 17, 20:25 UTCJul 17, 22:20 UTC1h 55m
2026-07-16 VSV490 - Jul 16, 07:15 UTCJul 16, 19:35 UTC12h 20m
2026-07-15 VSV486 - Jul 15, 07:40 UTCJul 15, 09:40 UTC2h 0m
2026-07-14 VSV485 - Jul 14, 16:20 UTCJul 15, 05:55 UTC13h 34m
2026-07-14 VSV485 - Jul 14, 14:00 UTCJul 14, 14:15 UTC15m
2026-07-14 VSV485 - Jul 14, 11:50 UTCJul 14, 12:30 UTC40m
2026-07-12 VSV5342 - Jul 12, 20:35 UTCJul 13, 06:20 UTC9h 45m
2026-07-12 VSV5342 - Jul 12, 07:05 UTCJul 13, 06:20 UTC23h 15m
2026-07-12 VSV5350 - Jul 12, 00:50 UTCJul 12, 20:55 UTC20h 5m
2026-07-11 VSV5350 - Jul 11, 20:15 UTCJul 12, 07:15 UTC11h 0m
2026-07-11 VSV5350 - Jul 11, 03:20 UTCJul 12, 01:10 UTC21h 50m
2026-07-10 VSV5350 - Jul 10, 22:40 UTCJul 11, 20:40 UTC22h 0m
2026-07-10 VSV5350 - Jul 10, 06:45 UTCJul 11, 03:35 UTC20h 50m
2026-07-10 VSV5350 - Jul 10, 01:10 UTCJul 10, 23:00 UTC21h 50m
2026-07-09 VSV5342 - Jul 9, 20:30 UTCJul 10, 06:55 UTC10h 25m
2026-07-09 VSV5342 - Jul 9, 07:15 UTCJul 10, 01:25 UTC18h 10m
2026-07-09 VSV5342 - Jul 9, 01:05 UTCJul 9, 20:55 UTC19h 50m
2026-07-08 VSV5350 - Jul 8, 20:35 UTCJul 9, 20:30 UTC23h 55m
2026-07-08 VSV486 - Jul 8, 08:50 UTCJul 9, 07:30 UTC22h 40m
2026-07-08 VSV486 - Jul 8, 07:55 UTCJul 9, 01:15 UTC17h 20m
2026-07-08 VSV485 - Jul 8, 05:55 UTCJul 8, 06:05 UTC10m
2026-07-08 VSV485 - Jul 8, 03:35 UTCJul 8, 04:25 UTC50m
2026-07-06 VSV468 - Jul 6, 22:40 UTCJul 7, 04:20 UTC5h 40m
2026-07-06 VSV467 - Jul 6, 20:40 UTCJul 6, 21:00 UTC20m
2026-07-06 VSV468 - Jul 6, 03:00 UTCJul 6, 19:50 UTC16h 50m
2026-07-05 VSV468 - Jul 5, 23:20 UTCJul 6, 19:50 UTC20h 30m
2026-07-05 VSV468 - Jul 5, 22:00 UTCJul 6, 19:50 UTC21h 50m
2026-07-05 VSV467 - Jul 5, 20:05 UTCJul 5, 20:35 UTC30m
2026-07-05 VSV844 - Jul 5, 07:05 UTCJul 5, 19:20 UTC12h 15m
2026-07-04 VSV843 - Jul 4, 12:05 UTCJul 5, 05:30 UTC17h 25m
2026-07-04 VSV843 - Jul 4, 09:20 UTCJul 5, 05:30 UTC20h 10m
2026-07-02 VSV5342 - Jul 2, 20:45 UTCJul 3, 06:35 UTC9h 50m
2026-07-02 VSV5342 - Jul 2, 06:51 UTCJul 3, 06:30 UTC23h 39m
2026-07-02 VSV5350 - Jul 2, 01:05 UTCJul 2, 20:55 UTC19h 50m
2026-07-01 VSV5350 - Jul 1, 20:20 UTCJul 2, 07:40 UTC11h 20m
2026-06-28 VSV5342 - Jun 28, 20:45 UTCJun 29, 06:44 UTC10h 0m

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

Mode-S 6832B2 frequently asked

What is Mode-S code 6832B2?
6832B2 is an ICAO 24-bit transponder address. Allocated to Kazakhstan. Assigned to UP-B3743.
Where is Mode-S 6832B2 registered?
Mode-S code 6832B2 is allocated to Kazakhstan (KZ). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 6832B2 broadcasting right now?
No active broadcast right now. Last signal was Jul 26, 20:55 UTC.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 6832B2, octal 32031262, decimal 6,828,722.
What flights does 6832B2 operate?
Mode-S 6832B2 has broadcast 20 distinct callsigns, including VSV5350, VSV5342, VSV486, VSV485, VSV843.