sensors Mode-S transponder
683296
ICAO 24-bit transponder address · allocated to Kazakhstan
Currently assigned to UP-B3730 · BOEING 737-800
- Hex
- 683296
- Octal
- 32031226
- Decimal
- 6,828,694
- Country
- KZ
- Tail
- UP-B3730
- Type
- B738
- Flights observed
- 41
- Distinct callsigns
- 14
- Country
- KZ
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 683296 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 14 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| VSV803 | Scat Air | 9 | 2026-05-26 |
| VSV822 | Scat Air | 6 | 2026-05-29 |
| VSV804 | Scat Air | 5 | 2026-05-26 |
| VSV813 | Scat Air | 4 | 2026-04-26 |
| VSV818 | Scat Air | 3 | 2026-04-22 |
| VSV821 | Scat Air | 2 | 2026-05-22 |
| VSV784 | Scat Air | 2 | 2026-05-28 |
| VSV732 | Scat Air | 2 | 2026-05-18 |
| VSV731 | Scat Air | 2 | 2026-05-17 |
| VSV725 | Scat Air | 2 | 2026-05-28 |
| VSV817 | Scat Air | 1 | 2026-04-22 |
| VSV730D | - | 1 | 2026-05-17 |
| VSV730 | Scat Air | 1 | 2026-05-15 |
| VSV703 | Scat Air | 1 | 2026-04-17 |
Recent flights last 41
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | VSV822 | LED → NQZ | May 29, 06:00 UTC | May 29, 10:55 UTC | 4h 55m |
| 2026-05-28 | VSV784 | UKK → NQZ | May 28, 12:55 UTC | May 29, 10:55 UTC | 22h 0m |
| 2026-05-28 | VSV725 | ALA → UKK | May 28, 09:55 UTC | May 28, 10:15 UTC | 20m |
| 2026-05-26 | VSV804 | DME → AKX | May 26, 11:09 UTC | May 26, 15:24 UTC | 4h 15m |
| 2026-05-26 | VSV803 | AKX → DME | May 26, 04:54 UTC | May 26, 09:29 UTC | 4h 35m |
| 2026-05-23 | VSV803 | AKX → DME | May 23, 05:30 UTC | May 23, 09:55 UTC | 4h 25m |
| 2026-05-22 | VSV803 | AKX → DME | May 22, 12:25 UTC | May 23, 09:55 UTC | 21h 29m |
| 2026-05-22 | VSV803 | AKX → DME | May 22, 11:15 UTC | May 23, 09:30 UTC | 22h 14m |
| 2026-05-22 | VSV822 | LED → NQZ | May 22, 09:45 UTC | May 22, 10:10 UTC | 25m |
| 2026-05-22 | VSV821 | NQZ → LED | May 22, 05:00 UTC | May 22, 06:00 UTC | 1h 0m |
| 2026-05-21 | VSV821 | NQZ → LED | May 21, 06:20 UTC | May 22, 05:30 UTC | 23h 10m |
| 2026-05-18 | VSV732 | SCO → ALA | May 18, 06:10 UTC | May 18, 22:45 UTC | 16h 34m |
| 2026-05-17 | VSV730D | - | May 17, 21:15 UTC | May 18, 04:25 UTC | 7h 10m |
| 2026-05-17 | VSV731 | ALA → SCO | May 17, 19:01 UTC | May 17, 19:20 UTC | 20m |
| 2026-05-17 | VSV731 | ALA → SCO | May 17, 14:35 UTC | May 17, 15:20 UTC | 45m |
| 2026-05-16 | VSV732 | SCO → ALA | May 16, 01:05 UTC | May 16, 01:20 UTC | 15m |
| 2026-05-15 | VSV730 | ALA → SCO | May 15, 22:30 UTC | May 15, 22:40 UTC | 10m |
| 2026-05-08 | VSV822 | LED → NQZ | May 8, 09:54 UTC | May 8, 10:14 UTC | 20m |
| 2026-05-05 | VSV725 | ALA → UKK | May 5, 09:50 UTC | May 5, 10:20 UTC | 30m |
| 2026-04-29 | VSV822 | LED → NQZ | Apr 29, 09:50 UTC | Apr 29, 10:05 UTC | 15m |
| 2026-04-28 | VSV804 | DME → AKX | Apr 28, 11:35 UTC | Apr 29, 06:39 UTC | 19h 5m |
| 2026-04-28 | VSV804 | DME → AKX | Apr 28, 10:55 UTC | Apr 29, 06:39 UTC | 19h 45m |
| 2026-04-28 | VSV803 | AKX → DME | Apr 28, 05:45 UTC | Apr 28, 09:25 UTC | 3h 40m |
| 2026-04-27 | VSV803 | AKX → DME | Apr 27, 12:00 UTC | Apr 28, 09:25 UTC | 21h 25m |
| 2026-04-26 | VSV813 | ALA → TAS | Apr 26, 18:00 UTC | Apr 27, 10:05 UTC | 16h 5m |
| 2026-04-26 | VSV813 | ALA → TAS | Apr 26, 01:15 UTC | Apr 26, 18:40 UTC | 17h 25m |
| 2026-04-25 | VSV784 | UKK → NQZ | Apr 25, 12:05 UTC | Apr 26, 01:15 UTC | 13h 10m |
| 2026-04-24 | VSV813 | ALA → TAS | Apr 24, 17:50 UTC | Apr 25, 10:25 UTC | 16h 35m |
| 2026-04-24 | VSV813 | ALA → TAS | Apr 24, 06:40 UTC | Apr 24, 18:20 UTC | 11h 40m |
| 2026-04-23 | VSV822 | LED → NQZ | Apr 23, 10:05 UTC | Apr 24, 06:45 UTC | 20h 40m |
| 2026-04-22 | VSV818 | DXB → NQZ | Apr 22, 20:55 UTC | Apr 23, 10:10 UTC | 13h 15m |
| 2026-04-22 | VSV817 | NQZ → DXB | Apr 22, 17:00 UTC | Apr 22, 19:35 UTC | 2h 35m |
| 2026-04-21 | VSV804 | DME → AKX | Apr 21, 11:05 UTC | Apr 21, 12:50 UTC | 1h 45m |
| 2026-04-21 | VSV803 | AKX → DME | Apr 21, 05:40 UTC | Apr 21, 08:45 UTC | 3h 5m |
| 2026-04-20 | VSV803 | AKX → DME | Apr 20, 09:55 UTC | Apr 21, 08:45 UTC | 22h 50m |
| 2026-04-17 | VSV822 | LED → NQZ | Apr 17, 09:40 UTC | Apr 17, 09:55 UTC | 15m |
| 2026-04-17 | VSV703 | ALA → NQZ | Apr 17, 05:50 UTC | Apr 17, 06:50 UTC | 1h 0m |
| 2026-04-14 | VSV804 | DME → AKX | Apr 14, 11:10 UTC | Apr 14, 12:45 UTC | 1h 35m |
| 2026-04-14 | VSV803 | AKX → DME | Apr 14, 05:30 UTC | Apr 14, 06:00 UTC | 30m |
| 2026-04-13 | VSV818 | - | Apr 13, 03:55 UTC | Apr 13, 04:10 UTC | 15m |
| 2026-04-13 | VSV818 | - | Apr 13, 02:00 UTC | Apr 13, 04:10 UTC | 2h 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-B3730 page for operator, model, and routing details .