sensors Mode-S transponder
6832B2
ICAO 24-bit transponder address · allocated to Kazakhstan
Currently assigned to UP-B3743 · BOEING 737 MAX 8
- Hex
- 6832B2
- Octal
- 32031262
- Decimal
- 6,828,722
- Country
- KZ
- Tail
- UP-B3743
- Type
- B38M
- Flights observed
- 34
- Distinct callsigns
- 11
- Country
- KZ
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 6832B2 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 11 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| VSV843 | Scat Air | 7 | 2026-05-25 |
| VSV486 | Scat Air | 6 | 2026-05-28 |
| VSV485 | Scat Air | 5 | 2026-05-28 |
| VSV844 | Scat Air | 4 | 2026-05-14 |
| VSV490 | Scat Air | 2 | 2026-05-19 |
| VSV470 | Scat Air | 2 | 2026-05-25 |
| VSV469 | Scat Air | 2 | 2026-05-25 |
| VSV468 | Scat Air | 2 | 2026-05-18 |
| VSV467 | Scat Air | 2 | 2026-05-18 |
| VSV821 | Scat Air | 1 | 2026-04-13 |
| VSV489 | Scat Air | 1 | 2026-04-23 |
Recent flights last 34
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-28 | VSV486 | IST → CIT | May 28, 06:45 UTC | May 28, 08:45 UTC | 2h 0m |
| 2026-05-28 | VSV485 | CIT → IST | May 28, 02:55 UTC | May 28, 05:25 UTC | 2h 30m |
| 2026-05-25 | VSV470 | BKK → CIT | May 25, 22:49 UTC | May 26, 03:09 UTC | 4h 20m |
| 2026-05-25 | VSV469 | CIT → BKK | May 25, 10:40 UTC | May 25, 21:15 UTC | 10h 34m |
| 2026-05-25 | VSV843 | CIT → TBS | May 25, 08:35 UTC | May 25, 09:05 UTC | 30m |
| 2026-05-22 | VSV486 | IST → CIT | May 22, 20:30 UTC | May 22, 22:30 UTC | 2h 0m |
| 2026-05-22 | VSV485 | CIT → IST | May 22, 17:45 UTC | May 22, 18:00 UTC | 15m |
| 2026-05-22 | VSV485 | CIT → IST | May 22, 15:50 UTC | May 22, 16:55 UTC | 1h 5m |
| 2026-05-21 | VSV486 | IST → CIT | May 21, 07:15 UTC | May 21, 09:20 UTC | 2h 5m |
| 2026-05-21 | VSV485 | CIT → IST | May 21, 04:55 UTC | May 21, 05:10 UTC | 15m |
| 2026-05-20 | VSV486 | IST → CIT | May 20, 08:35 UTC | May 21, 04:00 UTC | 19h 25m |
| 2026-05-20 | VSV486 | IST → CIT | May 20, 07:40 UTC | May 21, 04:00 UTC | 20h 20m |
| 2026-05-20 | VSV485 | CIT → IST | May 20, 05:40 UTC | May 20, 05:50 UTC | 10m |
| 2026-05-19 | VSV490 | BUD → CIT | May 19, 15:25 UTC | May 20, 04:50 UTC | 13h 26m |
| 2026-05-18 | VSV468 | ICN → CIT | May 18, 22:20 UTC | May 19, 14:00 UTC | 15h 40m |
| 2026-05-18 | VSV467 | CIT → ICN | May 18, 10:05 UTC | May 18, 20:10 UTC | 10h 4m |
| 2026-05-18 | VSV843 | CIT → TBS | May 18, 07:45 UTC | May 18, 08:15 UTC | 30m |
| 2026-05-14 | VSV844 | TBS → CIT | May 14, 07:20 UTC | May 14, 07:50 UTC | 30m |
| 2026-05-14 | VSV843 | CIT → TBS | May 14, 04:55 UTC | May 14, 05:25 UTC | 30m |
| 2026-05-12 | VSV470 | BKK → CIT | May 12, 02:45 UTC | May 12, 09:55 UTC | 7h 10m |
| 2026-05-11 | VSV469 | CIT → BKK | May 11, 10:30 UTC | May 11, 21:10 UTC | 10h 40m |
| 2026-05-11 | VSV843 | CIT → TBS | May 11, 07:35 UTC | May 11, 08:00 UTC | 25m |
| 2026-05-08 | VSV486 | IST → CIT | May 8, 16:15 UTC | May 8, 22:35 UTC | 6h 20m |
| 2026-05-04 | VSV468 | ICN → CIT | May 4, 22:00 UTC | May 4, 23:40 UTC | 1h 40m |
| 2026-05-04 | VSV467 | CIT → ICN | May 4, 20:30 UTC | May 4, 20:40 UTC | 10m |
| 2026-05-04 | VSV844 | TBS → CIT | May 4, 10:10 UTC | May 4, 19:20 UTC | 9h 11m |
| 2026-05-04 | VSV843 | CIT → TBS | May 4, 07:40 UTC | May 4, 08:10 UTC | 30m |
| 2026-04-30 | VSV844 | TBS → CIT | Apr 30, 10:55 UTC | Apr 30, 11:25 UTC | 30m |
| 2026-04-30 | VSV843 | CIT → TBS | Apr 30, 05:30 UTC | Apr 30, 06:05 UTC | 35m |
| 2026-04-23 | VSV490 | BUD → CIT | Apr 23, 07:05 UTC | Apr 23, 10:05 UTC | 3h 0m |
| 2026-04-23 | VSV489 | CIT → BUD | Apr 23, 04:50 UTC | Apr 23, 05:30 UTC | 40m |
| 2026-04-20 | VSV844 | TBS → CIT | Apr 20, 10:05 UTC | Apr 20, 10:30 UTC | 25m |
| 2026-04-20 | VSV843 | CIT → TBS | Apr 20, 07:30 UTC | Apr 20, 08:00 UTC | 30m |
| 2026-04-13 | VSV821 | NQZ → LED | Apr 13, 05:15 UTC | Apr 13, 05:25 UTC | 10m |
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-B3743 page for operator, model, and routing details .