sensors Mode-S transponder
6832C6
ICAO 24-bit transponder address · allocated to Kazakhstan
Currently assigned to UP-B3749 · BOEING 737 MAX 8
- Hex
- 6832C6
- Octal
- 32031306
- Decimal
- 6,828,742
- Country
- KZ
- Tail
- UP-B3749
- Type
- B38M
- Flights observed
- 163
- Distinct callsigns
- 20
- Country
- KZ
- Last broadcast
- 10d ago
Last known position
Country allocation
The ICAO 24-bit address 6832C6 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 |
|---|---|---|---|
| VSV5332 | - | 63 | 2026-07-24 |
| VSV5333 | - | 44 | 2026-07-23 |
| VSV5334 | Scat Air | 17 | 2026-07-22 |
| VSV498 | Scat Air | 7 | 2026-07-18 |
| VSV5340 | - | 4 | 2026-07-25 |
| VSV5375 | - | 3 | 2026-07-01 |
| VSV821 | Scat Air | 2 | 2026-05-06 |
| VSV725 | - | 2 | 2026-06-14 |
| VSV5341 | Scat Air | 2 | 2026-07-25 |
| VSV5337 | - | 2 | 2026-07-21 |
| VSV5335 | - | 2 | 2026-07-05 |
| VSV468 | Scat Air | 2 | 2026-05-10 |
| VSV467 | Scat Air | 2 | 2026-05-10 |
| VSV844 | Scat Air | 1 | 2026-05-10 |
| VSV843 | Scat Air | 1 | 2026-05-09 |
| VSV813 | Scat Air | 1 | 2026-05-04 |
| VSV804 | - | 1 | 2026-06-30 |
| VSV803 | - | 1 | 2026-06-29 |
| VSV732 | Scat Air | 1 | 2026-05-17 |
| VSV730 | Scat Air | 1 | 2026-05-16 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-25 | VSV5341 | DAD → ALA | Jul 25, 08:55 UTC | Jul 26, 01:30 UTC | 16h 35m |
| 2026-07-25 | VSV5340 | - | Jul 25, 02:50 UTC | Jul 26, 01:30 UTC | 22h 40m |
| 2026-07-24 | VSV5332 | - | Jul 24, 03:35 UTC | Jul 25, 03:00 UTC | 23h 25m |
| 2026-07-24 | VSV5332 | - | Jul 24, 00:25 UTC | Jul 24, 04:20 UTC | 3h 55m |
| 2026-07-23 | VSV5332 | - | Jul 23, 07:35 UTC | Jul 24, 04:20 UTC | 20h 45m |
| 2026-07-23 | VSV5332 | - | Jul 23, 05:35 UTC | Jul 24, 04:20 UTC | 22h 45m |
| 2026-07-23 | VSV5333 | - | Jul 23, 04:25 UTC | Jul 24, 03:30 UTC | 23h 5m |
| 2026-07-22 | VSV5333 | - | Jul 22, 22:55 UTC | Jul 23, 08:05 UTC | 9h 10m |
| 2026-07-22 | VSV5334 | NQZ → HKT | Jul 22, 01:15 UTC | Jul 22, 23:10 UTC | 21h 55m |
| 2026-07-21 | VSV5337 | - | Jul 21, 09:05 UTC | Jul 22, 01:25 UTC | 16h 20m |
| 2026-07-21 | VSV5332 | - | Jul 21, 03:35 UTC | Jul 22, 01:25 UTC | 21h 50m |
| 2026-07-21 | VSV5332 | - | Jul 21, 01:50 UTC | Jul 22, 01:25 UTC | 23h 35m |
| 2026-07-21 | VSV5332 | - | Jul 21, 00:25 UTC | Jul 21, 09:20 UTC | 8h 55m |
| 2026-07-20 | VSV5332 | - | Jul 20, 05:35 UTC | Jul 21, 04:10 UTC | 22h 35m |
| 2026-07-20 | VSV5333 | - | Jul 20, 04:05 UTC | Jul 21, 03:30 UTC | 23h 25m |
| 2026-07-19 | VSV5333 | - | Jul 19, 22:45 UTC | Jul 20, 07:30 UTC | 8h 45m |
| 2026-07-19 | VSV5333 | - | Jul 19, 06:25 UTC | Jul 20, 05:30 UTC | 23h 5m |
| 2026-07-19 | VSV5334 | NQZ → HKT | Jul 19, 00:50 UTC | Jul 19, 22:55 UTC | 22h 5m |
| 2026-07-18 | VSV5334 | NQZ → HKT | Jul 18, 05:35 UTC | Jul 19, 01:05 UTC | 19h 30m |
| 2026-07-18 | VSV498 | JED → CIT | Jul 18, 03:35 UTC | Jul 19, 01:05 UTC | 21h 30m |
| 2026-07-18 | VSV498 | JED → CIT | Jul 18, 03:15 UTC | Jul 19, 01:05 UTC | 21h 50m |
| 2026-07-17 | VSV498 | JED → CIT | Jul 17, 09:04 UTC | Jul 18, 05:40 UTC | 20h 36m |
| 2026-07-17 | VSV5332 | - | Jul 17, 03:34 UTC | Jul 18, 03:30 UTC | 23h 56m |
| 2026-07-17 | VSV5332 | - | Jul 17, 00:20 UTC | Jul 17, 09:20 UTC | 9h 0m |
| 2026-07-16 | VSV5332 | - | Jul 16, 05:35 UTC | Jul 17, 04:14 UTC | 22h 40m |
| 2026-07-16 | VSV5333 | - | Jul 16, 04:20 UTC | Jul 17, 03:30 UTC | 23h 10m |
| 2026-07-15 | VSV5333 | - | Jul 15, 06:30 UTC | Jul 16, 05:30 UTC | 23h 0m |
| 2026-07-15 | VSV5334 | - | Jul 15, 00:40 UTC | Jul 15, 06:40 UTC | 6h 0m |
| 2026-07-14 | VSV5337 | - | Jul 14, 09:20 UTC | Jul 15, 06:40 UTC | 21h 19m |
| 2026-07-14 | VSV5332 | - | Jul 14, 03:35 UTC | Jul 15, 00:50 UTC | 21h 14m |
| 2026-07-14 | VSV5332 | - | Jul 14, 01:35 UTC | Jul 15, 00:50 UTC | 23h 14m |
| 2026-07-14 | VSV5332 | - | Jul 14, 00:35 UTC | Jul 14, 09:30 UTC | 8h 55m |
| 2026-07-13 | VSV5332 | - | Jul 13, 07:35 UTC | Jul 14, 04:30 UTC | 20h 55m |
| 2026-07-13 | VSV5332 | - | Jul 13, 05:35 UTC | Jul 14, 04:30 UTC | 22h 55m |
| 2026-07-13 | VSV5333 | - | Jul 13, 04:25 UTC | Jul 14, 03:30 UTC | 23h 5m |
| 2026-07-12 | VSV5333 | - | Jul 12, 22:45 UTC | Jul 13, 08:01 UTC | 9h 15m |
| 2026-07-12 | VSV5333 | - | Jul 12, 06:30 UTC | Jul 13, 05:31 UTC | 23h 0m |
| 2026-07-12 | VSV5334 | - | Jul 12, 00:45 UTC | Jul 12, 23:00 UTC | 22h 15m |
| 2026-07-11 | VSV5340 | - | Jul 11, 02:30 UTC | Jul 12, 01:00 UTC | 22h 30m |
| 2026-07-10 | VSV5340 | - | Jul 10, 09:10 UTC | Jul 11, 02:45 UTC | 17h 35m |
| 2026-07-10 | VSV5332 | - | Jul 10, 03:35 UTC | Jul 11, 02:45 UTC | 23h 10m |
| 2026-07-10 | VSV5332 | - | Jul 10, 00:25 UTC | Jul 10, 09:20 UTC | 8h 55m |
| 2026-07-09 | VSV5332 | - | Jul 9, 07:35 UTC | Jul 10, 04:35 UTC | 21h 0m |
| 2026-07-09 | VSV5332 | - | Jul 9, 05:35 UTC | Jul 10, 04:35 UTC | 23h 0m |
| 2026-07-09 | VSV5333 | - | Jul 9, 04:20 UTC | Jul 10, 03:30 UTC | 23h 10m |
| 2026-07-08 | VSV5333 | - | Jul 8, 22:45 UTC | Jul 9, 07:55 UTC | 9h 10m |
| 2026-07-08 | VSV5333 | - | Jul 8, 06:40 UTC | Jul 9, 05:30 UTC | 22h 50m |
| 2026-07-08 | VSV5334 | - | Jul 8, 01:35 UTC | Jul 8, 23:00 UTC | 21h 25m |
| 2026-07-08 | VSV5334 | - | Jul 8, 01:25 UTC | Jul 8, 23:00 UTC | 21h 35m |
| 2026-07-07 | VSV5334 | - | Jul 7, 09:20 UTC | Jul 8, 06:50 UTC | 21h 30m |
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-B3749 page for operator, model, and routing details .