sensors Mode-S transponder
152069
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73833 · AIRBUS A-320
- Hex
- 152069
- Octal
- 05220151
- Decimal
- 1,384,553
- Country
- RU
- Tail
- RA-73833
- Type
- A320
- Flights observed
- 75
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 7h ago
Last known position
Country allocation
The ICAO 24-bit address 152069 falls within the block assigned to Russia (RU) by ICAO Annex 10, Volume III. Every aircraft registered in Russia 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 |
|---|---|---|---|
| SVR2317 | - | 9 | 2026-06-02 |
| SVR774 | Ural Airlines | 5 | 2026-05-21 |
| SVR2411 | Ural Airlines | 5 | 2026-05-19 |
| SVR2862 | Ural Airlines | 4 | 2026-05-30 |
| SVR2412 | Ural Airlines | 4 | 2026-05-17 |
| SVR2318 | - | 4 | 2026-06-01 |
| SVR7242 | Ural Airlines | 3 | 2026-05-04 |
| SVR2952 | Ural Airlines | 3 | 2026-05-16 |
| SVR2949 | Ural Airlines | 2 | 2026-05-03 |
| SVR2879 | Ural Airlines | 2 | 2026-05-27 |
| SVR2734 | Ural Airlines | 2 | 2026-05-26 |
| SVR2720 | Ural Airlines | 2 | 2026-04-23 |
| SVR2719 | Ural Airlines | 2 | 2026-04-23 |
| SVR262 | Ural Airlines | 2 | 2026-05-10 |
| SVR2104 | Ural Airlines | 2 | 2026-05-14 |
| SVR209 | Ural Airlines | 2 | 2026-04-24 |
| SVR106 | - | 2 | 2026-04-13 |
| SVR9310 | - | 1 | 2026-04-30 |
| SVR876 | Ural Airlines | 1 | 2026-05-23 |
| SVR773 | Ural Airlines | 1 | 2026-05-21 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | SVR2317 | - | Jun 2, 01:40 UTC | Jun 2, 19:25 UTC | 17h 45m |
| 2026-06-01 | SVR2317 | - | Jun 1, 22:20 UTC | Jun 2, 19:25 UTC | 21h 5m |
| 2026-06-01 | SVR2318 | - | Jun 1, 21:00 UTC | Jun 2, 19:25 UTC | 22h 25m |
| 2026-06-01 | SVR2318 | - | Jun 1, 10:55 UTC | Jun 2, 03:10 UTC | 16h 15m |
| 2026-05-30 | SVR2862 | SKD → SVX | May 30, 00:20 UTC | May 30, 00:35 UTC | 15m |
| 2026-05-29 | SVR2862 | SKD → SVX | May 29, 03:10 UTC | May 30, 00:35 UTC | 21h 25m |
| 2026-05-27 | SVR2879 | LED → DYU | May 27, 15:00 UTC | May 27, 23:15 UTC | 8h 15m |
| 2026-05-26 | SVR2734 | OSS → LED | May 26, 11:24 UTC | May 27, 01:29 UTC | 14h 5m |
| 2026-05-26 | SVR2151 | LED → FRU | May 26, 04:54 UTC | May 27, 01:29 UTC | 20h 35m |
| 2026-05-25 | SVR2879 | LED → DYU | May 25, 14:25 UTC | May 25, 14:40 UTC | 15m |
| 2026-05-24 | SVR391 | LED → KGD | May 24, 23:20 UTC | May 25, 08:50 UTC | 9h 30m |
| 2026-05-24 | SVR2733 | LED → OSS | May 24, 15:10 UTC | May 24, 15:30 UTC | 20m |
| 2026-05-23 | SVR876 | PKX → SVX | May 23, 19:20 UTC | May 24, 09:50 UTC | 14h 30m |
| 2026-05-23 | SVR2986 | FRU → SVX | May 23, 02:50 UTC | May 23, 09:10 UTC | 6h 20m |
| 2026-05-22 | SVR2862 | SKD → SVX | May 22, 23:30 UTC | May 22, 23:55 UTC | 25m |
| 2026-05-21 | SVR774 | IST → SVX | May 21, 17:00 UTC | May 21, 17:10 UTC | 10m |
| 2026-05-21 | SVR773 | SVX → IST | May 21, 08:50 UTC | May 21, 09:35 UTC | 45m |
| 2026-05-21 | SVR2862 | SKD → SVX | May 21, 03:05 UTC | May 21, 03:20 UTC | 15m |
| 2026-05-20 | SVR2734 | OSS → LED | May 20, 06:00 UTC | May 20, 19:10 UTC | 13h 10m |
| 2026-05-19 | SVR2411 | DME → KVD | May 19, 09:35 UTC | May 19, 09:55 UTC | 20m |
| 2026-05-17 | SVR2412 | KVD → DME | May 17, 16:25 UTC | May 17, 17:20 UTC | 55m |
| 2026-05-16 | SVR2952 | GYD → SVX | May 16, 03:35 UTC | May 16, 03:55 UTC | 20m |
| 2026-05-15 | SVR2952 | GYD → SVX | May 15, 07:50 UTC | May 16, 03:55 UTC | 20h 4m |
| 2026-05-14 | SVR2104 | NMA → IKT | May 14, 15:05 UTC | May 15, 08:00 UTC | 16h 55m |
| 2026-05-14 | SVR2104 | NMA → IKT | May 14, 11:05 UTC | May 15, 08:00 UTC | 20h 55m |
| 2026-05-14 | SVR2952 | GYD → SVX | May 14, 02:30 UTC | May 14, 03:00 UTC | 30m |
| 2026-05-13 | SVR2317 | - | May 13, 06:40 UTC | May 14, 00:35 UTC | 17h 55m |
| 2026-05-12 | SVR2317 | - | May 12, 22:20 UTC | May 13, 17:20 UTC | 19h 0m |
| 2026-05-12 | SVR2317 | - | May 12, 22:10 UTC | May 13, 17:20 UTC | 19h 10m |
| 2026-05-11 | SVR2411 | DME → KVD | May 11, 18:45 UTC | May 12, 09:55 UTC | 15h 10m |
| 2026-05-10 | SVR2412 | KVD → DME | May 10, 12:05 UTC | May 10, 14:34 UTC | 2h 30m |
| 2026-05-10 | SVR2411 | DME → KVD | May 10, 08:15 UTC | May 10, 08:30 UTC | 15m |
| 2026-05-10 | SVR262 | SVX → DME | May 10, 05:20 UTC | May 10, 05:40 UTC | 20m |
| 2026-05-10 | SVR262 | SVX → DME | May 10, 03:35 UTC | May 10, 04:45 UTC | 1h 10m |
| 2026-05-09 | SVR263 | DME → SVX | May 9, 18:05 UTC | May 9, 18:25 UTC | 20m |
| 2026-05-08 | SVR105 | DME → IKT | May 8, 18:30 UTC | May 9, 18:15 UTC | 23h 45m |
| 2026-05-08 | SVR300 | SVX → DME | May 8, 11:09 UTC | May 8, 18:50 UTC | 7h 40m |
| 2026-05-07 | SVR774 | IST → SVX | May 7, 18:40 UTC | May 8, 08:44 UTC | 14h 5m |
| 2026-05-06 | SVR2317 | - | May 6, 07:15 UTC | May 6, 16:55 UTC | 9h 40m |
| 2026-05-04 | SVR774 | IST → SVX | May 4, 17:10 UTC | May 4, 19:00 UTC | 1h 51m |
| 2026-05-04 | SVR7242 | IST → AER | May 4, 10:05 UTC | May 4, 10:15 UTC | 10m |
| 2026-05-03 | SVR2950 | EVN → SVX | May 3, 20:45 UTC | May 3, 21:10 UTC | 25m |
| 2026-05-03 | SVR2949 | SVX → EVN | May 3, 19:10 UTC | May 3, 19:25 UTC | 15m |
| 2026-04-30 | SVR9310 | - | Apr 30, 00:15 UTC | Apr 30, 10:40 UTC | 10h 25m |
| 2026-04-28 | SVR270 | SVX → DME | Apr 28, 16:05 UTC | Apr 28, 19:40 UTC | 3h 35m |
| 2026-04-27 | SVR2317 | - | Apr 27, 21:15 UTC | Apr 28, 19:40 UTC | 22h 25m |
| 2026-04-27 | SVR2317 | - | Apr 27, 18:20 UTC | Apr 28, 16:45 UTC | 22h 25m |
| 2026-04-27 | SVR2318 | - | Apr 27, 17:30 UTC | Apr 28, 16:15 UTC | 22h 45m |
| 2026-04-27 | SVR2318 | - | Apr 27, 06:55 UTC | Apr 27, 21:55 UTC | 15h 0m |
| 2026-04-27 | SVR2772 | SKD → DME | Apr 27, 03:35 UTC | Apr 27, 04:20 UTC | 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 RA-73833 page for operator, model, and routing details .