sensors Mode-S transponder
152061
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73825 · AIRBUS A-320
- Hex
- 152061
- Octal
- 05220141
- Decimal
- 1,384,545
- Country
- RU
- Tail
- RA-73825
- Type
- A320
- Flights observed
- 85
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 3d ago
Last known position
Country allocation
The ICAO 24-bit address 152061 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 |
|---|---|---|---|
| SVR403 | Ural Airlines | 5 | 2026-06-01 |
| SVR094 | - | 5 | 2026-06-18 |
| SVR623 | - | 4 | 2026-07-07 |
| SVR209 | - | 4 | 2026-06-21 |
| SVR628 | - | 3 | 2026-06-29 |
| SVR627 | - | 3 | 2026-06-25 |
| SVR624 | - | 3 | 2026-07-01 |
| SVR266 | Ural Airlines | 3 | 2026-05-25 |
| SVR264 | Ural Airlines | 3 | 2026-04-24 |
| SVR261 | Ural Airlines | 3 | 2026-05-20 |
| SVR105 | - | 3 | 2026-06-28 |
| SVR547 | Ural Airlines | 2 | 2026-06-04 |
| SVR504 | Ural Airlines | 2 | 2026-04-18 |
| SVR404 | Ural Airlines | 2 | 2026-04-26 |
| SVR392 | Ural Airlines | 2 | 2026-05-28 |
| SVR321 | Ural Airlines | 2 | 2026-05-20 |
| SVR2880 | - | 2 | 2026-07-08 |
| SVR272 | Ural Airlines | 2 | 2026-04-17 |
| SVR263 | Ural Airlines | 2 | 2026-05-17 |
| SVR106 | - | 2 | 2026-06-28 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-10 | SVR2930 | - | Jul 10, 22:00 UTC | Jul 11, 14:30 UTC | 16h 30m |
| 2026-07-08 | SVR2880 | - | Jul 8, 23:50 UTC | Jul 9, 10:05 UTC | 10h 15m |
| 2026-07-07 | SVR623 | - | Jul 7, 02:20 UTC | Jul 7, 16:55 UTC | 14h 35m |
| 2026-07-05 | SVR292 | - | Jul 5, 12:15 UTC | Jul 5, 12:25 UTC | 10m |
| 2026-07-05 | SVR291 | - | Jul 5, 10:35 UTC | Jul 5, 10:50 UTC | 15m |
| 2026-07-03 | SVR1366 | - | Jul 3, 15:25 UTC | Jul 4, 08:30 UTC | 17h 5m |
| 2026-07-01 | SVR624 | - | Jul 1, 23:45 UTC | Jul 2, 00:25 UTC | 40m |
| 2026-06-29 | SVR628 | - | Jun 29, 14:09 UTC | Jun 29, 21:34 UTC | 7h 25m |
| 2026-06-28 | SVR106 | - | Jun 28, 22:49 UTC | Jun 29, 12:20 UTC | 13h 30m |
| 2026-06-28 | SVR105 | - | Jun 28, 01:29 UTC | Jun 28, 23:25 UTC | 21h 55m |
| 2026-06-25 | SVR628 | - | Jun 25, 15:04 UTC | Jun 26, 03:05 UTC | 12h 0m |
| 2026-06-25 | SVR627 | - | Jun 25, 07:59 UTC | Jun 25, 13:05 UTC | 5h 5m |
| 2026-06-22 | SVR2990 | - | Jun 22, 08:50 UTC | Jun 22, 09:00 UTC | 10m |
| 2026-06-21 | SVR209 | - | Jun 21, 14:15 UTC | Jun 21, 14:34 UTC | 20m |
| 2026-06-20 | SVR1334 | - | Jun 20, 09:05 UTC | Jun 20, 16:05 UTC | 7h 0m |
| 2026-06-19 | SVR628 | - | Jun 19, 20:24 UTC | Jun 19, 21:59 UTC | 1h 35m |
| 2026-06-19 | SVR627 | - | Jun 19, 17:39 UTC | Jun 19, 18:09 UTC | 30m |
| 2026-06-18 | SVR094 | - | Jun 18, 06:00 UTC | Jun 18, 06:20 UTC | 20m |
| 2026-06-15 | SVR105 | - | Jun 15, 04:15 UTC | Jun 15, 09:35 UTC | 5h 20m |
| 2026-06-12 | SVR1338 | KEJ → AER | Jun 12, 02:55 UTC | Jun 12, 07:10 UTC | 4h 15m |
| 2026-06-12 | SVR1337 | AER → KEJ | Jun 12, 00:55 UTC | Jun 12, 01:30 UTC | 35m |
| 2026-06-11 | SVR372 | KGD → DME | Jun 11, 11:45 UTC | Jun 11, 13:30 UTC | 1h 45m |
| 2026-06-11 | SVR371 | DME → KGD | Jun 11, 01:30 UTC | Jun 11, 09:40 UTC | 8h 10m |
| 2026-06-09 | SVR109 | DME → KRR | Jun 9, 08:50 UTC | Jun 9, 09:15 UTC | 25m |
| 2026-06-08 | SVR209 | SVX → KRR | Jun 8, 11:10 UTC | Jun 9, 05:55 UTC | 18h 45m |
| 2026-06-06 | SVR322 | AER → SVX | Jun 6, 08:35 UTC | Jun 6, 09:24 UTC | 50m |
| 2026-06-04 | SVR547 | LED → AER | Jun 4, 16:05 UTC | Jun 5, 08:50 UTC | 16h 45m |
| 2026-06-04 | SVR547 | LED → AER | Jun 4, 10:20 UTC | Jun 5, 08:50 UTC | 22h 30m |
| 2026-06-03 | SVR623 | HTA → SVX | Jun 3, 14:55 UTC | Jun 4, 10:45 UTC | 19h 50m |
| 2026-06-02 | SVR242 | AER → DME | Jun 2, 18:40 UTC | Jun 2, 21:20 UTC | 2h 40m |
| 2026-06-01 | SVR623 | HTA → SVX | Jun 1, 22:55 UTC | Jun 2, 10:45 UTC | 11h 50m |
| 2026-06-01 | SVR403 | SVX → KGD | Jun 1, 12:20 UTC | Jun 1, 14:30 UTC | 2h 10m |
| 2026-05-31 | SVR403 | SVX → KGD | May 31, 14:45 UTC | Jun 1, 14:15 UTC | 23h 30m |
| 2026-05-29 | SVR2880 | DYU → LED | May 29, 01:15 UTC | May 29, 01:25 UTC | 10m |
| 2026-05-28 | SVR2879 | LED → DYU | May 28, 14:10 UTC | May 28, 14:35 UTC | 25m |
| 2026-05-28 | SVR392 | KGD → LED | May 28, 11:05 UTC | May 28, 11:55 UTC | 50m |
| 2026-05-28 | SVR391 | LED → KGD | May 28, 07:35 UTC | May 28, 08:55 UTC | 1h 20m |
| 2026-05-27 | SVR2641 | - | May 27, 17:40 UTC | May 27, 18:00 UTC | 20m |
| 2026-05-25 | SVR266 | SVX → DME | May 25, 14:40 UTC | May 26, 08:45 UTC | 18h 5m |
| 2026-05-25 | SVR266 | SVX → DME | May 25, 11:00 UTC | May 26, 08:45 UTC | 21h 44m |
| 2026-05-24 | SVR266 | SVX → DME | May 24, 19:30 UTC | May 25, 15:25 UTC | 19h 55m |
| 2026-05-24 | SVR173 | SVX → KHV | May 24, 14:45 UTC | May 24, 14:55 UTC | 10m |
| 2026-05-23 | SVR392 | KGD → LED | May 23, 16:30 UTC | May 24, 11:50 UTC | 19h 20m |
| 2026-05-23 | SVR548 | AER → LED | May 23, 13:50 UTC | May 23, 14:00 UTC | 10m |
| 2026-05-22 | SVR623 | HTA → SVX | May 22, 02:15 UTC | May 22, 13:50 UTC | 11h 35m |
| 2026-05-20 | SVR321 | SVX → AER | May 20, 14:15 UTC | May 20, 18:50 UTC | 4h 35m |
| 2026-05-20 | SVR261 | DME → SVX | May 20, 08:50 UTC | May 20, 09:05 UTC | 15m |
| 2026-05-19 | SVR093 | DME → HTA | May 19, 18:50 UTC | May 19, 21:25 UTC | 2h 35m |
| 2026-05-19 | SVR627 | DME → KGD | May 19, 11:10 UTC | May 19, 11:35 UTC | 25m |
| 2026-05-19 | SVR094 | HTA → DME | May 19, 06:40 UTC | May 19, 06:50 UTC | 10m |
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-73825 page for operator, model, and routing details .