Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

6832B4

ICAO 24-bit transponder address · allocated to Kazakhstan

Currently assigned to UP-B3745 · BOEING 737 MAX 8

Hex
6832B4
Octal
32031264
Decimal
6,828,724
Country
KZ
Tail
UP-B3745
Type
B38M
No current signal · last broadcast 13h ago
Flights observed
100
Distinct callsigns
20
Country
KZ
Last broadcast
13h ago

Last known position

Most recent position reported by Mode-S 6832B4.

Country allocation

The ICAO 24-bit address 6832B4 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 - 12 2026-07-12
VSV486 - 8 2026-07-13
VSV469 - 8 2026-07-16
VSV468 - 8 2026-07-12
VSV467 - 8 2026-07-12
VSV470 - 7 2026-07-16
VSV844 - 6 2026-07-17
VSV489 - 6 2026-06-25
VSV843 - 5 2026-07-02
VSV723 - 5 2026-06-22
VSV490 - 5 2026-06-25
VSV5350 - 4 2026-07-04
VSV803 Scat Air 2 2026-05-09
VSV724 - 2 2026-06-23
VSV5342 - 2 2026-07-05
VSV484 - 2 2026-07-07
VSV483 - 2 2026-07-16
VSV842 Scat Air 1 2026-06-06
VSV841 Scat Air 1 2026-06-06
VSV828 Scat Air 1 2026-05-21

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-17 VSV844 - Jul 17, 12:25 UTCJul 17, 12:55 UTC30m
2026-07-16 VSV470 - Jul 16, 23:20 UTCJul 17, 11:00 UTC11h 40m
2026-07-16 VSV469 - Jul 16, 07:05 UTCJul 16, 21:50 UTC14h 45m
2026-07-16 VSV483 - Jul 16, 04:10 UTCJul 16, 05:50 UTC1h 40m
2026-07-13 VSV486 - Jul 13, 18:05 UTCJul 13, 20:05 UTC2h 0m
2026-07-12 VSV485 - Jul 12, 23:20 UTCJul 13, 16:20 UTC17h 0m
2026-07-12 VSV468 - Jul 12, 22:05 UTCJul 12, 22:25 UTC20m
2026-07-12 VSV467 - Jul 12, 20:10 UTCJul 12, 20:35 UTC25m
2026-07-12 VSV467 - Jul 12, 18:55 UTCJul 12, 19:25 UTC30m
2026-07-10 VSV486 - Jul 10, 21:20 UTCJul 10, 23:10 UTC1h 50m
2026-07-10 VSV485 - Jul 10, 17:15 UTCJul 10, 19:45 UTC2h 30m
2026-07-07 VSV484 - Jul 7, 16:15 UTCJul 7, 18:10 UTC1h 55m
2026-07-05 VSV5342 - Jul 5, 20:20 UTCJul 6, 01:05 UTC4h 45m
2026-07-05 VSV5342 - Jul 5, 01:05 UTCJul 6, 01:00 UTC23h 55m
2026-07-04 VSV5350 - Jul 4, 07:10 UTCJul 5, 01:40 UTC18h 30m
2026-07-04 VSV5350 - Jul 4, 06:30 UTCJul 5, 01:40 UTC19h 10m
2026-07-04 VSV5350 - Jul 4, 01:30 UTCJul 5, 01:00 UTC23h 30m
2026-07-03 VSV5350 - Jul 3, 20:45 UTCJul 4, 07:20 UTC10h 35m
2026-07-02 VSV844 - Jul 2, 07:20 UTCJul 2, 07:50 UTC30m
2026-07-02 VSV843 - Jul 2, 05:35 UTCJul 2, 06:15 UTC40m
2026-07-01 VSV486 - Jul 1, 09:05 UTCJul 2, 06:15 UTC21h 10m
2026-07-01 VSV486 - Jul 1, 07:55 UTCJul 2, 06:15 UTC22h 20m
2026-07-01 VSV485 - Jul 1, 03:35 UTCJul 1, 06:00 UTC2h 25m
2026-06-29 VSV470 - Jun 29, 22:59 UTCJun 30, 03:05 UTC4h 5m
2026-06-29 VSV469 - Jun 29, 03:05 UTCJun 29, 21:39 UTC18h 35m
2026-06-29 VSV469 - Jun 29, 02:54 UTCJun 29, 21:39 UTC18h 45m
2026-06-28 VSV469 - Jun 28, 23:14 UTCJun 29, 21:39 UTC22h 25m
2026-06-28 VSV468 - Jun 28, 21:59 UTCJun 28, 22:10 UTC10m
2026-06-28 VSV467 - Jun 28, 18:59 UTCJun 28, 20:34 UTC1h 35m
2026-06-25 VSV468 - Jun 25, 23:49 UTCJun 26, 04:00 UTC4h 10m
2026-06-25 VSV468 - Jun 25, 22:34 UTCJun 25, 22:54 UTC20m
2026-06-25 VSV467 - Jun 25, 20:49 UTCJun 25, 21:15 UTC25m
2026-06-25 VSV490 - Jun 25, 08:04 UTCJun 25, 19:59 UTC11h 55m
2026-06-25 VSV489 - Jun 25, 06:14 UTCJun 25, 07:00 UTC45m
2026-06-23 VSV490 - Jun 23, 15:40 UTCJun 23, 18:39 UTC3h 0m
2026-06-23 VSV489 - Jun 23, 05:00 UTCJun 23, 14:04 UTC9h 5m
2026-06-23 VSV724 - Jun 23, 03:45 UTCJun 23, 04:05 UTC20m
2026-06-22 VSV723 - Jun 22, 15:50 UTCJun 23, 02:04 UTC10h 15m
2026-06-19 VSV844 - Jun 19, 12:09 UTCJun 20, 02:54 UTC14h 45m
2026-06-19 VSV843 - Jun 19, 03:09 UTCJun 19, 10:24 UTC7h 15m
2026-06-18 VSV468 - Jun 18, 22:10 UTCJun 18, 22:30 UTC20m
2026-06-18 VSV467 - Jun 18, 20:20 UTCJun 18, 20:40 UTC20m
2026-06-18 VSV844 - Jun 18, 07:00 UTCJun 18, 07:30 UTC30m
2026-06-18 VSV843 - Jun 18, 04:55 UTCJun 18, 05:25 UTC30m
2026-06-16 VSV484 MUC → CIT Jun 16, 16:00 UTCJun 16, 19:40 UTC3h 40m
2026-06-15 VSV468 ICN → CIT Jun 15, 22:25 UTCJun 16, 14:30 UTC16h 5m
2026-06-15 VSV844 TBS → CIT Jun 15, 10:20 UTCJun 15, 20:45 UTC10h 25m
2026-06-15 VSV843 - Jun 15, 07:29 UTCJun 15, 08:00 UTC30m
2026-06-14 VSV724 UKK → CIT Jun 14, 02:05 UTCJun 14, 02:35 UTC30m
2026-06-14 VSV723 CIT → UKK Jun 14, 00:05 UTCJun 14, 00:30 UTC25m

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

Mode-S 6832B4 frequently asked

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