sensors Mode-S transponder

683298

ICAO 24-bit transponder address · allocated to Kazakhstan

Currently assigned to UP-B3732 · BOEING 737-800

Hex
683298
Octal
32031230
Decimal
6,828,696
Country
KZ
Tail
UP-B3732
Type
B738
No current signal · last broadcast 2d ago
Flights observed
66
Distinct callsigns
15
Country
KZ
Last broadcast
2d ago

Last known position

Most recent position reported by Mode-S 683298.

Country allocation

The ICAO 24-bit address 683298 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
VSV726 - 15 2026-07-16
VSV725 - 15 2026-07-16
VSV784 - 8 2026-07-06
VSV813 Scat Air 7 2026-06-07
VSV783 - 5 2026-07-06
VSV814 Scat Air 4 2026-06-08
VSV804 - 3 2026-07-11
VSV803 Scat Air 2 2026-04-25
VSV821 Scat Air 1 2026-06-03
VSV818 Scat Air 1 2026-05-27
VSV817 Scat Air 1 2026-05-27
VSV809 Scat Air 1 2026-05-18
VSV808 Scat Air 1 2026-04-15
VSV799 - 1 2026-07-10
VRV810 - 1 2026-05-19

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-16 VSV726 - Jul 16, 16:19 UTCJul 16, 16:44 UTC25m
2026-07-16 VSV725 - Jul 16, 14:35 UTCJul 16, 14:55 UTC20m
2026-07-13 VSV726 - Jul 13, 16:10 UTCJul 13, 16:40 UTC30m
2026-07-13 VSV725 - Jul 13, 14:35 UTCJul 13, 15:00 UTC25m
2026-07-11 VSV804 - Jul 11, 12:05 UTCJul 11, 14:05 UTC2h 0m
2026-07-10 VSV799 - Jul 10, 17:55 UTCJul 11, 00:25 UTC6h 30m
2026-07-07 VSV726 - Jul 7, 16:10 UTCJul 7, 16:30 UTC20m
2026-07-07 VSV725 - Jul 7, 14:25 UTCJul 7, 14:50 UTC25m
2026-07-06 VSV784 - Jul 6, 14:30 UTCJul 6, 14:55 UTC25m
2026-07-06 VSV783 - Jul 6, 12:50 UTCJul 6, 13:10 UTC20m
2026-06-28 VSV726 - Jun 28, 16:25 UTCJun 28, 16:49 UTC25m
2026-06-28 VSV725 - Jun 28, 14:45 UTCJun 28, 15:09 UTC25m
2026-06-25 VSV726 - Jun 25, 17:05 UTCJun 25, 17:20 UTC15m
2026-06-25 VSV725 - Jun 25, 15:24 UTCJun 25, 15:50 UTC25m
2026-06-22 VSV726 - Jun 22, 16:20 UTCJun 22, 16:34 UTC15m
2026-06-22 VSV725 - Jun 22, 14:40 UTCJun 22, 14:59 UTC20m
2026-06-21 VSV726 - Jun 21, 16:19 UTCJun 21, 16:44 UTC25m
2026-06-21 VSV725 - Jun 21, 14:40 UTCJun 21, 14:59 UTC20m
2026-06-18 VSV726 - Jun 18, 18:30 UTCJun 18, 18:45 UTC15m
2026-06-18 VSV725 - Jun 18, 16:40 UTCJun 18, 17:05 UTC25m
2026-06-15 VSV726 UKK → ALA Jun 15, 16:24 UTCJun 15, 16:45 UTC20m
2026-06-15 VSV725 - Jun 15, 14:40 UTCJun 15, 15:04 UTC25m
2026-06-11 VSV726 UKK → ALA Jun 11, 16:30 UTCJun 11, 17:00 UTC30m
2026-06-11 VSV725 ALA → UKK Jun 11, 14:35 UTCJun 11, 15:00 UTC25m
2026-06-10 VSV726 UKK → ALA Jun 10, 16:30 UTCJun 11, 15:00 UTC22h 30m
2026-06-10 VSV725 ALA → UKK Jun 10, 14:50 UTCJun 10, 15:15 UTC25m
2026-06-09 VSV784 UKK → NQZ Jun 9, 07:25 UTCJun 9, 07:55 UTC30m
2026-06-08 VSV814 TAS → ALA Jun 8, 21:10 UTCJun 9, 05:55 UTC8h 45m
2026-06-08 VSV814 TAS → ALA Jun 8, 08:05 UTCJun 9, 05:55 UTC21h 50m
2026-06-08 VSV784 UKK → NQZ Jun 8, 07:40 UTCJun 9, 05:55 UTC22h 15m
2026-06-07 VSV813 ALA → TAS Jun 7, 18:00 UTCJun 8, 05:55 UTC11h 55m
2026-06-07 VSV813 ALA → TAS Jun 7, 08:05 UTCJun 8, 05:55 UTC21h 50m
2026-06-07 VSV784 UKK → NQZ Jun 7, 07:45 UTCJun 8, 05:55 UTC22h 10m
2026-06-07 VSV783 NQZ → UKK Jun 7, 05:35 UTCJun 7, 05:50 UTC15m
2026-06-06 VSV813 ALA → TAS Jun 6, 07:50 UTCJun 6, 18:25 UTC10h 35m
2026-06-05 VSV783 NQZ → UKK Jun 5, 19:25 UTCJun 6, 06:25 UTC11h 0m
2026-06-05 VSV783 NQZ → UKK Jun 5, 08:05 UTCJun 6, 06:25 UTC22h 20m
2026-06-05 VSV784 UKK → NQZ Jun 5, 07:35 UTCJun 6, 01:55 UTC18h 20m
2026-06-04 VSV813 ALA → TAS Jun 4, 18:00 UTCJun 5, 06:05 UTC12h 5m
2026-06-04 VSV784 UKK → NQZ Jun 4, 07:25 UTCJun 5, 06:00 UTC22h 35m
2026-06-03 VSV783 NQZ → UKK Jun 3, 11:00 UTCJun 4, 06:00 UTC19h 0m
2026-06-03 VSV821 NQZ → LED Jun 3, 06:10 UTCJun 4, 06:00 UTC23h 50m
2026-06-02 VSV813 ALA → TAS Jun 2, 18:35 UTCJun 2, 20:10 UTC1h 35m
2026-06-01 VSV726 UKK → ALA Jun 1, 16:45 UTCJun 1, 17:15 UTC30m
2026-06-01 VSV725 ALA → UKK Jun 1, 15:00 UTCJun 1, 15:25 UTC25m
2026-05-27 VSV818 DXB → NQZ May 27, 20:35 UTCMay 28, 10:00 UTC13h 25m
2026-05-27 VSV817 NQZ → DXB May 27, 14:45 UTCMay 27, 19:20 UTC4h 35m
2026-05-26 VSV726 UKK → ALA May 26, 04:15 UTCMay 26, 04:39 UTC25m
2026-05-25 VSV814 TAS → ALA May 25, 12:05 UTCMay 26, 02:39 UTC14h 35m
2026-05-25 VSV725 ALA → UKK May 25, 04:05 UTCMay 25, 10:20 UTC6h 15m

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-B3732 page for operator, model, and routing details .

Mode-S 683298 frequently asked

What is Mode-S code 683298?
683298 is an ICAO 24-bit transponder address. Allocated to Kazakhstan. Assigned to UP-B3732.
Where is Mode-S 683298 registered?
Mode-S code 683298 is allocated to Kazakhstan (KZ). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 683298 broadcasting right now?
No active broadcast right now. Last signal was 2d ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 683298, octal 32031230, decimal 6,828,696.
What flights does 683298 operate?
Mode-S 683298 has broadcast 15 distinct callsigns, including VSV726, VSV725, VSV784, VSV813, VSV783.