sensors Mode-S transponder
152053
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73811 · AIRBUS A-319
- Hex
- 152053
- Octal
- 05220123
- Decimal
- 1,384,531
- Country
- RU
- Tail
- RA-73811
- Type
- A319
- Flights observed
- 37
- Distinct callsigns
- 16
- Country
- RU
- Last broadcast
- 5h ago
Current position
Country allocation
The ICAO 24-bit address 152053 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 16 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| SVR624 | Ural Airlines | 5 | 2026-05-21 |
| SVR404 | Ural Airlines | 5 | 2026-05-29 |
| SVR173 | Ural Airlines | 5 | 2026-05-12 |
| SVR623 | Ural Airlines | 4 | 2026-05-10 |
| SVR403 | Ural Airlines | 4 | 2026-05-29 |
| SVR365 | Ural Airlines | 2 | 2026-05-26 |
| SVR299 | Ural Airlines | 2 | 2026-04-28 |
| SVR174 | Ural Airlines | 2 | 2026-04-29 |
| SVR321 | Ural Airlines | 1 | 2026-05-16 |
| SVR300 | Ural Airlines | 1 | 2026-05-15 |
| SVR2986 | Ural Airlines | 1 | 2026-05-16 |
| SVR269 | Ural Airlines | 1 | 2026-04-19 |
| SVR263 | Ural Airlines | 1 | 2026-05-15 |
| SVR225 | Ural Airlines | 1 | 2026-05-26 |
| SVR205 | Ural Airlines | 1 | 2026-05-17 |
| SSVR403 | - | 1 | 2026-05-18 |
Recent flights last 37
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | SVR404 | KGD → SVX | May 29, 16:00 UTC | May 29, 23:45 UTC | 7h 45m |
| 2026-05-29 | SVR403 | SVX → KGD | May 29, 14:00 UTC | May 29, 14:25 UTC | 25m |
| 2026-05-27 | SVR404 | KGD → SVX | May 27, 16:00 UTC | May 28, 09:40 UTC | 17h 40m |
| 2026-05-27 | SVR403 | SVX → KGD | May 27, 11:20 UTC | May 27, 14:10 UTC | 2h 50m |
| 2026-05-26 | SVR365 | SVX → IKT | May 26, 11:05 UTC | May 26, 11:50 UTC | 45m |
| 2026-05-26 | SVR365 | SVX → IKT | May 26, 09:55 UTC | May 26, 10:14 UTC | 20m |
| 2026-05-26 | SVR225 | SVX → LED | May 26, 05:34 UTC | May 26, 06:20 UTC | 45m |
| 2026-05-22 | SVR403 | SVX → KGD | May 22, 03:50 UTC | May 22, 14:40 UTC | 10h 50m |
| 2026-05-21 | SVR624 | SVX → HTA | May 21, 00:00 UTC | May 21, 00:35 UTC | 35m |
| 2026-05-20 | SVR404 | KGD → SVX | May 20, 17:15 UTC | May 20, 18:35 UTC | 1h 20m |
| 2026-05-18 | SVR624 | SVX → HTA | May 18, 23:15 UTC | May 19, 11:15 UTC | 12h 0m |
| 2026-05-18 | SSVR403 | - | May 18, 11:00 UTC | May 19, 10:45 UTC | 23h 44m |
| 2026-05-17 | SVR205 | SVX → MRV | May 17, 09:15 UTC | May 17, 13:20 UTC | 4h 5m |
| 2026-05-16 | SVR321 | SVX → AER | May 16, 13:41 UTC | May 16, 15:20 UTC | 1h 40m |
| 2026-05-16 | SVR2986 | FRU → SVX | May 16, 02:05 UTC | May 16, 07:05 UTC | 5h 1m |
| 2026-05-15 | SVR263 | DME → SVX | May 15, 18:10 UTC | May 15, 18:25 UTC | 15m |
| 2026-05-15 | SVR300 | SVX → DME | May 15, 11:40 UTC | May 15, 12:20 UTC | 40m |
| 2026-05-13 | SVR404 | KGD → SVX | May 13, 16:30 UTC | May 14, 09:55 UTC | 17h 25m |
| 2026-05-13 | SVR404 | KGD → SVX | May 13, 11:10 UTC | May 14, 09:55 UTC | 22h 45m |
| 2026-05-12 | SVR173 | SVX → KHV | May 12, 18:40 UTC | May 12, 18:50 UTC | 10m |
| 2026-05-11 | SVR403 | SVX → KGD | May 11, 11:25 UTC | May 11, 14:55 UTC | 3h 30m |
| 2026-05-10 | SVR173 | SVX → KHV | May 10, 15:45 UTC | May 10, 16:50 UTC | 1h 5m |
| 2026-05-10 | SVR173 | SVX → KHV | May 10, 14:34 UTC | May 10, 14:59 UTC | 25m |
| 2026-05-10 | SVR623 | HTA → SVX | May 10, 08:15 UTC | May 10, 09:24 UTC | 1h 10m |
| 2026-04-29 | SVR624 | SVX → HTA | Apr 29, 16:55 UTC | Apr 29, 17:20 UTC | 25m |
| 2026-04-29 | SVR174 | KHV → SVX | Apr 29, 13:30 UTC | Apr 29, 14:20 UTC | 50m |
| 2026-04-28 | SVR299 | DME → SVX | Apr 28, 14:55 UTC | Apr 28, 15:15 UTC | 20m |
| 2026-04-26 | SVR174 | KHV → SVX | Apr 26, 12:30 UTC | Apr 26, 13:25 UTC | 55m |
| 2026-04-25 | SVR173 | SVX → KHV | Apr 25, 15:55 UTC | Apr 25, 16:35 UTC | 40m |
| 2026-04-25 | SVR173 | SVX → KHV | Apr 25, 14:45 UTC | Apr 25, 15:10 UTC | 25m |
| 2026-04-25 | SVR623 | HTA → SVX | Apr 25, 04:50 UTC | Apr 25, 05:15 UTC | 25m |
| 2026-04-20 | SVR624 | SVX → HTA | Apr 20, 12:40 UTC | Apr 21, 00:20 UTC | 11h 40m |
| 2026-04-19 | SVR269 | DME → SVX | Apr 19, 11:00 UTC | Apr 19, 11:15 UTC | 15m |
| 2026-04-17 | SVR623 | HTA → SVX | Apr 17, 09:20 UTC | Apr 17, 09:35 UTC | 15m |
| 2026-04-17 | SVR623 | HTA → SVX | Apr 17, 08:45 UTC | Apr 17, 09:15 UTC | 30m |
| 2026-04-14 | SVR624 | SVX → HTA | Apr 14, 22:10 UTC | Apr 14, 22:45 UTC | 35m |
| 2026-04-13 | SVR299 | DME → SVX | Apr 13, 15:05 UTC | Apr 13, 15:25 UTC | 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-73811 page for operator, model, and routing details .