sensors Mode-S transponder

6832C5

ICAO 24-bit transponder address · allocated to Kazakhstan

Currently assigned to UP-B3748 · BOEING 737 MAX 8

Hex
6832C5
Octal
32031305
Decimal
6,828,741
Country
KZ
Tail
UP-B3748
Type
B38M
No current signal · last broadcast 4d ago
Flights observed
97
Distinct callsigns
20
Country
KZ
Last broadcast
4d ago

Last known position

Most recent position reported by Mode-S 6832C5.

Country allocation

The ICAO 24-bit address 6832C5 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
VSV5348 - 15 2026-07-10
VSV5328 - 9 2026-07-21
VSV5263 - 9 2026-06-28
VSV5374 - 8 2026-07-22
VSV5334 Scat Air 8 2026-07-20
VSV5341 - 7 2026-07-16
VSV5375 - 5 2026-07-15
VSV5340 - 4 2026-07-16
VSV821 Scat Air 3 2026-05-27
VSV803 Scat Air 3 2026-05-05
VSV726 - 3 2026-07-15
VSV725 - 3 2026-06-17
VSV5264 - 3 2026-06-28
VSV813 Scat Air 2 2026-05-03
VSV729 Scat Air 2 2026-06-03
VSV5335 - 2 2026-07-20
VSV489 Scat Air 2 2026-07-22
VSV822 Scat Air 1 2026-05-27
VSV818 Scat Air 1 2026-04-29
VSV817 Scat Air 1 2026-04-29

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-24 VSV486 IST → CIT Jul 24, 20:20 UTCJul 24, 22:15 UTC1h 55m
2026-07-24 VSV470 BKK → CIT Jul 24, 00:55 UTCJul 24, 18:10 UTC17h 15m
2026-07-23 VSV469 CIT → BKK Jul 23, 08:10 UTCJul 23, 21:50 UTC13h 40m
2026-07-22 VSV489 CIT → BUD Jul 22, 11:20 UTCJul 23, 06:35 UTC19h 15m
2026-07-22 VSV489 CIT → BUD Jul 22, 10:20 UTCJul 23, 06:35 UTC20h 15m
2026-07-22 VSV5374 - Jul 22, 03:35 UTCJul 23, 03:15 UTC23h 40m
2026-07-22 VSV5374 - Jul 22, 01:20 UTCJul 22, 11:30 UTC10h 10m
2026-07-21 VSV5374 - Jul 21, 09:55 UTCJul 22, 04:50 UTC18h 55m
2026-07-21 VSV5328 - Jul 21, 02:30 UTCJul 21, 10:10 UTC7h 40m
2026-07-20 VSV5335 - Jul 20, 10:00 UTCJul 21, 02:45 UTC16h 45m
2026-07-20 VSV5334 NQZ → HKT Jul 20, 03:45 UTCJul 21, 02:45 UTC23h 0m
2026-07-17 VSV5349 - Jul 17, 23:10 UTCJul 18, 04:45 UTC5h 36m
2026-07-17 VSV5334 - Jul 17, 00:10 UTCJul 17, 23:14 UTC23h 5m
2026-07-16 VSV5341 - Jul 16, 09:05 UTCJul 17, 00:20 UTC15h 15m
2026-07-16 VSV5340 - Jul 16, 02:30 UTCJul 17, 00:20 UTC21h 50m
2026-07-15 VSV726 - Jul 15, 17:45 UTCJul 16, 09:15 UTC15h 30m
2026-07-15 VSV5375 - Jul 15, 00:40 UTCJul 15, 16:20 UTC15h 40m
2026-07-14 VSV5374 - Jul 14, 08:45 UTCJul 15, 04:15 UTC19h 29m
2026-07-14 VSV5328 - Jul 14, 02:40 UTCJul 15, 00:40 UTC21h 59m
2026-07-13 VSV5328 - Jul 13, 09:45 UTCJul 14, 09:00 UTC23h 15m
2026-07-13 VSV5328 - Jul 13, 03:50 UTCJul 14, 03:05 UTC23h 15m
2026-07-10 VSV5348 - Jul 10, 19:00 UTCJul 11, 05:01 UTC10h 1m
2026-07-10 VSV5348 - Jul 10, 06:05 UTCJul 10, 23:45 UTC17h 40m
2026-07-10 VSV5334 - Jul 10, 00:10 UTCJul 10, 19:15 UTC19h 5m
2026-07-09 VSV5341 - Jul 9, 08:55 UTCJul 10, 06:20 UTC21h 25m
2026-07-09 VSV5341 - Jul 9, 02:35 UTCJul 10, 00:25 UTC21h 50m
2026-07-08 VSV5375 - Jul 8, 09:20 UTCJul 9, 09:15 UTC23h 55m
2026-07-08 VSV5375 - Jul 8, 07:40 UTCJul 9, 02:45 UTC19h 5m
2026-07-08 VSV5375 - Jul 8, 04:00 UTCJul 9, 02:45 UTC22h 45m
2026-07-08 VSV5374 - Jul 8, 01:00 UTCJul 8, 11:15 UTC10h 15m
2026-07-07 VSV5374 - Jul 7, 09:30 UTCJul 8, 08:30 UTC23h 0m
2026-07-03 VSV5348 - Jul 3, 18:50 UTCJul 4, 05:20 UTC10h 30m
2026-07-03 VSV5348 - Jul 3, 07:20 UTCJul 4, 05:20 UTC22h 0m
2026-07-03 VSV5348 - Jul 3, 02:00 UTCJul 4, 00:35 UTC22h 35m
2026-07-02 VSV5341 - Jul 2, 08:20 UTCJul 3, 02:50 UTC18h 30m
2026-07-02 VSV5341 - Jul 2, 02:50 UTCJul 2, 09:05 UTC6h 15m
2026-07-01 VSV5335 - Jul 1, 05:55 UTCJul 2, 03:00 UTC21h 5m
2026-07-01 VSV5334 - Jul 1, 00:55 UTCJul 1, 06:35 UTC5h 40m
2026-06-30 VSV5334 - Jun 30, 08:10 UTCJul 1, 06:35 UTC22h 25m
2026-06-30 VSV5334 - Jun 30, 03:20 UTCJul 1, 01:10 UTC21h 50m
2026-06-30 VSV5328 - Jun 30, 02:35 UTCJul 1, 01:10 UTC22h 35m
2026-06-29 VSV5328 - Jun 29, 09:54 UTCJun 30, 08:55 UTC23h 0m
2026-06-29 VSV5328 - Jun 29, 09:14 UTCJun 30, 03:20 UTC18h 6m
2026-06-28 VSV5263 - Jun 28, 15:20 UTCJun 29, 10:10 UTC18h 50m
2026-06-28 VSV5263 - Jun 28, 13:45 UTCJun 29, 10:10 UTC20h 25m
2026-06-28 VSV5264 - Jun 28, 08:39 UTCJun 28, 11:29 UTC2h 50m
2026-06-26 VSV5348 - Jun 26, 18:44 UTCJun 27, 04:09 UTC9h 25m
2026-06-26 VSV5348 - Jun 26, 06:00 UTCJun 27, 04:09 UTC22h 10m
2026-06-26 VSV5348 - Jun 26, 01:10 UTCJun 26, 19:04 UTC17h 55m
2026-06-25 VSV5341 - Jun 25, 08:20 UTCJun 26, 06:04 UTC21h 45m

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

Mode-S 6832C5 frequently asked

What is Mode-S code 6832C5?
6832C5 is an ICAO 24-bit transponder address. Allocated to Kazakhstan. Assigned to UP-B3748.
Where is Mode-S 6832C5 registered?
Mode-S code 6832C5 is allocated to Kazakhstan (KZ). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 6832C5 broadcasting right now?
No active broadcast right now. Last signal was 4d ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 6832C5, octal 32031305, decimal 6,828,741.
What flights does 6832C5 operate?
Mode-S 6832C5 has broadcast 20 distinct callsigns, including VSV5348, VSV5328, VSV5263, VSV5374, VSV5334.