sensors Mode-S transponder

6832A3

ICAO 24-bit transponder address · allocated to Kazakhstan

Currently assigned to UP-B3742 · BOEING 737 MAX 8

Hex
6832A3
Octal
32031243
Decimal
6,828,707
Country
KZ
Tail
UP-B3742
Type
B38M
No current signal · last broadcast 8h ago
Flights observed
42
Distinct callsigns
14
Country
KZ
Last broadcast
8h ago

Last known position

Most recent position reported by Mode-S 6832A3.

Country allocation

The ICAO 24-bit address 6832A3 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 14 distinct

Callsign Airline Flights Last seen
VSV486 Scat Air 8 2026-05-29
VSV485 Scat Air 6 2026-05-29
VSV843 Scat Air 4 2026-05-21
VSV490 Scat Air 4 2026-06-02
VSV489 Scat Air 4 2026-06-02
VSV844 Scat Air 3 2026-05-07
VSV724 Scat Air 3 2026-05-26
VSV723 Scat Air 2 2026-05-23
VSV468 Scat Air 2 2026-05-14
VSV467 Scat Air 2 2026-04-20
VSV760 Scat Air 1 2026-05-27
VSV484 Scat Air 1 2026-05-26
VSV470 Scat Air 1 2026-05-21
VSV469 Scat Air 1 2026-05-21

Recent flights last 42

DateFlightRouteTakeoffLandingDuration
2026-06-02 VSV490 BUD → CIT Jun 2, 15:35 UTCJun 2, 17:05 UTC1h 30m
2026-06-02 VSV489 CIT → BUD Jun 2, 13:40 UTCJun 2, 14:25 UTC45m
2026-05-29 VSV486 IST → CIT May 29, 20:25 UTCMay 29, 22:20 UTC1h 55m
2026-05-29 VSV485 CIT → IST May 29, 15:55 UTCMay 29, 18:25 UTC2h 30m
2026-05-27 VSV760 NQZ → ALA May 27, 04:14 UTCMay 27, 04:24 UTC10m
2026-05-26 VSV484 MUC → CIT May 26, 15:49 UTCMay 26, 17:35 UTC1h 45m
2026-05-26 VSV724 UKK → CIT May 26, 03:45 UTCMay 26, 04:10 UTC25m
2026-05-25 VSV486 IST → CIT May 25, 19:00 UTCMay 26, 02:00 UTC6h 59m
2026-05-25 VSV486 IST → CIT May 25, 18:05 UTCMay 25, 18:15 UTC10m
2026-05-25 VSV485 CIT → IST May 25, 15:55 UTCMay 25, 16:05 UTC10m
2026-05-25 VSV485 CIT → IST May 25, 13:50 UTCMay 25, 15:10 UTC1h 20m
2026-05-24 VSV724 UKK → CIT May 24, 02:05 UTCMay 24, 02:30 UTC25m
2026-05-23 VSV723 CIT → UKK May 23, 23:55 UTCMay 24, 00:25 UTC30m
2026-05-21 VSV470 BKK → CIT May 21, 23:05 UTCMay 22, 03:25 UTC4h 20m
2026-05-21 VSV469 CIT → BKK May 21, 07:15 UTCMay 21, 21:35 UTC14h 20m
2026-05-21 VSV843 CIT → TBS May 21, 05:05 UTCMay 21, 05:30 UTC25m
2026-05-20 VSV724 UKK → CIT May 20, 04:15 UTCMay 20, 04:35 UTC20m
2026-05-20 VSV723 CIT → UKK May 20, 02:15 UTCMay 20, 02:45 UTC30m
2026-05-14 VSV468 ICN → CIT May 14, 22:00 UTCMay 14, 22:15 UTC15m
2026-05-14 VSV490 BUD → CIT May 14, 07:05 UTCMay 14, 20:25 UTC13h 20m
2026-05-14 VSV489 CIT → BUD May 14, 04:55 UTCMay 14, 05:35 UTC40m
2026-05-13 VSV486 IST → CIT May 13, 08:50 UTCMay 14, 05:35 UTC20h 45m
2026-05-13 VSV486 IST → CIT May 13, 08:30 UTCMay 14, 05:35 UTC21h 5m
2026-05-12 VSV490 BUD → CIT May 12, 16:00 UTCMay 13, 04:45 UTC12h 45m
2026-05-12 VSV489 CIT → BUD May 12, 13:30 UTCMay 12, 14:40 UTC1h 10m
2026-05-07 VSV844 TBS → CIT May 7, 07:10 UTCMay 7, 07:35 UTC25m
2026-05-07 VSV843 CIT → TBS May 7, 05:25 UTCMay 7, 05:45 UTC20m
2026-05-05 VSV490 BUD → CIT May 5, 16:10 UTCMay 5, 19:15 UTC3h 5m
2026-05-05 VSV489 CIT → BUD May 5, 13:30 UTCMay 5, 14:55 UTC1h 25m
2026-05-03 VSV844 TBS → CIT May 3, 07:05 UTCMay 3, 07:30 UTC25m
2026-05-03 VSV843 CIT → TBS May 3, 05:00 UTCMay 3, 05:20 UTC20m
2026-05-01 VSV486 IST → CIT May 1, 21:10 UTCMay 1, 22:15 UTC1h 5m
2026-05-01 VSV485 CIT → IST May 1, 15:45 UTCMay 1, 17:05 UTC1h 20m
2026-04-27 VSV844 TBS → CIT Apr 27, 10:15 UTCApr 27, 10:45 UTC30m
2026-04-27 VSV843 CIT → TBS Apr 27, 07:40 UTCApr 27, 08:15 UTC35m
2026-04-24 VSV485 CIT → IST Apr 24, 15:55 UTCApr 24, 22:15 UTC6h 20m
2026-04-20 VSV468 ICN → CIT Apr 20, 21:55 UTCApr 20, 23:45 UTC1h 50m
2026-04-20 VSV467 CIT → ICN Apr 20, 19:50 UTCApr 20, 20:10 UTC20m
2026-04-20 VSV467 CIT → ICN Apr 20, 18:45 UTCApr 20, 19:05 UTC20m
2026-04-15 VSV486 IST → CIT Apr 15, 09:00 UTCApr 15, 09:35 UTC35m
2026-04-15 VSV486 IST → CIT Apr 15, 08:30 UTCApr 15, 08:55 UTC25m
2026-04-15 VSV485 CIT → IST Apr 15, 03:25 UTCApr 15, 04:45 UTC1h 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-B3742 page for operator, model, and routing details .

Mode-S 6832A3 frequently asked

What is Mode-S code 6832A3?
6832A3 is an ICAO 24-bit transponder address. Allocated to Kazakhstan. Assigned to UP-B3742.
Where is Mode-S 6832A3 registered?
Mode-S code 6832A3 is allocated to Kazakhstan (KZ). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 6832A3 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 6832A3, octal 32031243, decimal 6,828,707.
What flights does 6832A3 operate?
Mode-S 6832A3 has broadcast 14 distinct callsigns, including VSV486, VSV485, VSV843, VSV490, VSV489.