sensors Mode-S transponder
152060
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73824 · AIRBUS A-320
- Hex
- 152060
- Octal
- 05220140
- Decimal
- 1,384,544
- Country
- RU
- Tail
- RA-73824
- Type
- A320
- Flights observed
- 120
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- Jul 26, 21:15 UTC
Last known position
Country allocation
The ICAO 24-bit address 152060 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 | - | 8 | 2026-06-16 |
| SVR2719 | Ural Airlines | 7 | 2026-05-26 |
| SVR2772 | Ural Airlines | 6 | 2026-07-24 |
| SVR2720 | Ural Airlines | 6 | 2026-06-12 |
| SVR094 | Ural Airlines | 6 | 2026-05-11 |
| SVR2412 | - | 5 | 2026-06-23 |
| SVR783 | Ural Airlines | 4 | 2026-07-26 |
| SVR2909 | Ural Airlines | 4 | 2026-06-23 |
| SVR2103 | Ural Airlines | 4 | 2026-05-01 |
| SVR784 | Ural Airlines | 3 | 2026-07-26 |
| SVR774 | Ural Airlines | 3 | 2026-04-26 |
| SVR773 | Ural Airlines | 3 | 2026-04-25 |
| SVR365 | Ural Airlines | 3 | 2026-07-19 |
| SVR321 | Ural Airlines | 3 | 2026-04-24 |
| SVR2910 | Ural Airlines | 3 | 2026-06-28 |
| SVR2104 | Ural Airlines | 3 | 2026-05-01 |
| SVR093 | Ural Airlines | 3 | 2026-04-16 |
| SVR772 | Ural Airlines | 2 | 2026-06-07 |
| SVR771 | Ural Airlines | 2 | 2026-06-07 |
| SVR2862 | Ural Airlines | 2 | 2026-05-27 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | SVR271 | DME → SVX | Jul 26, 21:05 UTC | Jul 26, 21:15 UTC | 10m |
| 2026-07-26 | SVR784 | IST → DME | Jul 26, 14:40 UTC | Jul 26, 16:15 UTC | 1h 35m |
| 2026-07-26 | SVR783 | DME → IST | Jul 26, 12:00 UTC | Jul 26, 12:20 UTC | 20m |
| 2026-07-26 | SVR783 | DME → IST | Jul 26, 10:00 UTC | Jul 26, 11:15 UTC | 1h 15m |
| 2026-07-24 | SVR2772 | SKD → DME | Jul 24, 14:00 UTC | Jul 25, 07:05 UTC | 17h 5m |
| 2026-07-24 | SVR2772 | SKD → DME | Jul 24, 07:05 UTC | Jul 25, 01:55 UTC | 18h 50m |
| 2026-07-23 | SVR2804 | FRU → DME | Jul 23, 17:00 UTC | Jul 24, 14:15 UTC | 21h 15m |
| 2026-07-23 | SVR784 | IST → DME | Jul 23, 14:05 UTC | Jul 24, 14:00 UTC | 23h 55m |
| 2026-07-23 | SVR784 | IST → DME | Jul 23, 13:45 UTC | Jul 24, 07:05 UTC | 17h 20m |
| 2026-07-23 | SVR783 | DME → IST | Jul 23, 10:25 UTC | Jul 23, 12:10 UTC | 1h 45m |
| 2026-07-22 | SVR783 | DME → IST | Jul 22, 17:10 UTC | Jul 23, 12:10 UTC | 19h 0m |
| 2026-07-22 | SVR2612 | NMA → DME | Jul 22, 14:00 UTC | Jul 22, 14:35 UTC | 35m |
| 2026-07-19 | SVR365 | SVX → IKT | Jul 19, 06:30 UTC | Jul 19, 11:45 UTC | 5h 15m |
| 2026-07-16 | SVR1324 | - | Jul 16, 07:40 UTC | Jul 16, 07:55 UTC | 15m |
| 2026-07-14 | SVR2968 | - | Jul 14, 17:25 UTC | Jul 14, 18:00 UTC | 35m |
| 2026-06-30 | SVR9383 | - | Jun 30, 08:00 UTC | Jun 30, 08:25 UTC | 25m |
| 2026-06-28 | SVR2910 | OSS → DME | Jun 28, 01:34 UTC | Jun 28, 18:25 UTC | 16h 50m |
| 2026-06-27 | SVR2910 | OSS → DME | Jun 27, 17:55 UTC | Jun 28, 06:44 UTC | 12h 50m |
| 2026-06-27 | SVR2141 | DME → FEG | Jun 27, 06:54 UTC | Jun 27, 07:15 UTC | 20m |
| 2026-06-26 | SVR2772 | SKD → DME | Jun 26, 03:34 UTC | Jun 26, 03:45 UTC | 10m |
| 2026-06-24 | SVR2609 | - | Jun 24, 11:39 UTC | Jun 24, 21:54 UTC | 10h 15m |
| 2026-06-23 | SVR2909 | DME → OSS | Jun 23, 17:34 UTC | Jun 24, 11:45 UTC | 18h 10m |
| 2026-06-23 | SVR2412 | - | Jun 23, 12:05 UTC | Jun 24, 11:45 UTC | 23h 40m |
| 2026-06-23 | SVR2411 | - | Jun 23, 10:15 UTC | Jun 23, 10:24 UTC | 10m |
| 2026-06-22 | SVR2611 | DME → NMA | Jun 22, 06:54 UTC | Jun 22, 18:09 UTC | 11h 15m |
| 2026-06-19 | SVR075 | - | Jun 19, 16:09 UTC | Jun 19, 18:09 UTC | 2h 0m |
| 2026-06-19 | SVR403 | - | Jun 19, 13:29 UTC | Jun 19, 14:39 UTC | 1h 10m |
| 2026-06-16 | SVR2805 | KJA → OSS | Jun 16, 13:30 UTC | Jun 17, 06:15 UTC | 16h 46m |
| 2026-06-16 | SVR2317 | - | Jun 16, 02:04 UTC | Jun 17, 02:00 UTC | 23h 56m |
| 2026-06-15 | SVR2317 | - | Jun 15, 22:00 UTC | Jun 16, 13:40 UTC | 15h 40m |
| 2026-06-12 | SVR2720 | TAS → IKT | Jun 12, 03:30 UTC | Jun 12, 15:00 UTC | 11h 30m |
| 2026-06-11 | SVR2720 | TAS → IKT | Jun 11, 06:25 UTC | Jun 12, 04:45 UTC | 22h 20m |
| 2026-06-10 | SVR2803 | DME → FRU | Jun 10, 18:35 UTC | Jun 11, 06:45 UTC | 12h 10m |
| 2026-06-10 | SVR2771 | DME → SKD | Jun 10, 07:10 UTC | Jun 10, 18:50 UTC | 11h 40m |
| 2026-06-10 | SVR2910 | OSS → DME | Jun 10, 02:35 UTC | Jun 10, 02:45 UTC | 10m |
| 2026-06-09 | SVR2909 | DME → OSS | Jun 9, 17:45 UTC | Jun 9, 18:05 UTC | 20m |
| 2026-06-09 | SVR2909 | DME → OSS | Jun 9, 16:45 UTC | Jun 9, 17:05 UTC | 20m |
| 2026-06-09 | SVR2412 | KVD → DME | Jun 9, 14:15 UTC | Jun 9, 14:45 UTC | 30m |
| 2026-06-09 | SVR2412 | KVD → DME | Jun 9, 11:50 UTC | Jun 9, 12:45 UTC | 55m |
| 2026-06-08 | SVR2909 | DME → OSS | Jun 8, 17:15 UTC | Jun 8, 18:10 UTC | 55m |
| 2026-06-08 | SVR2804 | FRU → DME | Jun 8, 14:45 UTC | Jun 8, 15:04 UTC | 20m |
| 2026-06-07 | SVR2412 | KVD → DME | Jun 7, 20:25 UTC | Jun 8, 07:00 UTC | 10h 35m |
| 2026-06-07 | SVR772 | IST → DME | Jun 7, 10:15 UTC | Jun 7, 12:50 UTC | 2h 35m |
| 2026-06-07 | SVR771 | DME → IST | Jun 7, 08:35 UTC | Jun 7, 08:55 UTC | 20m |
| 2026-06-07 | SVR2772 | SKD → DME | Jun 7, 02:10 UTC | Jun 7, 02:25 UTC | 15m |
| 2026-06-06 | SVR2142 | FEG → DME | Jun 6, 07:10 UTC | Jun 6, 18:55 UTC | 11h 45m |
| 2026-06-05 | SVR2141 | DME → FEG | Jun 5, 13:05 UTC | Jun 6, 07:25 UTC | 18h 20m |
| 2026-06-05 | SVR2803 | DME → FRU | Jun 5, 06:15 UTC | Jun 5, 13:10 UTC | 6h 55m |
| 2026-06-02 | SVR2772 | SKD → DME | Jun 2, 12:05 UTC | Jun 3, 07:05 UTC | 19h 0m |
| 2026-06-02 | SVR2772 | SKD → DME | Jun 2, 11:45 UTC | Jun 3, 07:05 UTC | 19h 20m |
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-73824 page for operator, model, and routing details .