sensors Mode-S transponder
683297
ICAO 24-bit transponder address · allocated to Kazakhstan
Currently assigned to UP-B3731 · BOEING 737-800
- Hex
- 683297
- Octal
- 32031227
- Decimal
- 6,828,695
- Country
- KZ
- Tail
- UP-B3731
- Type
- B738
- Flights observed
- 143
- Distinct callsigns
- 15
- Country
- KZ
- Last broadcast
- 3h ago
Last known position
Country allocation
The ICAO 24-bit address 683297 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 15 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| VSV783 | - | 36 | 2026-07-13 |
| VSV784 | - | 34 | 2026-07-12 |
| VSV813 | Scat Air | 26 | 2026-07-01 |
| VSV725 | Scat Air | 21 | 2026-06-08 |
| VSV814 | Scat Air | 7 | 2026-05-19 |
| VSV726 | Scat Air | 6 | 2026-06-08 |
| VSV822 | Scat Air | 2 | 2026-06-14 |
| VSV821 | Scat Air | 2 | 2026-04-27 |
| VSV804 | - | 2 | 2026-07-14 |
| VSV803 | - | 2 | 2026-07-14 |
| VSV842 | Scat Air | 1 | 2026-04-21 |
| VSV841 | Scat Air | 1 | 2026-04-21 |
| VSV808 | Scat Air | 1 | 2026-05-24 |
| VSV807 | Scat Air | 1 | 2026-05-24 |
| VSV741 | Scat Air | 1 | 2026-05-11 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | VSV804 | - | Jul 14, 11:30 UTC | Jul 14, 13:15 UTC | 1h 45m |
| 2026-07-14 | VSV803 | - | Jul 14, 08:10 UTC | Jul 14, 09:25 UTC | 1h 15m |
| 2026-07-13 | VSV803 | - | Jul 13, 08:30 UTC | Jul 13, 16:55 UTC | 8h 25m |
| 2026-07-13 | VSV783 | - | Jul 13, 06:30 UTC | Jul 13, 06:55 UTC | 25m |
| 2026-07-12 | VSV784 | - | Jul 12, 07:20 UTC | Jul 12, 07:45 UTC | 25m |
| 2026-07-12 | VSV783 | - | Jul 12, 05:25 UTC | Jul 12, 05:50 UTC | 25m |
| 2026-07-11 | VSV784 | - | Jul 11, 08:05 UTC | Jul 12, 05:50 UTC | 21h 45m |
| 2026-07-11 | VSV783 | - | Jul 11, 06:15 UTC | Jul 11, 06:40 UTC | 25m |
| 2026-07-10 | VSV783 | - | Jul 10, 07:50 UTC | Jul 11, 06:40 UTC | 22h 50m |
| 2026-07-10 | VSV784 | - | Jul 10, 07:30 UTC | Jul 10, 07:50 UTC | 20m |
| 2026-07-10 | VSV783 | - | Jul 10, 05:35 UTC | Jul 10, 06:00 UTC | 25m |
| 2026-07-09 | VSV783 | - | Jul 9, 08:15 UTC | Jul 10, 06:00 UTC | 21h 45m |
| 2026-07-09 | VSV783 | - | Jul 9, 06:10 UTC | Jul 9, 06:35 UTC | 25m |
| 2026-07-08 | VSV783 | - | Jul 8, 07:50 UTC | Jul 9, 06:35 UTC | 22h 45m |
| 2026-07-08 | VSV784 | - | Jul 8, 07:30 UTC | Jul 8, 07:55 UTC | 25m |
| 2026-07-08 | VSV783 | - | Jul 8, 05:45 UTC | Jul 8, 06:10 UTC | 25m |
| 2026-07-07 | VSV783 | - | Jul 7, 07:50 UTC | Jul 8, 06:10 UTC | 22h 20m |
| 2026-07-07 | VSV783 | - | Jul 7, 05:55 UTC | Jul 7, 06:20 UTC | 25m |
| 2026-07-04 | VSV784 | - | Jul 4, 07:40 UTC | Jul 4, 08:00 UTC | 20m |
| 2026-07-04 | VSV783 | - | Jul 4, 05:50 UTC | Jul 4, 06:10 UTC | 20m |
| 2026-07-02 | VSV784 | - | Jul 2, 07:45 UTC | Jul 2, 08:10 UTC | 25m |
| 2026-07-02 | VSV783 | - | Jul 2, 06:00 UTC | Jul 2, 06:25 UTC | 25m |
| 2026-07-01 | VSV813 | ALA → TAS | Jul 1, 20:15 UTC | Jul 1, 20:35 UTC | 20m |
| 2026-06-30 | VSV783 | - | Jun 30, 07:50 UTC | Jun 30, 08:15 UTC | 25m |
| 2026-06-30 | VSV783 | - | Jun 30, 06:10 UTC | Jun 30, 06:30 UTC | 20m |
| 2026-06-29 | VSV813 | ALA → TAS | Jun 29, 19:05 UTC | Jun 29, 19:35 UTC | 30m |
| 2026-06-29 | VSV783 | - | Jun 29, 05:30 UTC | Jun 29, 05:54 UTC | 25m |
| 2026-06-27 | VSV784 | - | Jun 27, 07:34 UTC | Jun 27, 07:59 UTC | 25m |
| 2026-06-26 | VSV813 | ALA → TAS | Jun 26, 20:15 UTC | Jun 27, 06:05 UTC | 9h 50m |
| 2026-06-24 | VSV784 | - | Jun 24, 07:30 UTC | Jun 24, 07:50 UTC | 20m |
| 2026-06-24 | VSV783 | - | Jun 24, 05:40 UTC | Jun 24, 05:59 UTC | 20m |
| 2026-06-23 | VSV783 | - | Jun 23, 07:49 UTC | Jun 24, 05:59 UTC | 22h 10m |
| 2026-06-23 | VSV784 | - | Jun 23, 07:40 UTC | Jun 24, 05:44 UTC | 22h 5m |
| 2026-06-23 | VSV783 | - | Jun 23, 05:34 UTC | Jun 23, 05:59 UTC | 25m |
| 2026-06-22 | VSV784 | - | Jun 22, 07:49 UTC | Jun 22, 19:44 UTC | 11h 55m |
| 2026-06-22 | VSV783 | - | Jun 22, 06:00 UTC | Jun 22, 06:25 UTC | 25m |
| 2026-06-21 | VSV783 | - | Jun 21, 07:49 UTC | Jun 22, 06:25 UTC | 22h 35m |
| 2026-06-21 | VSV784 | - | Jun 21, 07:40 UTC | Jun 21, 08:04 UTC | 25m |
| 2026-06-21 | VSV783 | - | Jun 21, 05:40 UTC | Jun 21, 05:59 UTC | 20m |
| 2026-06-20 | VSV783 | - | Jun 20, 07:49 UTC | Jun 21, 05:59 UTC | 22h 10m |
| 2026-06-20 | VSV784 | - | Jun 20, 07:29 UTC | Jun 21, 05:44 UTC | 22h 15m |
| 2026-06-20 | VSV783 | - | Jun 20, 05:44 UTC | Jun 20, 06:05 UTC | 20m |
| 2026-06-19 | VSV783 | - | Jun 19, 07:49 UTC | Jun 20, 06:05 UTC | 22h 15m |
| 2026-06-19 | VSV784 | - | Jun 19, 07:34 UTC | Jun 20, 05:44 UTC | 22h 10m |
| 2026-06-18 | VSV784 | - | Jun 18, 07:35 UTC | Jun 18, 07:55 UTC | 20m |
| 2026-06-17 | VSV783 | - | Jun 17, 22:05 UTC | Jun 18, 05:55 UTC | 7h 50m |
| 2026-06-17 | VSV813 | ALA → TAS | Jun 17, 19:30 UTC | Jun 17, 19:55 UTC | 25m |
| 2026-06-16 | VSV813 | ALA → TAS | Jun 16, 19:00 UTC | Jun 16, 19:25 UTC | 25m |
| 2026-06-16 | VSV784 | - | Jun 16, 07:25 UTC | Jun 16, 07:50 UTC | 25m |
| 2026-06-16 | VSV783 | NQZ → UKK | Jun 16, 05:30 UTC | Jun 16, 05:55 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-B3731 page for operator, model, and routing details .