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
- 67
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 21h ago
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 |
|---|---|---|---|
| SVR2719 | Ural Airlines | 7 | 2026-05-26 |
| SVR2317 | - | 6 | 2026-05-26 |
| SVR094 | Ural Airlines | 6 | 2026-05-11 |
| SVR2720 | Ural Airlines | 4 | 2026-05-26 |
| SVR2103 | Ural Airlines | 4 | 2026-05-01 |
| SVR774 | Ural Airlines | 3 | 2026-04-26 |
| SVR773 | Ural Airlines | 3 | 2026-04-25 |
| SVR321 | Ural Airlines | 3 | 2026-04-24 |
| SVR2104 | Ural Airlines | 3 | 2026-05-01 |
| SVR093 | Ural Airlines | 3 | 2026-04-16 |
| SVR365 | Ural Airlines | 2 | 2026-05-24 |
| SVR2862 | Ural Airlines | 2 | 2026-05-27 |
| SVR2861 | Ural Airlines | 2 | 2026-05-06 |
| SVR266 | Ural Airlines | 2 | 2026-04-25 |
| SVR219 | Ural Airlines | 2 | 2026-05-02 |
| SVR772 | Ural Airlines | 1 | 2026-05-29 |
| SVR771 | Ural Airlines | 1 | 2026-05-29 |
| SVR7242 | Ural Airlines | 1 | 2026-04-20 |
| SVR2952 | Ural Airlines | 1 | 2026-05-25 |
| SVR269 | Ural Airlines | 1 | 2026-04-23 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | SVR772 | IST → DME | May 29, 11:25 UTC | May 29, 18:35 UTC | 7h 10m |
| 2026-05-29 | SVR771 | DME → IST | May 29, 09:10 UTC | May 29, 09:40 UTC | 30m |
| 2026-05-28 | SVR2127 | DME → KSQ | May 28, 06:50 UTC | May 29, 01:30 UTC | 18h 40m |
| 2026-05-28 | SVR264 | SVX → DME | May 28, 03:45 UTC | May 28, 03:55 UTC | 10m |
| 2026-05-27 | SVR2862 | SKD → SVX | May 27, 17:00 UTC | May 27, 22:15 UTC | 5h 15m |
| 2026-05-27 | SVR2862 | SKD → SVX | May 27, 00:34 UTC | May 27, 22:15 UTC | 21h 40m |
| 2026-05-26 | SVR2719 | IKT → TAS | May 26, 18:14 UTC | May 27, 17:05 UTC | 22h 51m |
| 2026-05-26 | SVR2720 | TAS → IKT | May 26, 11:50 UTC | May 27, 00:44 UTC | 12h 55m |
| 2026-05-26 | SVR2317 | - | May 26, 03:40 UTC | May 27, 00:44 UTC | 21h 5m |
| 2026-05-26 | SVR2317 | - | May 26, 00:04 UTC | May 26, 19:34 UTC | 19h 30m |
| 2026-05-25 | SVR2317 | - | May 25, 23:54 UTC | May 26, 19:34 UTC | 19h 40m |
| 2026-05-25 | SVR2952 | GYD → SVX | May 25, 06:20 UTC | May 25, 06:30 UTC | 10m |
| 2026-05-24 | SVR365 | SVX → IKT | May 24, 12:00 UTC | May 24, 12:25 UTC | 25m |
| 2026-05-24 | SVR365 | SVX → IKT | May 24, 10:45 UTC | May 24, 11:00 UTC | 15m |
| 2026-05-23 | SVR225 | SVX → LED | May 23, 19:10 UTC | May 24, 09:05 UTC | 13h 55m |
| 2026-05-11 | SVR094 | HTA → DME | May 11, 04:20 UTC | May 11, 11:35 UTC | 7h 15m |
| 2026-05-09 | SVR094 | HTA → DME | May 9, 17:15 UTC | May 10, 06:00 UTC | 12h 45m |
| 2026-05-09 | SVR1343 | DME → MCX | May 9, 10:20 UTC | May 9, 10:45 UTC | 25m |
| 2026-05-06 | SVR2861 | SVX → SKD | May 6, 16:45 UTC | May 6, 22:15 UTC | 5h 29m |
| 2026-05-06 | SVR262 | SVX → DME | May 6, 05:30 UTC | May 6, 05:45 UTC | 15m |
| 2026-05-05 | SVR2719 | IKT → TAS | May 5, 13:10 UTC | May 6, 04:35 UTC | 15h 25m |
| 2026-05-03 | SVR073 | DME → KGD | May 3, 11:20 UTC | May 3, 18:00 UTC | 6h 40m |
| 2026-05-02 | SVR219 | SVX → AER | May 2, 22:40 UTC | May 3, 09:30 UTC | 10h 49m |
| 2026-05-02 | SVR209 | SVX → KRR | May 2, 05:05 UTC | May 2, 05:15 UTC | 10m |
| 2026-05-01 | SVR2861 | SVX → SKD | May 1, 16:50 UTC | May 1, 22:15 UTC | 5h 25m |
| 2026-05-01 | SVR2103 | IKT → NMA | May 1, 06:20 UTC | May 1, 12:20 UTC | 6h 0m |
| 2026-05-01 | SVR2103 | IKT → NMA | May 1, 04:55 UTC | May 1, 05:10 UTC | 15m |
| 2026-05-01 | SVR2104 | NMA → IKT | May 1, 02:00 UTC | May 1, 02:10 UTC | 10m |
| 2026-05-01 | SVR2104 | NMA → IKT | May 1, 00:15 UTC | May 1, 00:50 UTC | 35m |
| 2026-04-30 | SVR2719 | IKT → TAS | Apr 30, 09:10 UTC | Apr 30, 16:25 UTC | 7h 15m |
| 2026-04-29 | SVR2719 | IKT → TAS | Apr 29, 16:40 UTC | Apr 30, 15:55 UTC | 23h 14m |
| 2026-04-29 | SVR2317 | - | Apr 29, 10:35 UTC | Apr 30, 09:40 UTC | 23h 4m |
| 2026-04-29 | SVR2317 | - | Apr 29, 07:05 UTC | Apr 29, 16:50 UTC | 9h 46m |
| 2026-04-28 | SVR2317 | - | Apr 28, 18:50 UTC | Apr 29, 16:50 UTC | 22h 1m |
| 2026-04-28 | SVR2719 | IKT → TAS | Apr 28, 12:40 UTC | Apr 29, 11:45 UTC | 23h 6m |
| 2026-04-28 | SVR2719 | IKT → TAS | Apr 28, 11:10 UTC | Apr 28, 11:25 UTC | 15m |
| 2026-04-28 | SVR2720 | TAS → IKT | Apr 28, 07:35 UTC | Apr 28, 08:00 UTC | 25m |
| 2026-04-26 | SVR774 | IST → SVX | Apr 26, 18:15 UTC | Apr 26, 19:55 UTC | 1h 40m |
| 2026-04-25 | SVR773 | SVX → IST | Apr 25, 20:45 UTC | Apr 26, 06:40 UTC | 9h 55m |
| 2026-04-25 | SVR266 | SVX → DME | Apr 25, 17:40 UTC | Apr 25, 18:00 UTC | 20m |
| 2026-04-25 | SVR266 | SVX → DME | Apr 25, 16:30 UTC | Apr 25, 17:05 UTC | 35m |
| 2026-04-24 | SVR321 | SVX → AER | Apr 24, 13:55 UTC | Apr 25, 02:10 UTC | 12h 15m |
| 2026-04-24 | SVR321 | SVX → AER | Apr 24, 12:05 UTC | Apr 24, 12:15 UTC | 10m |
| 2026-04-24 | SVR2103 | IKT → NMA | Apr 24, 01:40 UTC | Apr 24, 02:15 UTC | 35m |
| 2026-04-24 | SVR2103 | IKT → NMA | Apr 24, 00:15 UTC | Apr 24, 00:30 UTC | 15m |
| 2026-04-23 | SVR2104 | NMA → IKT | Apr 23, 19:30 UTC | Apr 23, 20:40 UTC | 1h 10m |
| 2026-04-23 | SVR2013 | SVX → NMA | Apr 23, 14:35 UTC | Apr 23, 14:45 UTC | 10m |
| 2026-04-23 | SVR269 | DME → SVX | Apr 23, 11:55 UTC | Apr 23, 12:15 UTC | 20m |
| 2026-04-23 | SVR2264 | NMA → AER | Apr 23, 02:10 UTC | Apr 23, 02:25 UTC | 15m |
| 2026-04-22 | SVR321 | SVX → AER | Apr 22, 14:15 UTC | Apr 22, 16:15 UTC | 2h 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 RA-73824 page for operator, model, and routing details .