sensors Mode-S transponder
6832B4
ICAO 24-bit transponder address · allocated to Kazakhstan
Currently assigned to UP-B3745 · BOEING 737 MAX 8
- Hex
- 6832B4
- Octal
- 32031264
- Decimal
- 6,828,724
- Country
- KZ
- Tail
- UP-B3745
- Type
- B38M
- Flights observed
- 35
- Distinct callsigns
- 19
- Country
- KZ
- Last broadcast
- 5h ago
Last known position
Country allocation
The ICAO 24-bit address 6832B4 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 |
|---|---|---|---|
| VSV470 | Scat Air | 5 | 2026-05-18 |
| VSV469 | Scat Air | 4 | 2026-05-18 |
| VSV485 | Scat Air | 3 | 2026-05-03 |
| VSV467 | Scat Air | 3 | 2026-05-31 |
| VSV803 | Scat Air | 2 | 2026-05-09 |
| VSV723 | Scat Air | 2 | 2026-06-02 |
| VSV489 | Scat Air | 2 | 2026-04-30 |
| VSV486 | Scat Air | 2 | 2026-05-03 |
| VSV468 | Scat Air | 2 | 2026-05-31 |
| VSV844 | Scat Air | 1 | 2026-04-17 |
| VSV843 | Scat Air | 1 | 2026-04-17 |
| VSV828 | Scat Air | 1 | 2026-05-21 |
| VSV804 | Scat Air | 1 | 2026-05-09 |
| VSV741 | Scat Air | 1 | 2026-05-13 |
| VSV730D | - | 1 | 2026-05-15 |
| VSV5351 | Scat Air | 1 | 2026-05-16 |
| VSV490 | Scat Air | 1 | 2026-04-21 |
| VSV484 | Scat Air | 1 | 2026-06-02 |
| VSV483 | Scat Air | 1 | 2026-06-02 |
Recent flights last 35
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | VSV484 | MUC → CIT | Jun 2, 16:15 UTC | Jun 2, 18:05 UTC | 1h 50m |
| 2026-06-02 | VSV483 | CIT → MUC | Jun 2, 04:10 UTC | Jun 2, 14:50 UTC | 10h 40m |
| 2026-06-02 | VSV723 | CIT → UKK | Jun 2, 02:10 UTC | Jun 2, 02:50 UTC | 40m |
| 2026-06-01 | VSV723 | CIT → UKK | Jun 1, 03:55 UTC | Jun 2, 02:50 UTC | 22h 55m |
| 2026-05-31 | VSV468 | ICN → CIT | May 31, 22:15 UTC | Jun 1, 04:25 UTC | 6h 10m |
| 2026-05-31 | VSV467 | CIT → ICN | May 31, 20:20 UTC | May 31, 20:50 UTC | 30m |
| 2026-05-21 | VSV828 | KJA → CIT | May 21, 18:40 UTC | May 22, 00:25 UTC | 5h 45m |
| 2026-05-18 | VSV470 | BKK → CIT | May 18, 22:55 UTC | May 19, 03:15 UTC | 4h 20m |
| 2026-05-18 | VSV469 | CIT → BKK | May 18, 17:25 UTC | May 18, 21:25 UTC | 3h 59m |
| 2026-05-16 | VSV5351 | ALA → NQZ | May 16, 13:35 UTC | May 16, 14:05 UTC | 30m |
| 2026-05-15 | VSV730D | - | May 15, 08:30 UTC | May 15, 08:50 UTC | 20m |
| 2026-05-13 | VSV741 | NQZ → SCO | May 13, 17:35 UTC | May 13, 17:55 UTC | 20m |
| 2026-05-09 | VSV804 | DME → AKX | May 9, 11:35 UTC | May 9, 14:55 UTC | 3h 20m |
| 2026-05-09 | VSV803 | AKX → DME | May 9, 09:40 UTC | May 9, 09:50 UTC | 10m |
| 2026-05-09 | VSV803 | AKX → DME | May 9, 05:10 UTC | May 9, 06:40 UTC | 1h 30m |
| 2026-05-03 | VSV486 | IST → CIT | May 3, 13:30 UTC | May 3, 14:40 UTC | 1h 10m |
| 2026-05-03 | VSV485 | CIT → IST | May 3, 08:30 UTC | May 3, 09:50 UTC | 1h 20m |
| 2026-04-30 | VSV470 | BKK → CIT | Apr 30, 23:15 UTC | May 1, 03:40 UTC | 4h 25m |
| 2026-04-30 | VSV469 | CIT → BKK | Apr 30, 08:50 UTC | Apr 30, 21:40 UTC | 12h 50m |
| 2026-04-30 | VSV489 | CIT → BUD | Apr 30, 05:25 UTC | Apr 30, 05:30 UTC | 5m |
| 2026-04-27 | VSV468 | ICN → CIT | Apr 27, 22:00 UTC | Apr 27, 23:50 UTC | 1h 50m |
| 2026-04-27 | VSV467 | CIT → ICN | Apr 27, 19:55 UTC | Apr 27, 20:15 UTC | 20m |
| 2026-04-27 | VSV467 | CIT → ICN | Apr 27, 18:50 UTC | Apr 27, 19:10 UTC | 20m |
| 2026-04-26 | VSV485 | CIT → IST | Apr 26, 09:45 UTC | Apr 26, 15:45 UTC | 6h 0m |
| 2026-04-21 | VSV490 | BUD → CIT | Apr 21, 18:50 UTC | Apr 21, 21:40 UTC | 2h 50m |
| 2026-04-21 | VSV489 | CIT → BUD | Apr 21, 16:45 UTC | Apr 21, 17:40 UTC | 55m |
| 2026-04-17 | VSV844 | TBS → CIT | Apr 17, 12:15 UTC | Apr 17, 12:40 UTC | 25m |
| 2026-04-17 | VSV843 | CIT → TBS | Apr 17, 10:05 UTC | Apr 17, 10:35 UTC | 30m |
| 2026-04-17 | VSV470 | BKK → CIT | Apr 17, 01:20 UTC | Apr 17, 03:15 UTC | 1h 55m |
| 2026-04-17 | VSV470 | BKK → CIT | Apr 17, 00:20 UTC | Apr 17, 01:15 UTC | 55m |
| 2026-04-16 | VSV470 | BKK → CIT | Apr 16, 22:50 UTC | Apr 16, 23:00 UTC | 10m |
| 2026-04-16 | VSV469 | CIT → BKK | Apr 16, 19:15 UTC | Apr 16, 21:10 UTC | 1h 55m |
| 2026-04-16 | VSV469 | CIT → BKK | Apr 16, 17:20 UTC | Apr 16, 19:10 UTC | 1h 50m |
| 2026-04-13 | VSV486 | - | Apr 13, 21:30 UTC | Apr 13, 22:35 UTC | 1h 5m |
| 2026-04-13 | VSV485 | - | Apr 13, 16:30 UTC | Apr 13, 17:55 UTC | 1h 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-B3745 page for operator, model, and routing details .