sensors Mode-S transponder
152062
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73826 · AIRBUS A-320
- Hex
- 152062
- Octal
- 05220142
- Decimal
- 1,384,546
- Country
- RU
- Tail
- RA-73826
- Type
- A320
- Flights observed
- 41
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 14h ago
Last known position
Country allocation
The ICAO 24-bit address 152062 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 | Ural Airlines | 7 | 2026-05-26 |
| SVR391 | Ural Airlines | 4 | 2026-05-05 |
| SVR105 | Ural Airlines | 4 | 2026-05-10 |
| SVR392 | Ural Airlines | 2 | 2026-04-30 |
| SVR372 | Ural Airlines | 2 | 2026-04-15 |
| SVR2929 | Ural Airlines | 2 | 2026-05-13 |
| SVR2880 | Ural Airlines | 2 | 2026-05-06 |
| SVR168 | Ural Airlines | 2 | 2026-04-15 |
| SVR093 | Ural Airlines | 2 | 2026-05-29 |
| SVR628 | Ural Airlines | 1 | 2026-05-11 |
| SVR623 | Ural Airlines | 1 | 2026-04-27 |
| SVR404 | Ural Airlines | 1 | 2026-05-08 |
| SVR365 | Ural Airlines | 1 | 2026-05-21 |
| SVR2956 | Ural Airlines | 1 | 2026-05-23 |
| SVR2930 | Ural Airlines | 1 | 2026-05-13 |
| SVR2866 | Ural Airlines | 1 | 2026-05-13 |
| SVR266 | Ural Airlines | 1 | 2026-05-28 |
| SVR2641 | Ural Airlines | 1 | 2026-05-06 |
| SVR263 | Ural Airlines | 1 | 2026-04-12 |
| SVR262 | Ural Airlines | 1 | 2026-05-16 |
Recent flights last 41
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | SVR093 | DME → HTA | May 29, 17:25 UTC | May 29, 20:55 UTC | 3h 30m |
| 2026-05-28 | SVR266 | SVX → DME | May 28, 14:55 UTC | May 28, 20:40 UTC | 5h 45m |
| 2026-05-26 | SVR106 | IKT → DME | May 26, 20:05 UTC | May 27, 04:59 UTC | 8h 55m |
| 2026-05-26 | SVR106 | IKT → DME | May 26, 01:10 UTC | May 26, 20:34 UTC | 19h 25m |
| 2026-05-25 | SVR106 | IKT → DME | May 25, 17:35 UTC | May 26, 01:55 UTC | 8h 20m |
| 2026-05-23 | SVR2956 | LBD → SVX | May 23, 04:15 UTC | May 23, 04:25 UTC | 10m |
| 2026-05-21 | SVR365 | SVX → IKT | May 21, 15:35 UTC | May 21, 16:10 UTC | 35m |
| 2026-05-21 | SVR225 | SVX → LED | May 21, 05:05 UTC | May 21, 06:05 UTC | 1h 0m |
| 2026-05-17 | SVR219 | SVX → AER | May 17, 07:25 UTC | May 17, 08:25 UTC | 1h 0m |
| 2026-05-16 | SVR262 | SVX → DME | May 16, 03:50 UTC | May 16, 04:35 UTC | 45m |
| 2026-05-13 | SVR2866 | DYU → MRV | May 13, 19:30 UTC | May 14, 09:50 UTC | 14h 20m |
| 2026-05-13 | SVR2929 | KJA → DYU | May 13, 12:35 UTC | May 14, 09:50 UTC | 21h 15m |
| 2026-05-13 | SVR2929 | KJA → DYU | May 13, 06:35 UTC | May 14, 06:15 UTC | 23h 40m |
| 2026-05-13 | SVR2930 | DYU → KJA | May 13, 06:25 UTC | May 14, 00:25 UTC | 18h 0m |
| 2026-05-11 | SVR628 | KGD → DME | May 11, 01:15 UTC | May 11, 18:25 UTC | 17h 11m |
| 2026-05-10 | SVR105 | DME → IKT | May 10, 20:09 UTC | May 10, 20:30 UTC | 20m |
| 2026-05-08 | SVR404 | KGD → SVX | May 8, 17:15 UTC | May 8, 18:10 UTC | 55m |
| 2026-05-06 | SVR2641 | LED → LBD | May 6, 00:35 UTC | May 6, 19:15 UTC | 18h 39m |
| 2026-05-06 | SVR2880 | DYU → LED | May 6, 00:01 UTC | May 6, 19:15 UTC | 19h 14m |
| 2026-05-05 | SVR2880 | DYU → LED | May 5, 14:50 UTC | May 6, 00:40 UTC | 9h 50m |
| 2026-05-05 | SVR391 | LED → KGD | May 5, 08:30 UTC | May 5, 08:50 UTC | 20m |
| 2026-05-03 | SVR391 | LED → KGD | May 3, 09:25 UTC | May 3, 10:10 UTC | 45m |
| 2026-04-30 | SVR392 | KGD → LED | Apr 30, 11:10 UTC | Apr 30, 11:55 UTC | 45m |
| 2026-04-30 | SVR391 | LED → KGD | Apr 30, 08:05 UTC | Apr 30, 08:45 UTC | 40m |
| 2026-04-28 | SVR392 | KGD → LED | Apr 28, 10:25 UTC | Apr 28, 11:55 UTC | 1h 30m |
| 2026-04-28 | SVR391 | LED → KGD | Apr 28, 07:50 UTC | Apr 28, 08:40 UTC | 50m |
| 2026-04-27 | SVR623 | HTA → SVX | Apr 27, 09:20 UTC | Apr 28, 08:30 UTC | 23h 10m |
| 2026-04-23 | SVR106 | IKT → DME | Apr 23, 01:35 UTC | Apr 23, 02:25 UTC | 50m |
| 2026-04-23 | SVR106 | IKT → DME | Apr 23, 00:00 UTC | Apr 23, 00:15 UTC | 15m |
| 2026-04-22 | SVR105 | DME → IKT | Apr 22, 21:55 UTC | Apr 22, 22:10 UTC | 15m |
| 2026-04-20 | SVR094 | HTA → DME | Apr 20, 20:15 UTC | Apr 21, 10:55 UTC | 14h 40m |
| 2026-04-20 | SVR106 | IKT → DME | Apr 20, 01:20 UTC | Apr 20, 21:50 UTC | 20h 30m |
| 2026-04-19 | SVR106 | IKT → DME | Apr 19, 23:50 UTC | Apr 20, 21:50 UTC | 22h 0m |
| 2026-04-19 | SVR105 | DME → IKT | Apr 19, 21:35 UTC | Apr 19, 21:50 UTC | 15m |
| 2026-04-19 | SVR105 | DME → IKT | Apr 19, 20:00 UTC | Apr 19, 20:30 UTC | 30m |
| 2026-04-15 | SVR168 | KGD → DME | Apr 15, 19:05 UTC | Apr 15, 19:45 UTC | 40m |
| 2026-04-15 | SVR168 | KGD → DME | Apr 15, 17:40 UTC | Apr 15, 19:00 UTC | 1h 20m |
| 2026-04-15 | SVR372 | KGD → DME | Apr 15, 11:00 UTC | Apr 15, 12:30 UTC | 1h 30m |
| 2026-04-15 | SVR372 | KGD → DME | Apr 15, 10:15 UTC | Apr 15, 10:55 UTC | 40m |
| 2026-04-13 | SVR093 | DME → HTA | Apr 13, 20:15 UTC | Apr 13, 21:55 UTC | 1h 40m |
| 2026-04-12 | SVR263 | DME → SVX | Apr 12, 19:00 UTC | Apr 12, 19:25 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-73826 page for operator, model, and routing details .