sensors Mode-S transponder

683273

ICAO 24-bit transponder address · allocated to Kazakhstan

Currently assigned to UP-B3726 · BOEING 737 MAX 9

Hex
683273
Octal
32031163
Decimal
6,828,659
Country
KZ
Tail
UP-B3726
Type
B39M
Broadcasting now · callsign VSV5263 · 32,000 ft
Flights observed
255
Distinct callsigns
20
Country
KZ
Last broadcast
14h ago

Current position

683273 is currently broadcasting. Map zoomed to live position.

Country allocation

The ICAO 24-bit address 683273 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 20 distinct

Callsign Airline Flights Last seen
VSV5240 - 66 2026-07-13
VSV5241 - 37 2026-06-18
VSV5266 - 25 2026-07-10
VSV5291 - 14 2026-06-21
VSV5265 - 14 2026-06-19
VSV5263 - 14 2026-07-07
VSV5264 - 12 2026-07-12
VSV5262 - 11 2026-07-04
VSV5200 - 8 2026-07-11
VSV5269 - 7 2026-06-16
VSV5261 - 7 2026-06-13
VSV5321 Scat Air 6 2026-04-19
VSV5304 - 5 2026-04-18
VSV5292 - 5 2026-06-14
VSV5275 - 3 2026-07-02
VSV5272 - 3 2026-06-29
VSV5212 Scat Air 3 2026-05-09
VSV5273 - 2 2026-07-01
VSV5271 - 2 2026-06-28
VSV726 Scat Air 1 2026-04-13

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-13 VSV5240 - Jul 13, 14:15 UTCJul 14, 03:25 UTC13h 10m
2026-07-13 VSV5240 - Jul 13, 06:50 UTCJul 14, 03:25 UTC20h 35m
2026-07-13 VSV5240 - Jul 13, 04:50 UTCJul 14, 03:25 UTC22h 35m
2026-07-12 VSV5264 - Jul 12, 13:05 UTCJul 12, 23:35 UTC10h 30m
2026-07-11 VSV5200 - Jul 11, 21:25 UTCJul 12, 07:31 UTC10h 5m
2026-07-10 VSV5266 - Jul 10, 17:55 UTCJul 11, 05:35 UTC11h 40m
2026-07-09 VSV5240 - Jul 9, 14:00 UTCJul 10, 04:00 UTC14h 0m
2026-07-09 VSV5240 - Jul 9, 06:50 UTCJul 10, 04:00 UTC21h 10m
2026-07-09 VSV5240 - Jul 9, 04:55 UTCJul 10, 04:00 UTC23h 5m
2026-07-08 VSV5266 - Jul 8, 14:45 UTCJul 9, 02:50 UTC12h 5m
2026-07-07 VSV5263 - Jul 7, 17:40 UTCJul 8, 04:55 UTC11h 15m
2026-07-06 VSV5240 - Jul 6, 13:45 UTCJul 7, 03:40 UTC13h 55m
2026-07-06 VSV5240 - Jul 6, 06:50 UTCJul 7, 03:40 UTC20h 50m
2026-07-06 VSV5240 - Jul 6, 04:50 UTCJul 7, 03:40 UTC22h 50m
2026-07-05 VSV5264 - Jul 5, 12:45 UTCJul 6, 00:15 UTC11h 30m
2026-07-04 VSV5262 - Jul 4, 21:25 UTCJul 5, 10:00 UTC12h 35m
2026-07-03 VSV5380 - Jul 3, 12:30 UTCJul 4, 04:35 UTC16h 5m
2026-07-03 VSV5282 - Jul 3, 01:15 UTCJul 3, 10:40 UTC9h 25m
2026-07-02 VSV5275 - Jul 2, 11:30 UTCJul 2, 23:05 UTC11h 35m
2026-07-01 VSV5273 - Jul 1, 16:15 UTCJul 2, 09:40 UTC17h 25m
2026-07-01 VSV5288 - Jul 1, 03:40 UTCJul 1, 13:15 UTC9h 35m
2026-06-30 VSV5369 - Jun 30, 22:25 UTCJun 30, 23:45 UTC1h 20m
2026-06-29 VSV5272 - Jun 29, 09:40 UTCJun 29, 11:25 UTC1h 45m
2026-06-28 VSV5271 - Jun 28, 13:10 UTCJun 29, 08:14 UTC19h 5m
2026-06-27 VSV5266 - Jun 27, 17:44 UTCJun 28, 06:40 UTC12h 55m
2026-06-26 VSV5266 - Jun 26, 17:50 UTCJun 27, 05:44 UTC11h 55m
2026-06-25 VSV5240 - Jun 25, 14:14 UTCJun 26, 04:00 UTC13h 45m
2026-06-25 VSV5240 - Jun 25, 06:50 UTCJun 26, 04:00 UTC21h 10m
2026-06-25 VSV5240 - Jun 25, 06:14 UTCJun 26, 04:00 UTC21h 45m
2026-06-24 VSV5262 - Jun 24, 15:05 UTCJun 25, 03:54 UTC12h 50m
2026-06-23 VSV5263 - Jun 23, 20:24 UTCJun 24, 12:44 UTC16h 20m
2026-06-23 VSV5263 - Jun 23, 08:50 UTCJun 24, 05:34 UTC20h 45m
2026-06-23 VSV5263 - Jun 23, 07:35 UTCJun 24, 05:34 UTC22h 0m
2026-06-22 VSV5240 - Jun 22, 17:40 UTCJun 23, 04:50 UTC11h 10m
2026-06-21 VSV5291 - Jun 21, 12:35 UTCJun 22, 03:40 UTC15h 5m
2026-06-20 VSV5200 SSH → SSH Jun 20, 21:19 UTCJun 20, 23:55 UTC2h 35m
2026-06-19 VSV5265 - Jun 19, 17:49 UTCJun 20, 04:44 UTC10h 55m
2026-06-18 VSV5240 - Jun 18, 18:15 UTCJun 19, 12:14 UTC17h 59m
2026-06-18 VSV5241 - Jun 18, 10:50 UTCJun 19, 10:44 UTC23h 54m
2026-06-18 VSV5241 - Jun 18, 09:25 UTCJun 19, 00:14 UTC14h 49m
2026-06-17 VSV5266 - Jun 17, 18:35 UTCJun 18, 07:00 UTC12h 25m
2026-06-16 VSV5264 - Jun 16, 22:55 UTCJun 17, 16:20 UTC17h 25m
2026-06-16 VSV5269 - Jun 16, 14:50 UTCJun 17, 14:15 UTC23h 26m
2026-06-16 VSV5269 - Jun 16, 12:50 UTCJun 17, 08:00 UTC19h 11m
2026-06-15 VSV5240 - Jun 15, 18:50 UTCJun 16, 09:15 UTC14h 25m
2026-06-15 VSV5240 - Jun 15, 12:55 UTCJun 16, 09:15 UTC20h 20m
2026-06-15 VSV5240 - Jun 15, 10:50 UTCJun 16, 09:15 UTC22h 25m
2026-06-15 VSV5241 - Jun 15, 10:30 UTCJun 16, 08:44 UTC22h 15m
2026-06-15 VSV5241 - Jun 15, 07:10 UTCJun 16, 06:40 UTC23h 30m
2026-06-15 VSV5241 - Jun 15, 05:30 UTCJun 16, 00:15 UTC18h 45m

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

Mode-S 683273 frequently asked

What is Mode-S code 683273?
683273 is an ICAO 24-bit transponder address. Allocated to Kazakhstan. Assigned to UP-B3726.
Where is Mode-S 683273 registered?
Mode-S code 683273 is allocated to Kazakhstan (KZ). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 683273 broadcasting right now?
Yes. Mode-S 683273 is currently airborne.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 683273, octal 32031163, decimal 6,828,659.
What flights does 683273 operate?
Mode-S 683273 has broadcast 20 distinct callsigns, including VSV5240, VSV5241, VSV5266, VSV5291, VSV5265.