Apparatus

Try JFK, AAL1290, BAW, or N225AN.

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 Jul 26, 20:40 UTC
Flights observed
142
Distinct callsigns
20
Country
KZ
Last broadcast
Jul 26, 20:40 UTC

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

Callsign Airline Flights Last seen
VSV485 - 32 2026-07-20
VSV486 Scat Air 18 2026-07-21
VSV467 Scat Air 16 2026-07-23
VSV468 Scat Air 14 2026-07-23
VSV469 - 11 2026-06-11
VSV843 Scat Air 10 2026-07-26
VSV844 Scat Air 9 2026-07-26
VSV470 Scat Air 9 2026-06-12
VSV723 - 4 2026-07-06
VSV490 Scat Air 4 2026-06-18
VSV489 Scat Air 3 2026-06-18
VSV826 Scat Air 2 2026-07-24
VSV724 - 2 2026-07-01
VSV832 - 1 2026-06-15
VSV824 Scat Air 1 2026-06-10
VSV823 Scat Air 1 2026-06-09
VSV799 Scat Air 1 2026-06-08
VSV5350 - 1 2026-05-22
VSV484 - 1 2026-07-14
VSV472 - 1 2026-07-07

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-26 VSV844 TBS → CIT Jul 26, 07:10 UTCJul 26, 20:40 UTC13h 30m
2026-07-26 VSV843 CIT → TBS Jul 26, 05:10 UTCJul 26, 05:30 UTC20m
2026-07-24 VSV826 LED → CIT Jul 24, 15:05 UTCJul 24, 15:25 UTC20m
2026-07-23 VSV468 ICN → CIT Jul 23, 22:15 UTCJul 23, 23:55 UTC1h 40m
2026-07-23 VSV467 CIT → ICN Jul 23, 19:00 UTCJul 23, 20:40 UTC1h 40m
2026-07-21 VSV486 IST → CIT Jul 21, 15:05 UTCJul 22, 04:50 UTC13h 45m
2026-07-20 VSV485 CIT → IST Jul 20, 19:20 UTCJul 21, 13:35 UTC18h 14m
2026-07-20 VSV485 CIT → IST Jul 20, 18:05 UTCJul 21, 13:35 UTC19h 30m
2026-07-20 VSV485 - Jul 20, 15:50 UTCJul 20, 16:10 UTC20m
2026-07-19 VSV485 - Jul 19, 23:45 UTCJul 20, 15:05 UTC15h 20m
2026-07-19 VSV468 ICN → CIT Jul 19, 22:35 UTCJul 19, 22:55 UTC20m
2026-07-19 VSV467 CIT → ICN Jul 19, 18:55 UTCJul 19, 20:35 UTC1h 40m
2026-07-16 VSV468 ICN → CIT Jul 16, 22:00 UTCJul 16, 23:35 UTC1h 35m
2026-07-16 VSV486 - Jul 16, 06:45 UTCJul 16, 20:35 UTC13h 50m
2026-07-16 VSV485 - Jul 16, 04:50 UTCJul 16, 05:15 UTC25m
2026-07-16 VSV485 - Jul 16, 02:40 UTCJul 16, 04:05 UTC1h 25m
2026-07-14 VSV484 - Jul 14, 15:50 UTCJul 14, 19:25 UTC3h 35m
2026-07-13 VSV468 ICN → MUC Jul 13, 22:30 UTCJul 14, 14:30 UTC16h 0m
2026-07-13 VSV467 - Jul 13, 20:45 UTCJul 13, 21:10 UTC25m
2026-07-13 VSV467 - Jul 13, 19:30 UTCJul 13, 19:55 UTC25m
2026-07-12 VSV844 - Jul 12, 07:05 UTCJul 12, 07:35 UTC30m
2026-07-12 VSV843 - Jul 12, 05:10 UTCJul 12, 05:40 UTC30m
2026-07-09 VSV468 - Jul 9, 23:25 UTCJul 10, 05:00 UTC5h 35m
2026-07-09 VSV467 - Jul 9, 20:40 UTCJul 9, 21:05 UTC25m
2026-07-09 VSV844 - Jul 9, 07:15 UTCJul 9, 19:30 UTC12h 15m
2026-07-09 VSV843 - Jul 9, 05:30 UTCJul 9, 06:00 UTC30m
2026-07-08 VSV843 - Jul 8, 07:50 UTCJul 9, 06:00 UTC22h 10m
2026-07-07 VSV472 - Jul 7, 21:55 UTCJul 8, 07:55 UTC10h 0m
2026-07-06 VSV723 - Jul 6, 19:25 UTCJul 7, 02:00 UTC6h 35m
2026-07-05 VSV486 - Jul 5, 09:10 UTCJul 5, 11:05 UTC1h 55m
2026-07-05 VSV485 - Jul 5, 04:55 UTCJul 5, 07:30 UTC2h 35m
2026-07-02 VSV468 - Jul 2, 22:15 UTCJul 3, 04:00 UTC5h 45m
2026-07-02 VSV467 - Jul 2, 20:25 UTCJul 2, 20:45 UTC20m
2026-07-02 VSV486 - Jul 2, 06:51 UTCJul 2, 19:40 UTC12h 49m
2026-07-02 VSV485 - Jul 2, 04:55 UTCJul 2, 05:15 UTC20m
2026-07-02 VSV485 - Jul 2, 02:50 UTCJul 2, 04:15 UTC1h 25m
2026-07-01 VSV724 - Jul 1, 03:55 UTCJul 2, 03:15 UTC23h 20m
2026-06-30 VSV486 - Jun 30, 16:25 UTCJul 1, 02:05 UTC9h 40m
2026-06-30 VSV485 - Jun 30, 03:40 UTCJun 30, 14:30 UTC10h 50m
2026-06-30 VSV723 - Jun 30, 01:40 UTCJun 30, 02:05 UTC25m
2026-06-28 VSV486 - Jun 28, 09:20 UTCJun 28, 11:25 UTC2h 5m
2026-06-28 VSV485 - Jun 28, 04:55 UTCJun 28, 07:20 UTC2h 25m
2026-06-26 VSV486 - Jun 26, 21:04 UTCJun 26, 23:00 UTC1h 55m
2026-06-26 VSV485 - Jun 26, 16:54 UTCJun 26, 19:30 UTC2h 35m
2026-06-25 VSV844 - Jun 25, 07:05 UTCJun 25, 07:34 UTC30m
2026-06-25 VSV843 - Jun 25, 05:15 UTCJun 25, 05:50 UTC35m
2026-06-23 VSV486 - Jun 23, 19:04 UTCJun 23, 20:59 UTC1h 55m
2026-06-22 VSV485 - Jun 22, 23:24 UTCJun 23, 17:25 UTC18h 0m
2026-06-22 VSV485 - Jun 22, 22:10 UTCJun 23, 17:25 UTC19h 15m
2026-06-22 VSV467 - Jun 22, 20:04 UTCJun 22, 20:24 UTC20m

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 Jul 26, 20:40 UTC.
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 20 distinct callsigns, including VSV485, VSV486, VSV467, VSV468, VSV469.