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