sensors Mode-S transponder
683274
ICAO 24-bit transponder address · allocated to Kazakhstan
Currently assigned to UP-B3727 · BOEING 737 MAX 9
- Hex
- 683274
- Octal
- 32031164
- Decimal
- 6,828,660
- Country
- KZ
- Tail
- UP-B3727
- Type
- B39M
- Flights observed
- 69
- Distinct callsigns
- 20
- Country
- KZ
- Last broadcast
- 3h ago
Last known position
Country allocation
The ICAO 24-bit address 683274 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 |
|---|---|---|---|
| VSV5316 | - | 9 | 2026-05-04 |
| VSV5271 | - | 7 | 2026-05-18 |
| VSV5317 | - | 6 | 2026-04-24 |
| VSV5272 | - | 5 | 2026-05-18 |
| VSV5219 | - | 4 | 2026-05-14 |
| VSV5380 | Scat Air | 3 | 2026-06-01 |
| VSV5339 | - | 3 | 2026-04-15 |
| VSV5338 | - | 3 | 2026-04-15 |
| VSV5321 | Scat Air | 3 | 2026-04-29 |
| VSV5320 | - | 3 | 2026-04-27 |
| VSV5307 | - | 3 | 2026-04-28 |
| VSV5220 | - | 3 | 2026-05-15 |
| VSV5381 | - | 2 | 2026-06-02 |
| VSV5306 | - | 2 | 2026-04-28 |
| VSV5217 | - | 2 | 2026-05-11 |
| VSV481 | Scat Air | 2 | 2026-05-30 |
| VSV784 | Scat Air | 1 | 2026-05-26 |
| VSV729 | Scat Air | 1 | 2026-05-09 |
| VSV725 | Scat Air | 1 | 2026-05-26 |
| VSV5396 | - | 1 | 2026-05-19 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | VSV5381 | - | Jun 2, 02:10 UTC | Jun 2, 23:20 UTC | 21h 10m |
| 2026-06-01 | VSV5380 | ALA → DOH | Jun 1, 10:40 UTC | Jun 2, 09:00 UTC | 22h 20m |
| 2026-06-01 | VSV5380 | ALA → DOH | Jun 1, 04:05 UTC | Jun 2, 02:40 UTC | 22h 35m |
| 2026-05-31 | VSV482 | PRG → FRU | May 31, 16:10 UTC | Jun 1, 10:45 UTC | 18h 35m |
| 2026-05-30 | VSV481 | FRU → PRG | May 30, 21:00 UTC | May 31, 14:00 UTC | 17h 0m |
| 2026-05-30 | VSV481 | FRU → PRG | May 30, 16:05 UTC | May 31, 14:00 UTC | 21h 55m |
| 2026-05-30 | VSV5381 | - | May 30, 05:05 UTC | May 31, 00:55 UTC | 19h 50m |
| 2026-05-30 | VSV5380 | ALA → DOH | May 30, 03:05 UTC | May 31, 00:55 UTC | 21h 50m |
| 2026-05-27 | VSV5350 | - | May 27, 21:05 UTC | May 27, 21:30 UTC | 25m |
| 2026-05-26 | VSV784 | UKK → NQZ | May 26, 14:09 UTC | May 26, 14:35 UTC | 25m |
| 2026-05-26 | VSV725 | ALA → UKK | May 26, 12:30 UTC | May 26, 12:54 UTC | 25m |
| 2026-05-24 | VSV5342 | - | May 24, 20:55 UTC | May 24, 21:20 UTC | 25m |
| 2026-05-19 | VSV5396 | - | May 19, 22:00 UTC | May 20, 08:45 UTC | 10h 46m |
| 2026-05-18 | VSV5272 | - | May 18, 11:15 UTC | May 18, 12:15 UTC | 1h 0m |
| 2026-05-18 | VSV5271 | - | May 18, 08:30 UTC | May 18, 08:45 UTC | 15m |
| 2026-05-18 | VSV5271 | - | May 18, 06:35 UTC | May 18, 07:30 UTC | 55m |
| 2026-05-15 | VSV5220 | - | May 15, 09:20 UTC | May 15, 11:20 UTC | 2h 0m |
| 2026-05-15 | VSV5271 | - | May 15, 07:30 UTC | May 15, 07:50 UTC | 20m |
| 2026-05-14 | VSV5272 | - | May 14, 12:25 UTC | May 15, 06:40 UTC | 18h 15m |
| 2026-05-14 | VSV5219 | - | May 14, 08:30 UTC | May 14, 10:55 UTC | 2h 25m |
| 2026-05-12 | VSV5218 | - | May 12, 09:25 UTC | May 12, 11:20 UTC | 1h 55m |
| 2026-05-12 | VSV5271 | - | May 12, 07:20 UTC | May 12, 07:45 UTC | 25m |
| 2026-05-11 | VSV5271 | - | May 11, 13:50 UTC | May 12, 06:35 UTC | 16h 46m |
| 2026-05-11 | VSV5272 | - | May 11, 12:55 UTC | May 11, 13:10 UTC | 15m |
| 2026-05-11 | VSV5217 | - | May 11, 10:55 UTC | May 11, 11:10 UTC | 15m |
| 2026-05-11 | VSV5217 | - | May 11, 08:55 UTC | May 11, 10:05 UTC | 1h 10m |
| 2026-05-09 | VSV729 | SCO → ALA | May 9, 15:45 UTC | May 9, 15:55 UTC | 10m |
| 2026-05-08 | VSV5220 | - | May 8, 09:49 UTC | May 8, 11:49 UTC | 2h 0m |
| 2026-05-08 | VSV5271 | - | May 8, 07:59 UTC | May 8, 08:29 UTC | 30m |
| 2026-05-07 | VSV5271 | - | May 7, 13:25 UTC | May 8, 07:14 UTC | 17h 49m |
| 2026-05-07 | VSV5272 | - | May 7, 12:25 UTC | May 8, 07:14 UTC | 18h 50m |
| 2026-05-07 | VSV5219 | - | May 7, 10:30 UTC | May 7, 10:50 UTC | 20m |
| 2026-05-07 | VSV5219 | - | May 7, 08:30 UTC | May 7, 09:50 UTC | 1h 20m |
| 2026-05-04 | VSV5316 | - | May 4, 22:15 UTC | May 5, 06:50 UTC | 8h 35m |
| 2026-05-01 | VSV5220 | - | May 1, 09:20 UTC | May 1, 11:15 UTC | 1h 55m |
| 2026-04-30 | VSV5272 | - | Apr 30, 12:05 UTC | May 1, 06:55 UTC | 18h 50m |
| 2026-04-29 | VSV5219 | - | Apr 29, 15:05 UTC | Apr 30, 09:45 UTC | 18h 39m |
| 2026-04-29 | VSV5321 | ALA → ALA | Apr 29, 13:05 UTC | Apr 30, 09:45 UTC | 20h 39m |
| 2026-04-29 | VSV5321 | ALA → ALA | Apr 29, 11:05 UTC | Apr 30, 09:45 UTC | 22h 39m |
| 2026-04-29 | VSV5321 | ALA → ALA | Apr 29, 10:50 UTC | Apr 30, 09:00 UTC | 22h 9m |
| 2026-04-28 | VSV5307 | - | Apr 28, 21:05 UTC | Apr 29, 15:30 UTC | 18h 26m |
| 2026-04-28 | VSV5307 | - | Apr 28, 15:05 UTC | Apr 29, 15:00 UTC | 23h 55m |
| 2026-04-28 | VSV5307 | - | Apr 28, 14:50 UTC | Apr 29, 13:00 UTC | 22h 11m |
| 2026-04-28 | VSV5306 | - | Apr 28, 05:05 UTC | Apr 29, 05:00 UTC | 23h 55m |
| 2026-04-28 | VSV5306 | - | Apr 28, 04:25 UTC | Apr 28, 22:00 UTC | 17h 35m |
| 2026-04-27 | VSV5320 | - | Apr 27, 21:20 UTC | Apr 28, 01:40 UTC | 4h 20m |
| 2026-04-27 | VSV5320 | - | Apr 27, 05:35 UTC | Apr 28, 01:40 UTC | 20h 5m |
| 2026-04-27 | VSV5320 | - | Apr 27, 01:10 UTC | Apr 28, 01:05 UTC | 23h 55m |
| 2026-04-26 | VSV5316 | - | Apr 26, 23:05 UTC | Apr 27, 23:00 UTC | 23h 55m |
| 2026-04-26 | VSV5316 | - | Apr 26, 22:20 UTC | Apr 27, 06:20 UTC | 8h 0m |
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-B3727 page for operator, model, and routing details .