Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

6832B3

ICAO 24-bit transponder address · allocated to Kazakhstan

Currently assigned to UP-B3744 · BOEING 737 MAX 8

Hex
6832B3
Octal
32031263
Decimal
6,828,723
Country
KZ
Tail
UP-B3744
Type
B38M
No current signal · last broadcast 8h ago
Flights observed
115
Distinct callsigns
20
Country
KZ
Last broadcast
8h ago

Last known position

Most recent position reported by Mode-S 6832B3.

Country allocation

The ICAO 24-bit address 6832B3 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
VSV467 - 19 2026-07-10
VSV468 - 15 2026-07-10
VSV485 - 14 2026-07-03
VSV486 - 12 2026-07-12
VSV490 - 9 2026-07-11
VSV844 - 8 2026-06-26
VSV469 - 8 2026-07-13
VSV470 - 6 2026-07-13
VSV843 Scat Air 5 2026-06-12
VSV489 - 5 2026-07-02
VSV723 Scat Air 2 2026-05-30
VSV5375 - 2 2026-06-17
VSV5350 - 2 2026-06-19
VSV483 - 2 2026-07-09
VSV826 Scat Air 1 2026-06-01
VSV726 Scat Air 1 2026-06-03
VSV5348 - 1 2026-05-15
VSV5332 - 1 2026-06-30
VSV5317 - 1 2026-05-14
VSV3459 Scat Air 1 2026-05-21

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-13 VSV470 - Jul 13, 23:30 UTCJul 14, 03:30 UTC4h 0m
2026-07-13 VSV469 - Jul 13, 17:45 UTCJul 13, 21:55 UTC4h 10m
2026-07-12 VSV486 - Jul 12, 09:15 UTCJul 12, 11:10 UTC1h 55m
2026-07-11 VSV490 - Jul 11, 14:15 UTCJul 12, 07:20 UTC17h 5m
2026-07-10 VSV468 ICN → BUD Jul 10, 21:30 UTCJul 11, 12:50 UTC15h 20m
2026-07-10 VSV467 - Jul 10, 19:25 UTCJul 10, 19:45 UTC20m
2026-07-09 VSV470 - Jul 9, 23:15 UTCJul 10, 18:40 UTC19h 25m
2026-07-09 VSV469 MUC → BKK Jul 9, 06:50 UTCJul 9, 21:35 UTC14h 45m
2026-07-09 VSV483 - Jul 9, 04:35 UTCJul 9, 05:20 UTC45m
2026-07-07 VSV490 - Jul 7, 15:55 UTCJul 7, 18:50 UTC2h 55m
2026-07-06 VSV470 - Jul 6, 23:30 UTCJul 7, 14:30 UTC15h 0m
2026-07-06 VSV469 - Jul 6, 17:50 UTCJul 6, 22:05 UTC4h 15m
2026-07-03 VSV486 - Jul 3, 20:20 UTCJul 3, 22:15 UTC1h 55m
2026-07-03 VSV485 - Jul 3, 15:50 UTCJul 3, 18:15 UTC2h 25m
2026-07-02 VSV485 - Jul 2, 19:05 UTCJul 3, 18:15 UTC23h 10m
2026-07-02 VSV490 - Jul 2, 07:40 UTCJul 2, 19:30 UTC11h 50m
2026-07-02 VSV489 - Jul 2, 05:45 UTCJul 2, 06:20 UTC35m
2026-06-30 VSV5332 - Jun 30, 00:30 UTCJun 30, 09:55 UTC9h 26m
2026-06-26 VSV844 - Jun 26, 12:10 UTCJun 26, 12:34 UTC25m
2026-06-25 VSV470 - Jun 25, 23:59 UTCJun 26, 10:50 UTC10h 50m
2026-06-25 VSV469 - Jun 25, 07:05 UTCJun 25, 22:39 UTC15h 35m
2026-06-25 VSV483 CIT → MUC Jun 25, 05:05 UTCJun 25, 05:55 UTC50m
2026-06-24 VSV486 - Jun 24, 08:49 UTCJun 25, 05:55 UTC21h 5m
2026-06-24 VSV486 - Jun 24, 07:50 UTCJun 25, 05:55 UTC22h 5m
2026-06-24 VSV485 - Jun 24, 03:50 UTCJun 24, 06:15 UTC2h 25m
2026-06-22 VSV470 - Jun 22, 22:59 UTCJun 23, 03:15 UTC4h 15m
2026-06-22 VSV469 - Jun 22, 17:29 UTCJun 22, 21:35 UTC4h 5m
2026-06-19 VSV5350 - Jun 19, 20:29 UTCJun 20, 06:49 UTC10h 20m
2026-06-17 VSV5375 - Jun 17, 01:30 UTCJun 17, 11:10 UTC9h 40m
2026-06-15 VSV486 - Jun 15, 17:59 UTCJun 15, 19:55 UTC1h 55m
2026-06-15 VSV485 - Jun 15, 04:55 UTCJun 15, 16:04 UTC11h 10m
2026-06-14 VSV468 ICN → CIT Jun 14, 23:50 UTCJun 15, 00:05 UTC15m
2026-06-14 VSV467 - Jun 14, 22:05 UTCJun 14, 22:25 UTC20m
2026-06-12 VSV844 TBS → CIT Jun 12, 12:50 UTCJun 12, 13:15 UTC25m
2026-06-12 VSV843 CIT → TBS Jun 12, 10:15 UTCJun 12, 11:30 UTC1h 15m
2026-06-08 VSV468 ICN → CIT Jun 8, 22:35 UTCJun 9, 04:15 UTC5h 40m
2026-06-08 VSV467 CIT → ICN Jun 8, 20:55 UTCJun 8, 21:20 UTC25m
2026-06-08 VSV844 TBS → CIT Jun 8, 10:25 UTCJun 8, 20:10 UTC9h 45m
2026-06-08 VSV843 CIT → TBS Jun 8, 07:40 UTCJun 8, 08:10 UTC30m
2026-06-07 VSV843 CIT → TBS Jun 7, 10:50 UTCJun 8, 08:10 UTC21h 20m
2026-06-07 VSV486 IST → CIT Jun 7, 09:05 UTCJun 8, 08:10 UTC23h 5m
2026-06-07 VSV485 CIT → IST Jun 7, 06:30 UTCJun 7, 06:55 UTC25m
2026-06-07 VSV485 CIT → IST Jun 7, 04:35 UTCJun 7, 05:55 UTC1h 20m
2026-06-05 VSV844 TBS → CIT Jun 5, 12:05 UTCJun 5, 21:35 UTC9h 30m
2026-06-04 VSV468 ICN → CIT Jun 4, 21:55 UTCJun 5, 10:15 UTC12h 20m
2026-06-04 VSV467 CIT → ICN Jun 4, 20:00 UTCJun 4, 20:20 UTC20m
2026-06-04 VSV490 BUD → CIT Jun 4, 07:25 UTCJun 4, 19:10 UTC11h 45m
2026-06-03 VSV726 UKK → ALA Jun 3, 17:15 UTCJun 3, 17:40 UTC25m
2026-06-03 VSV5375 - Jun 3, 01:20 UTCJun 3, 15:55 UTC14h 35m
2026-06-02 VSV468 ICN → CIT Jun 2, 03:25 UTCJun 3, 02:45 UTC23h 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-B3744 page for operator, model, and routing details .

Mode-S 6832B3 frequently asked

What is Mode-S code 6832B3?
6832B3 is an ICAO 24-bit transponder address. Allocated to Kazakhstan. Assigned to UP-B3744.
Where is Mode-S 6832B3 registered?
Mode-S code 6832B3 is allocated to Kazakhstan (KZ). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 6832B3 broadcasting right now?
No active broadcast right now. Last signal was 8h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 6832B3, octal 32031263, decimal 6,828,723.
What flights does 6832B3 operate?
Mode-S 6832B3 has broadcast 20 distinct callsigns, including VSV467, VSV468, VSV485, VSV486, VSV490.