sensors Mode-S transponder
6832A2
ICAO 24-bit transponder address · allocated to Kazakhstan
Currently assigned to UP-B3741 · BOEING 737-800
- Hex
- 6832A2
- Octal
- 32031242
- Decimal
- 6,828,706
- Country
- KZ
- Tail
- UP-B3741
- Type
- B738
- Flights observed
- 148
- Distinct callsigns
- 20
- Country
- KZ
- Last broadcast
- Jul 25, 14:05 UTC
Current position
Country allocation
The ICAO 24-bit address 6832A2 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 |
|---|---|---|---|
| VSV818 | Scat Air | 26 | 2026-07-23 |
| VSV817 | Scat Air | 20 | 2026-07-22 |
| VSV824 | Scat Air | 16 | 2026-07-25 |
| VSV841 | Scat Air | 13 | 2026-06-30 |
| VSV823 | Scat Air | 13 | 2026-07-24 |
| VSV804 | Scat Air | 10 | 2026-07-23 |
| VSV842 | - | 9 | 2026-06-30 |
| VSV803 | Scat Air | 6 | 2026-07-23 |
| VSV784 | Scat Air | 5 | 2026-06-10 |
| VSV822 | Scat Air | 3 | 2026-05-04 |
| VSV741 | Scat Air | 3 | 2026-06-11 |
| VSV846 | Scat Air | 2 | 2026-05-19 |
| VSV845 | Scat Air | 2 | 2026-05-18 |
| VSV813 | - | 2 | 2026-07-18 |
| VSV783 | Scat Air | 2 | 2026-06-02 |
| VSV725 | Scat Air | 2 | 2026-04-22 |
| VSV5282 | - | 2 | 2026-06-04 |
| VSV5275 | - | 2 | 2026-06-04 |
| VSV821 | Scat Air | 1 | 2026-05-25 |
| VSV799 | Scat Air | 1 | 2026-06-18 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-25 | VSV824 | BUS → NQZ | Jul 25, 13:20 UTC | Jul 25, 14:05 UTC | 45m |
| 2026-07-24 | VSV823 | NQZ → BUS | Jul 24, 17:35 UTC | Jul 25, 11:50 UTC | 18h 15m |
| 2026-07-24 | VSV3435 | PAE → KEF | Jul 24, 08:05 UTC | Jul 25, 00:30 UTC | 16h 25m |
| 2026-07-23 | VSV804 | DME → AKX | Jul 23, 18:50 UTC | Jul 23, 20:35 UTC | 1h 45m |
| 2026-07-23 | VSV803 | AKX → DME | Jul 23, 16:50 UTC | Jul 23, 17:05 UTC | 15m |
| 2026-07-23 | VSV818 | DXB → NQZ | Jul 23, 02:15 UTC | Jul 23, 13:55 UTC | 11h 40m |
| 2026-07-22 | VSV817 | NQZ → DXB | Jul 22, 23:45 UTC | Jul 23, 00:40 UTC | 55m |
| 2026-07-21 | VSV824 | BUS → NQZ | Jul 21, 15:15 UTC | Jul 21, 16:00 UTC | 45m |
| 2026-07-21 | VSV823 | NQZ → BUS | Jul 21, 13:15 UTC | Jul 21, 13:20 UTC | 5m |
| 2026-07-20 | VSV804 | - | Jul 20, 19:00 UTC | Jul 20, 20:40 UTC | 1h 40m |
| 2026-07-20 | VSV818 | BEG → PRG | Jul 20, 03:00 UTC | Jul 20, 16:55 UTC | 13h 55m |
| 2026-07-20 | VSV817 | NQZ → DXB | Jul 20, 00:20 UTC | Jul 20, 01:00 UTC | 40m |
| 2026-07-18 | VSV813 | - | Jul 18, 19:50 UTC | Jul 18, 20:05 UTC | 15m |
| 2026-07-16 | VSV804 | - | Jul 16, 19:10 UTC | Jul 16, 20:55 UTC | 1h 45m |
| 2026-07-16 | VSV803 | - | Jul 16, 16:49 UTC | Jul 16, 17:14 UTC | 25m |
| 2026-07-16 | VSV818 | - | Jul 16, 02:40 UTC | Jul 16, 04:40 UTC | 2h 0m |
| 2026-07-15 | VSV824 | - | Jul 15, 12:20 UTC | Jul 15, 13:10 UTC | 50m |
| 2026-07-14 | VSV824 | - | Jul 14, 15:45 UTC | Jul 15, 02:55 UTC | 11h 9m |
| 2026-07-14 | VSV823 | - | Jul 14, 13:35 UTC | Jul 14, 14:35 UTC | 1h 0m |
| 2026-07-11 | VSV824 | - | Jul 11, 15:15 UTC | Jul 11, 16:00 UTC | 45m |
| 2026-07-11 | VSV823 | - | Jul 11, 13:00 UTC | Jul 11, 13:55 UTC | 55m |
| 2026-07-10 | VSV824 | - | Jul 10, 13:25 UTC | Jul 10, 14:10 UTC | 45m |
| 2026-07-09 | VSV804 | PRG → BUS | Jul 9, 19:05 UTC | Jul 10, 12:15 UTC | 17h 10m |
| 2026-07-09 | VSV818 | - | Jul 9, 02:20 UTC | Jul 9, 04:25 UTC | 2h 5m |
| 2026-07-08 | VSV824 | BUS → NQZ | Jul 8, 11:55 UTC | Jul 9, 00:40 UTC | 12h 45m |
| 2026-07-07 | VSV823 | NQZ → BUS | Jul 7, 19:35 UTC | Jul 8, 10:45 UTC | 15h 10m |
| 2026-07-07 | VSV823 | NQZ → BUS | Jul 7, 14:35 UTC | Jul 8, 10:45 UTC | 20h 10m |
| 2026-07-07 | VSV824 | BUS → NQZ | Jul 7, 13:55 UTC | Jul 8, 10:45 UTC | 20h 50m |
| 2026-07-07 | VSV823 | NQZ → BUS | Jul 7, 11:50 UTC | Jul 7, 12:50 UTC | 1h 0m |
| 2026-07-06 | VSV823 | NQZ → BUS | Jul 6, 12:35 UTC | Jul 7, 12:30 UTC | 23h 55m |
| 2026-07-06 | VSV784D | - | Jul 6, 12:25 UTC | Jul 6, 12:50 UTC | 25m |
| 2026-07-06 | VSV818 | - | Jul 6, 02:20 UTC | Jul 6, 11:05 UTC | 8h 45m |
| 2026-07-05 | VSV817 | - | Jul 5, 23:55 UTC | Jul 6, 00:30 UTC | 35m |
| 2026-07-04 | VSV824 | BUS → NQZ | Jul 4, 13:35 UTC | Jul 4, 14:20 UTC | 45m |
| 2026-07-04 | VSV823 | NQZ → BUS | Jul 4, 11:25 UTC | Jul 4, 12:20 UTC | 55m |
| 2026-07-03 | VSV824 | BUS → NQZ | Jul 3, 13:20 UTC | Jul 4, 12:20 UTC | 23h 0m |
| 2026-07-02 | VSV804 | PRG → BUS | Jul 2, 19:05 UTC | Jul 3, 12:10 UTC | 17h 5m |
| 2026-07-02 | VSV818 | BEG → PRG | Jul 2, 02:35 UTC | Jul 2, 17:25 UTC | 14h 50m |
| 2026-07-01 | VSV824 | BUS → NQZ | Jul 1, 11:50 UTC | Jul 2, 00:50 UTC | 13h 0m |
| 2026-06-30 | VSV842 | TBS → BUS | Jun 30, 22:35 UTC | Jul 1, 10:25 UTC | 11h 50m |
| 2026-06-30 | VSV841 | SCO → TBS | Jun 30, 20:50 UTC | Jun 30, 21:05 UTC | 15m |
| 2026-06-29 | VSV818 | - | Jun 29, 02:59 UTC | Jun 29, 04:14 UTC | 1h 15m |
| 2026-06-28 | VSV817 | - | Jun 28, 23:50 UTC | Jun 29, 00:44 UTC | 55m |
| 2026-06-27 | VSV824 | BUS → NQZ | Jun 27, 13:35 UTC | Jun 27, 14:14 UTC | 40m |
| 2026-06-27 | VSV823 | NQZ → BUS | Jun 27, 01:44 UTC | Jun 27, 12:19 UTC | 10h 35m |
| 2026-06-26 | VSV824 | BUS → NQZ | Jun 26, 14:29 UTC | Jun 27, 00:05 UTC | 9h 35m |
| 2026-06-25 | VSV804 | PRG → BUS | Jun 25, 19:09 UTC | Jun 26, 13:30 UTC | 18h 20m |
| 2026-06-25 | VSV803 | - | Jun 25, 16:39 UTC | Jun 25, 16:59 UTC | 20m |
| 2026-06-25 | VSV818 | - | Jun 25, 02:10 UTC | Jun 25, 03:20 UTC | 1h 10m |
| 2026-06-24 | VSV824 | BUS → NQZ | Jun 24, 11:59 UTC | Jun 24, 12:50 UTC | 50m |
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-B3741 page for operator, model, and routing details .