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
- 67
- Distinct callsigns
- 19
- Country
- KZ
- Last broadcast
- 19h ago
Last known 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 19 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| VSV818 | Scat Air | 13 | 2026-05-31 |
| VSV817 | Scat Air | 13 | 2026-05-31 |
| VSV841 | Scat Air | 8 | 2026-05-26 |
| VSV842 | Scat Air | 5 | 2026-05-26 |
| VSV784 | Scat Air | 4 | 2026-06-02 |
| VSV822 | Scat Air | 3 | 2026-05-04 |
| VSV804 | Scat Air | 3 | 2026-05-30 |
| VSV803 | Scat Air | 3 | 2026-05-29 |
| VSV846 | Scat Air | 2 | 2026-05-19 |
| VSV845 | Scat Air | 2 | 2026-05-18 |
| VSV783 | Scat Air | 2 | 2026-06-02 |
| VSV725 | Scat Air | 2 | 2026-04-22 |
| VSV821 | Scat Air | 1 | 2026-05-25 |
| VSV813 | Scat Air | 1 | 2026-05-08 |
| VSV726 | Scat Air | 1 | 2026-05-23 |
| VSV5282 | - | 1 | 2026-05-29 |
| VSV5281 | Scat Air | 1 | 2026-05-29 |
| VSV5275 | - | 1 | 2026-05-28 |
| VS817 | - | 1 | 2026-05-24 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | VSV784 | UKK → NQZ | Jun 2, 07:30 UTC | Jun 2, 07:55 UTC | 25m |
| 2026-06-02 | VSV783 | NQZ → UKK | Jun 2, 05:40 UTC | Jun 2, 06:05 UTC | 25m |
| 2026-05-31 | VSV818 | DXB → NQZ | May 31, 21:50 UTC | May 31, 23:45 UTC | 1h 55m |
| 2026-05-31 | VSV817 | NQZ → DXB | May 31, 17:10 UTC | May 31, 20:25 UTC | 3h 15m |
| 2026-05-30 | VSV804 | DME → AKX | May 30, 11:55 UTC | May 30, 15:25 UTC | 3h 30m |
| 2026-05-29 | VSV803 | AKX → DME | May 29, 14:35 UTC | May 30, 10:25 UTC | 19h 50m |
| 2026-05-29 | VSV803 | AKX → DME | May 29, 12:35 UTC | May 30, 10:25 UTC | 21h 50m |
| 2026-05-29 | VSV5282 | - | May 29, 10:40 UTC | May 29, 10:50 UTC | 10m |
| 2026-05-29 | VSV5281 | AYT → AKX | May 29, 01:40 UTC | May 29, 09:55 UTC | 8h 15m |
| 2026-05-28 | VSV5275 | - | May 28, 21:55 UTC | May 29, 00:05 UTC | 2h 10m |
| 2026-05-27 | VSV784 | UKK → NQZ | May 27, 12:55 UTC | May 27, 13:20 UTC | 25m |
| 2026-05-26 | VSV842 | TBS → SCO | May 26, 22:05 UTC | May 27, 10:25 UTC | 12h 20m |
| 2026-05-26 | VSV841 | SCO → TBS | May 26, 20:29 UTC | May 26, 20:50 UTC | 20m |
| 2026-05-25 | VSV821 | NQZ → LED | May 25, 07:50 UTC | May 25, 08:05 UTC | 15m |
| 2026-05-24 | VSV818 | DXB → NQZ | May 24, 21:00 UTC | May 24, 21:45 UTC | 45m |
| 2026-05-24 | VS817 | - | May 24, 15:10 UTC | May 24, 15:25 UTC | 15m |
| 2026-05-23 | VSV726 | UKK → ALA | May 23, 04:15 UTC | May 23, 04:35 UTC | 20m |
| 2026-05-22 | VSV783 | NQZ → UKK | May 22, 17:00 UTC | May 23, 02:45 UTC | 9h 45m |
| 2026-05-21 | VSV842 | TBS → SCO | May 21, 21:45 UTC | May 22, 17:10 UTC | 19h 25m |
| 2026-05-21 | VSV841 | SCO → TBS | May 21, 20:15 UTC | May 21, 20:45 UTC | 30m |
| 2026-05-20 | VSV818 | DXB → NQZ | May 20, 20:35 UTC | May 21, 20:30 UTC | 23h 55m |
| 2026-05-20 | VSV818 | DXB → NQZ | May 20, 20:25 UTC | May 20, 22:15 UTC | 1h 50m |
| 2026-05-20 | VSV817 | NQZ → DXB | May 20, 00:55 UTC | May 20, 19:25 UTC | 18h 31m |
| 2026-05-19 | VSV817 | NQZ → DXB | May 19, 22:35 UTC | May 20, 19:25 UTC | 20h 51m |
| 2026-05-19 | VSV817 | NQZ → DXB | May 19, 22:10 UTC | May 20, 19:25 UTC | 21h 16m |
| 2026-05-19 | VSV841 | SCO → TBS | May 19, 20:50 UTC | May 19, 21:10 UTC | 20m |
| 2026-05-19 | VSV846 | EVN → SCO | May 19, 01:25 UTC | May 19, 11:35 UTC | 10h 10m |
| 2026-05-18 | VSV845 | SCO → EVN | May 18, 23:45 UTC | May 19, 00:10 UTC | 25m |
| 2026-05-17 | VSV818 | DXB → NQZ | May 17, 21:25 UTC | May 17, 23:10 UTC | 1h 45m |
| 2026-05-17 | VSV817 | NQZ → DXB | May 17, 16:10 UTC | May 17, 20:15 UTC | 4h 5m |
| 2026-05-16 | VSV804 | DME → AKX | May 16, 11:25 UTC | May 16, 13:01 UTC | 1h 35m |
| 2026-05-16 | VSV803 | AKX → DME | May 16, 05:05 UTC | May 16, 09:40 UTC | 4h 36m |
| 2026-05-12 | VSV804 | DME → AKX | May 12, 11:25 UTC | May 12, 13:15 UTC | 1h 50m |
| 2026-05-10 | VSV818 | DXB → NQZ | May 10, 22:09 UTC | May 11, 02:15 UTC | 4h 5m |
| 2026-05-10 | VSV817 | NQZ → DXB | May 10, 15:39 UTC | May 10, 17:20 UTC | 1h 40m |
| 2026-05-08 | VSV813 | ALA → TAS | May 8, 18:20 UTC | May 8, 18:55 UTC | 35m |
| 2026-05-06 | VSV818 | DXB → NQZ | May 6, 20:40 UTC | May 6, 22:40 UTC | 2h 0m |
| 2026-05-05 | VSV842 | TBS → SCO | May 5, 22:15 UTC | May 6, 16:10 UTC | 17h 55m |
| 2026-05-05 | VSV841 | SCO → TBS | May 5, 20:45 UTC | May 5, 21:15 UTC | 30m |
| 2026-05-04 | VSV822 | LED → NQZ | May 4, 09:55 UTC | May 4, 10:15 UTC | 20m |
| 2026-05-03 | VSV818 | DXB → NQZ | May 3, 20:49 UTC | May 3, 23:00 UTC | 2h 10m |
| 2026-05-03 | VSV817 | NQZ → DXB | May 3, 15:00 UTC | May 3, 19:40 UTC | 4h 40m |
| 2026-05-01 | VSV822 | LED → NQZ | May 1, 11:25 UTC | May 1, 11:55 UTC | 30m |
| 2026-05-01 | VSV822 | LED → NQZ | May 1, 10:05 UTC | May 1, 10:25 UTC | 20m |
| 2026-04-26 | VSV818 | DXB → NQZ | Apr 26, 21:00 UTC | Apr 26, 23:45 UTC | 2h 45m |
| 2026-04-26 | VSV817 | NQZ → DXB | Apr 26, 16:00 UTC | Apr 26, 19:45 UTC | 3h 45m |
| 2026-04-25 | VSV817 | NQZ → DXB | Apr 25, 22:35 UTC | Apr 26, 19:45 UTC | 21h 10m |
| 2026-04-25 | VSV817 | NQZ → DXB | Apr 25, 22:20 UTC | Apr 26, 19:45 UTC | 21h 25m |
| 2026-04-25 | VSV841 | SCO → TBS | Apr 25, 20:55 UTC | Apr 25, 21:10 UTC | 15m |
| 2026-04-23 | VSV842 | TBS → SCO | Apr 23, 21:55 UTC | Apr 23, 22:20 UTC | 25m |
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 .