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
- 142
- Distinct callsigns
- 20
- Country
- KZ
- Last broadcast
- 16h 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 |
|---|---|---|---|
| VSV5380 | - | 10 | 2026-06-26 |
| VSV5381 | - | 9 | 2026-06-30 |
| VSV5316 | - | 9 | 2026-05-04 |
| VSV5271 | - | 9 | 2026-07-12 |
| VSV481 | - | 8 | 2026-06-25 |
| VSV5272 | - | 7 | 2026-07-13 |
| VSV5270 | - | 7 | 2026-07-09 |
| VSV5317 | - | 6 | 2026-04-24 |
| VSV482 | - | 6 | 2026-06-25 |
| VSV5273 | - | 5 | 2026-06-27 |
| VSV479 | Scat Air | 5 | 2026-06-24 |
| VSV5275 | - | 4 | 2026-07-16 |
| VSV5219 | - | 4 | 2026-05-14 |
| 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 |
| VSV5282 | - | 3 | 2026-06-22 |
| VSV5268 | - | 3 | 2026-06-27 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | VSV5276 | - | Jul 17, 12:40 UTC | Jul 17, 14:30 UTC | 1h 50m |
| 2026-07-17 | VSV5281 | AYT → AKX | Jul 17, 01:29 UTC | Jul 17, 10:55 UTC | 9h 25m |
| 2026-07-16 | VSV5275 | - | Jul 16, 11:34 UTC | Jul 16, 23:35 UTC | 12h 0m |
| 2026-07-15 | VSV5370 | - | Jul 15, 15:20 UTC | Jul 16, 10:04 UTC | 18h 45m |
| 2026-07-15 | VSV5288 | - | Jul 15, 03:40 UTC | Jul 15, 12:50 UTC | 9h 10m |
| 2026-07-14 | VSV5369 | - | Jul 14, 22:35 UTC | Jul 15, 00:55 UTC | 2h 19m |
| 2026-07-13 | VSV5272 | - | Jul 13, 10:20 UTC | Jul 13, 12:10 UTC | 1h 50m |
| 2026-07-12 | VSV5271 | - | Jul 12, 22:10 UTC | Jul 13, 08:55 UTC | 10h 45m |
| 2026-07-12 | VSV725 | - | Jul 12, 20:05 UTC | Jul 12, 20:30 UTC | 25m |
| 2026-07-09 | VSV5270 | - | Jul 9, 11:05 UTC | Jul 10, 06:45 UTC | 19h 40m |
| 2026-07-09 | VSV5270 | - | Jul 9, 09:30 UTC | Jul 10, 06:45 UTC | 21h 15m |
| 2026-07-08 | VSV5269 | - | Jul 8, 16:30 UTC | Jul 9, 06:20 UTC | 13h 50m |
| 2026-07-08 | VSV5287 | - | Jul 8, 03:35 UTC | Jul 8, 14:15 UTC | 10h 40m |
| 2026-07-07 | VSV5369 | - | Jul 7, 22:50 UTC | Jul 8, 01:15 UTC | 2h 25m |
| 2026-07-06 | VSV5272 | - | Jul 6, 09:50 UTC | Jul 6, 11:35 UTC | 1h 45m |
| 2026-07-06 | VSV5271 | - | Jul 6, 05:55 UTC | Jul 6, 08:20 UTC | 2h 25m |
| 2026-07-02 | VSV5270 | - | Jul 2, 11:05 UTC | Jul 3, 06:10 UTC | 19h 5m |
| 2026-07-02 | VSV5270 | - | Jul 2, 09:10 UTC | Jul 3, 06:10 UTC | 21h 0m |
| 2026-07-02 | VSV5269 | - | Jul 2, 03:35 UTC | Jul 2, 06:25 UTC | 2h 50m |
| 2026-06-30 | VSV5381 | - | Jun 30, 09:05 UTC | Jul 1, 04:10 UTC | 19h 5m |
| 2026-06-30 | VSV5381 | - | Jun 30, 07:30 UTC | Jul 1, 04:10 UTC | 20h 40m |
| 2026-06-29 | VSV5240 | - | Jun 29, 14:39 UTC | Jun 30, 03:40 UTC | 13h 1m |
| 2026-06-29 | VSV5240 | - | Jun 29, 07:05 UTC | Jun 30, 03:40 UTC | 20h 36m |
| 2026-06-29 | VSV5240 | - | Jun 29, 05:34 UTC | Jun 30, 03:40 UTC | 22h 6m |
| 2026-06-28 | VSV5291 | - | Jun 28, 09:30 UTC | Jun 29, 03:05 UTC | 17h 35m |
| 2026-06-27 | VSV5268 | - | Jun 27, 20:44 UTC | Jun 28, 08:00 UTC | 11h 15m |
| 2026-06-27 | VSV5273 | - | Jun 27, 07:39 UTC | Jun 27, 19:15 UTC | 11h 35m |
| 2026-06-27 | VSV5381 | - | Jun 27, 06:50 UTC | Jun 27, 07:34 UTC | 45m |
| 2026-06-26 | VSV5380 | - | Jun 26, 10:35 UTC | Jun 27, 04:59 UTC | 18h 25m |
| 2026-06-25 | VSV482 | - | Jun 25, 16:05 UTC | Jun 26, 10:39 UTC | 18h 35m |
| 2026-06-25 | VSV481 | - | Jun 25, 00:55 UTC | Jun 25, 14:14 UTC | 13h 20m |
| 2026-06-24 | VSV479 | NQZ → SYX | Jun 24, 03:44 UTC | Jun 24, 20:05 UTC | 16h 20m |
| 2026-06-23 | VSV479 | NQZ → SYX | Jun 23, 23:10 UTC | Jun 24, 20:05 UTC | 20h 55m |
| 2026-06-23 | VSV5382 | - | Jun 23, 17:39 UTC | Jun 24, 15:14 UTC | 21h 35m |
| 2026-06-23 | VSV5270 | - | Jun 23, 09:34 UTC | Jun 24, 03:44 UTC | 18h 10m |
| 2026-06-23 | VSV5270 | - | Jun 23, 02:09 UTC | Jun 23, 23:14 UTC | 21h 5m |
| 2026-06-22 | VSV5270 | - | Jun 22, 13:10 UTC | Jun 23, 12:40 UTC | 23h 30m |
| 2026-06-22 | VSV5282 | - | Jun 22, 02:10 UTC | Jun 22, 11:19 UTC | 9h 10m |
| 2026-06-21 | VSV5275 | - | Jun 21, 09:20 UTC | Jun 22, 00:29 UTC | 15h 10m |
| 2026-06-20 | VSV5268 | - | Jun 20, 18:14 UTC | Jun 21, 05:15 UTC | 11h 0m |
| 2026-06-19 | VSV5273 | - | Jun 19, 15:04 UTC | Jun 20, 11:25 UTC | 20h 20m |
| 2026-06-19 | VSV5273 | - | Jun 19, 13:20 UTC | Jun 20, 11:25 UTC | 22h 5m |
| 2026-06-19 | VSV5282 | - | Jun 19, 10:39 UTC | Jun 19, 11:04 UTC | 25m |
| 2026-06-19 | VSV5282 | - | Jun 19, 01:34 UTC | Jun 19, 09:59 UTC | 8h 25m |
| 2026-06-18 | VSV5275 | - | Jun 18, 20:55 UTC | Jun 18, 23:10 UTC | 2h 15m |
| 2026-06-18 | VSV5275 | - | Jun 18, 01:55 UTC | Jun 18, 23:10 UTC | 21h 15m |
| 2026-06-17 | VSV5276 | - | Jun 17, 09:05 UTC | Jun 18, 02:00 UTC | 16h 55m |
| 2026-06-16 | VSV5268 | - | Jun 16, 18:05 UTC | Jun 17, 05:10 UTC | 11h 6m |
| 2026-06-16 | VSV5273 | - | Jun 16, 15:09 UTC | Jun 16, 15:35 UTC | 25m |
| 2026-06-15 | VSV5273 | - | Jun 15, 21:50 UTC | Jun 16, 14:30 UTC | 16h 40m |
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 .