sensors Mode-S transponder
152068
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73832 · AIRBUS A-320
- Hex
- 152068
- Octal
- 05220150
- Decimal
- 1,384,552
- Country
- RU
- Tail
- RA-73832
- Type
- A320
- Flights observed
- 69
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 5h ago
Last known position
Country allocation
The ICAO 24-bit address 152068 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 |
|---|---|---|---|
| SVR106 | - | 11 | 2026-07-10 |
| SVR2879 | Ural Airlines | 4 | 2026-05-14 |
| SVR093 | - | 4 | 2026-07-11 |
| SVR391 | Ural Airlines | 3 | 2026-05-09 |
| SVR094 | - | 3 | 2026-07-11 |
| SVR628 | - | 2 | 2026-06-24 |
| SVR392 | Ural Airlines | 2 | 2026-04-27 |
| SVR272 | Ural Airlines | 2 | 2026-05-04 |
| SVR266 | Ural Airlines | 2 | 2026-04-28 |
| SVR2641 | Ural Airlines | 2 | 2026-05-09 |
| SVR174 | Ural Airlines | 2 | 2026-04-25 |
| SVR145 | Ural Airlines | 2 | 2026-06-13 |
| SVR627 | - | 1 | 2026-06-23 |
| SVR624 | - | 1 | 2026-07-09 |
| SVR619 | Ural Airlines | 1 | 2026-04-17 |
| SVR503 | Ural Airlines | 1 | 2026-07-18 |
| SVR404 | Ural Airlines | 1 | 2026-05-31 |
| SVR403 | Ural Airlines | 1 | 2026-05-31 |
| SVR388 | Ural Airlines | 1 | 2026-05-17 |
| SVR366 | - | 1 | 2026-07-05 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-18 | SVR503 | SVX → KGD | Jul 18, 12:40 UTC | Jul 18, 13:30 UTC | 50m |
| 2026-07-14 | SVR1388 | - | Jul 14, 11:05 UTC | Jul 14, 11:20 UTC | 15m |
| 2026-07-11 | SVR094 | - | Jul 11, 20:30 UTC | Jul 12, 03:30 UTC | 7h 0m |
| 2026-07-11 | SVR093 | - | Jul 11, 17:20 UTC | Jul 11, 17:35 UTC | 15m |
| 2026-07-10 | SVR106 | - | Jul 10, 20:10 UTC | Jul 11, 01:45 UTC | 5h 35m |
| 2026-07-09 | SVR624 | - | Jul 9, 16:35 UTC | Jul 9, 16:55 UTC | 20m |
| 2026-07-05 | SVR366 | - | Jul 5, 07:50 UTC | Jul 5, 08:45 UTC | 55m |
| 2026-07-04 | SVR365 | - | Jul 4, 10:25 UTC | Jul 4, 10:45 UTC | 20m |
| 2026-07-04 | SVR225 | - | Jul 4, 08:35 UTC | Jul 4, 08:45 UTC | 10m |
| 2026-07-02 | SVR168 | KGD → DME | Jul 2, 17:50 UTC | Jul 3, 06:15 UTC | 12h 25m |
| 2026-07-02 | SVR167 | - | Jul 2, 06:15 UTC | Jul 2, 16:15 UTC | 10h 0m |
| 2026-07-01 | SVR094 | - | Jul 1, 04:55 UTC | Jul 1, 05:30 UTC | 35m |
| 2026-06-29 | SVR106 | - | Jun 29, 20:30 UTC | Jun 30, 02:10 UTC | 5h 40m |
| 2026-06-24 | SVR628 | - | Jun 24, 12:50 UTC | Jun 24, 14:29 UTC | 1h 40m |
| 2026-06-23 | SVR627 | - | Jun 23, 22:55 UTC | Jun 24, 11:24 UTC | 12h 30m |
| 2026-06-14 | SVR628 | KGD → DME | Jun 14, 17:35 UTC | Jun 15, 07:20 UTC | 13h 45m |
| 2026-06-13 | SVR145 | KUF → AER | Jun 13, 07:00 UTC | Jun 13, 07:35 UTC | 35m |
| 2026-06-11 | SVR145 | KUF → AER | Jun 11, 10:25 UTC | Jun 12, 05:20 UTC | 18h 56m |
| 2026-06-10 | SVR2919 | KJA → LBD | Jun 10, 08:10 UTC | Jun 11, 01:20 UTC | 17h 10m |
| 2026-06-09 | SVR146 | AER → KUF | Jun 9, 14:00 UTC | Jun 9, 15:40 UTC | 1h 40m |
| 2026-06-07 | SVR2968 | DYU → KRR | Jun 7, 13:10 UTC | Jun 7, 19:05 UTC | 5h 55m |
| 2026-06-05 | SVR093 | DME → HTA | Jun 5, 18:05 UTC | Jun 6, 03:10 UTC | 9h 5m |
| 2026-06-04 | SVR093 | DME → HTA | Jun 4, 11:30 UTC | Jun 5, 03:05 UTC | 15h 35m |
| 2026-06-03 | SVR106 | IKT → DME | Jun 3, 20:10 UTC | Jun 4, 01:50 UTC | 5h 40m |
| 2026-06-02 | SVR263 | DME → SVX | Jun 2, 11:10 UTC | Jun 2, 19:45 UTC | 8h 35m |
| 2026-05-31 | SVR404 | KGD → SVX | May 31, 17:05 UTC | Jun 1, 08:55 UTC | 15h 50m |
| 2026-05-31 | SVR403 | SVX → KGD | May 31, 14:25 UTC | May 31, 15:10 UTC | 45m |
| 2026-05-29 | SVR265 | DME → SVX | May 29, 19:30 UTC | May 29, 20:45 UTC | 1h 15m |
| 2026-05-28 | SVR094 | HTA → DME | May 28, 18:15 UTC | May 29, 06:15 UTC | 12h 0m |
| 2026-05-24 | SVR106 | IKT → DME | May 24, 02:05 UTC | May 24, 21:45 UTC | 19h 40m |
| 2026-05-24 | SVR106 | IKT → DME | May 24, 01:40 UTC | May 24, 21:45 UTC | 20h 5m |
| 2026-05-23 | SVR106 | IKT → DME | May 23, 18:55 UTC | May 24, 05:10 UTC | 10h 15m |
| 2026-05-22 | SVR093 | DME → HTA | May 22, 21:25 UTC | May 23, 19:00 UTC | 21h 35m |
| 2026-05-22 | SVR106 | IKT → DME | May 22, 02:05 UTC | May 22, 21:55 UTC | 19h 50m |
| 2026-05-21 | SVR106 | IKT → DME | May 21, 04:55 UTC | May 22, 02:40 UTC | 21h 45m |
| 2026-05-21 | SVR106 | IKT → DME | May 21, 02:15 UTC | May 22, 02:00 UTC | 23h 45m |
| 2026-05-20 | SVR106 | IKT → DME | May 20, 21:15 UTC | May 21, 05:40 UTC | 8h 25m |
| 2026-05-19 | SVR209 | SVX → KRR | May 19, 12:10 UTC | May 19, 13:10 UTC | 1h 0m |
| 2026-05-17 | SVR388 | OMS → DME | May 17, 02:25 UTC | May 17, 23:00 UTC | 20h 35m |
| 2026-05-16 | SVR2990 | DYU → KZN | May 16, 02:30 UTC | May 16, 12:01 UTC | 9h 31m |
| 2026-05-14 | SVR2879 | LED → DYU | May 14, 15:05 UTC | May 14, 16:30 UTC | 1h 25m |
| 2026-05-13 | SVR2879 | LED → DYU | May 13, 18:55 UTC | May 14, 16:30 UTC | 21h 35m |
| 2026-05-11 | SVR2879 | LED → DYU | May 11, 14:50 UTC | May 12, 07:15 UTC | 16h 26m |
| 2026-05-10 | SVR2734 | OSS → LED | May 10, 22:49 UTC | May 11, 08:50 UTC | 10h 0m |
| 2026-05-09 | SVR391 | LED → KGD | May 9, 16:05 UTC | May 10, 08:45 UTC | 16h 40m |
| 2026-05-09 | SVR2641 | LED → LBD | May 9, 09:20 UTC | May 10, 08:00 UTC | 22h 40m |
| 2026-05-08 | SVR2641 | LED → LBD | May 8, 22:55 UTC | May 9, 16:30 UTC | 17h 35m |
| 2026-05-08 | SVR2733 | LED → OSS | May 8, 16:15 UTC | May 9, 09:40 UTC | 17h 25m |
| 2026-05-07 | SVR173 | SVX → KHV | May 7, 16:10 UTC | May 7, 16:25 UTC | 15m |
| 2026-05-04 | SVR109 | DME → KRR | May 4, 08:20 UTC | May 4, 08:45 UTC | 25m |
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-73832 page for operator, model, and routing details .