sensors Mode-S transponder
152059
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73817 · AIRBUS A-320
- Hex
- 152059
- Octal
- 05220131
- Decimal
- 1,384,537
- Country
- RU
- Tail
- RA-73817
- Type
- A320
- Flights observed
- 74
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 152059 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 | - | 6 | 2026-06-18 |
| SVR094 | - | 5 | 2026-07-06 |
| RA73817 | - | 5 | 2026-07-15 |
| SVR627 | Ural Airlines | 4 | 2026-06-12 |
| SVR269 | Ural Airlines | 4 | 2026-05-19 |
| SVR209 | Ural Airlines | 3 | 2026-05-14 |
| SVR105 | - | 3 | 2026-06-17 |
| SVR093 | Ural Airlines | 3 | 2026-06-16 |
| SVR9851 | - | 2 | 2026-06-12 |
| SVR9710 | - | 2 | 2026-04-18 |
| SVR9166 | - | 2 | 2026-06-24 |
| SVR628 | Ural Airlines | 2 | 2026-06-12 |
| SVR404 | Ural Airlines | 2 | 2026-05-24 |
| SVR403 | Ural Airlines | 2 | 2026-05-24 |
| SVR391 | Ural Airlines | 2 | 2026-05-16 |
| SVR2920 | Ural Airlines | 2 | 2026-04-15 |
| SVR2919 | - | 2 | 2026-07-02 |
| SVR2806 | Ural Airlines | 2 | 2026-04-15 |
| SVR2805 | - | 2 | 2026-04-15 |
| SVR274 | Ural Airlines | 2 | 2026-05-21 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-15 | RA73817 | - | Jul 15, 20:30 UTC | Jul 16, 13:45 UTC | 17h 15m |
| 2026-07-13 | SVR1338 | - | Jul 13, 07:10 UTC | Jul 13, 07:40 UTC | 30m |
| 2026-07-13 | SVR1337 | - | Jul 13, 05:05 UTC | Jul 13, 05:40 UTC | 35m |
| 2026-07-06 | SVR094 | - | Jul 6, 18:00 UTC | Jul 7, 03:45 UTC | 9h 45m |
| 2026-07-02 | SVR146 | AER → KUF | Jul 2, 18:10 UTC | Jul 2, 18:35 UTC | 25m |
| 2026-07-02 | SVR2919 | - | Jul 2, 02:05 UTC | Jul 2, 03:35 UTC | 1h 30m |
| 2026-07-01 | SVR2929 | - | Jul 1, 08:10 UTC | Jul 1, 23:50 UTC | 15h 40m |
| 2026-06-24 | RA73817 | - | Jun 24, 14:34 UTC | Jun 25, 07:30 UTC | 16h 55m |
| 2026-06-24 | SVR9166 | - | Jun 24, 11:59 UTC | Jun 25, 07:30 UTC | 19h 30m |
| 2026-06-24 | SVR9166 | - | Jun 24, 03:00 UTC | Jun 24, 15:14 UTC | 12h 15m |
| 2026-06-23 | SVR094 | - | Jun 23, 04:29 UTC | Jun 24, 03:35 UTC | 23h 5m |
| 2026-06-22 | SVR094 | - | Jun 22, 21:00 UTC | Jun 23, 05:15 UTC | 8h 15m |
| 2026-06-18 | SVR106 | - | Jun 18, 23:30 UTC | Jun 19, 05:05 UTC | 5h 34m |
| 2026-06-18 | SVR106 | - | Jun 18, 01:20 UTC | Jun 19, 00:00 UTC | 22h 40m |
| 2026-06-17 | SVR106 | - | Jun 17, 20:10 UTC | Jun 18, 02:00 UTC | 5h 50m |
| 2026-06-17 | SVR105 | - | Jun 17, 17:05 UTC | Jun 17, 17:15 UTC | 10m |
| 2026-06-16 | SVR093 | DME → HTA | Jun 16, 20:35 UTC | Jun 17, 06:05 UTC | 9h 30m |
| 2026-06-16 | SVR106 | - | Jun 16, 01:15 UTC | Jun 16, 21:05 UTC | 19h 51m |
| 2026-06-15 | SVR105 | - | Jun 15, 17:10 UTC | Jun 16, 01:50 UTC | 8h 40m |
| 2026-06-14 | SVR1344 | MCX → DME | Jun 14, 18:00 UTC | Jun 14, 18:10 UTC | 10m |
| 2026-06-12 | SVR628 | KGD → DME | Jun 12, 16:15 UTC | Jun 13, 06:50 UTC | 14h 34m |
| 2026-06-12 | SVR627 | DME → KGD | Jun 12, 12:20 UTC | Jun 12, 14:40 UTC | 2h 20m |
| 2026-06-12 | SVR9851 | SVO → SVO | Jun 12, 09:35 UTC | Jun 12, 10:35 UTC | 1h 0m |
| 2026-06-07 | SVR266 | SVX → DME | Jun 7, 20:55 UTC | Jun 8, 15:40 UTC | 18h 45m |
| 2026-06-07 | SVR106 | IKT → DME | Jun 7, 06:55 UTC | Jun 8, 05:40 UTC | 22h 45m |
| 2026-06-05 | SVR106 | IKT → DME | Jun 5, 06:50 UTC | Jun 6, 01:55 UTC | 19h 5m |
| 2026-06-03 | SVR219 | SVX → AER | Jun 3, 05:55 UTC | Jun 3, 15:25 UTC | 9h 30m |
| 2026-05-31 | RA73817 | - | May 31, 10:35 UTC | May 31, 10:55 UTC | 20m |
| 2026-05-27 | SVR105 | DME → IKT | May 27, 20:25 UTC | May 28, 08:55 UTC | 12h 30m |
| 2026-05-27 | SVR627 | DME → KGD | May 27, 10:05 UTC | May 27, 11:00 UTC | 55m |
| 2026-05-25 | SVR093 | DME → HTA | May 25, 17:15 UTC | May 25, 18:30 UTC | 1h 15m |
| 2026-05-24 | SVR404 | KGD → SVX | May 24, 16:35 UTC | May 24, 17:45 UTC | 1h 10m |
| 2026-05-24 | SVR403 | SVX → KGD | May 24, 04:45 UTC | May 24, 14:55 UTC | 10h 10m |
| 2026-05-21 | SVR274 | SVX → DME | May 21, 08:05 UTC | May 21, 13:05 UTC | 5h 0m |
| 2026-05-19 | SVR269 | DME → SVX | May 19, 11:50 UTC | May 19, 13:25 UTC | 1h 35m |
| 2026-05-18 | SVR269 | DME → SVX | May 18, 16:40 UTC | May 19, 13:25 UTC | 20h 44m |
| 2026-05-18 | SVR2754 | DYU → SVX | May 18, 06:40 UTC | May 18, 16:55 UTC | 10h 15m |
| 2026-05-17 | RA73817 | - | May 17, 17:50 UTC | May 18, 06:45 UTC | 12h 55m |
| 2026-05-16 | SVR392 | KGD → LED | May 16, 10:25 UTC | May 16, 11:46 UTC | 1h 20m |
| 2026-05-16 | SVR391 | LED → KGD | May 16, 07:55 UTC | May 16, 08:51 UTC | 55m |
| 2026-05-15 | SVR391 | LED → KGD | May 15, 12:20 UTC | May 16, 08:51 UTC | 20h 30m |
| 2026-05-15 | SVR269 | DME → SVX | May 15, 11:10 UTC | May 16, 08:51 UTC | 21h 40m |
| 2026-05-14 | SVR209 | SVX → KRR | May 14, 01:35 UTC | May 14, 12:05 UTC | 10h 30m |
| 2026-05-12 | SVR209 | SVX → KRR | May 12, 12:00 UTC | May 12, 12:55 UTC | 55m |
| 2026-05-11 | SVR209 | SVX → KRR | May 11, 17:50 UTC | May 12, 12:55 UTC | 19h 5m |
| 2026-05-06 | SVR272 | SVX → DME | May 6, 20:15 UTC | May 7, 06:05 UTC | 9h 50m |
| 2026-05-06 | SVR628 | KGD → DME | May 6, 13:20 UTC | May 6, 14:35 UTC | 1h 15m |
| 2026-05-06 | SVR627 | DME → KGD | May 6, 05:20 UTC | May 6, 11:15 UTC | 5h 55m |
| 2026-05-05 | SVR627 | DME → KGD | May 5, 13:50 UTC | May 6, 11:15 UTC | 21h 25m |
| 2026-05-04 | SVR2904 | OSS → SVX | May 4, 18:45 UTC | May 5, 14:00 UTC | 19h 15m |
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-73817 page for operator, model, and routing details .