sensors Mode-S transponder
152067
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73831 · AIRBUS A-320
- Hex
- 152067
- Octal
- 05220147
- Decimal
- 1,384,551
- Country
- RU
- Tail
- RA-73831
- Type
- A320
- Flights observed
- 123
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 6h ago
Last known position
Country allocation
The ICAO 24-bit address 152067 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 |
|---|---|---|---|
| SVR773 | Ural Airlines | 10 | 2026-05-25 |
| SVR774 | - | 9 | 2026-06-21 |
| SVR205 | Ural Airlines | 6 | 2026-05-15 |
| SVR2720 | Ural Airlines | 5 | 2026-05-19 |
| SVR209 | Ural Airlines | 5 | 2026-05-15 |
| SVR2950 | - | 4 | 2026-06-24 |
| SVR2909 | Ural Airlines | 4 | 2026-06-02 |
| SVR2804 | Ural Airlines | 4 | 2026-06-14 |
| SVR2772 | - | 4 | 2026-07-10 |
| SVR2611 | - | 4 | 2026-07-13 |
| SVR627 | - | 3 | 2026-07-11 |
| SVR2806 | - | 3 | 2026-06-23 |
| SVR2771 | - | 3 | 2026-07-06 |
| SVR2719 | Ural Airlines | 3 | 2026-05-19 |
| SVR2412 | - | 3 | 2026-07-14 |
| SVR2104 | Ural Airlines | 3 | 2026-05-21 |
| SVR7242 | - | 2 | 2026-06-21 |
| SVR7241 | Ural Airlines | 2 | 2026-06-21 |
| SVR628 | - | 2 | 2026-07-12 |
| SVR623 | Ural Airlines | 2 | 2026-04-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | SVR2412 | - | Jul 14, 14:35 UTC | Jul 14, 20:10 UTC | 5h 35m |
| 2026-07-14 | SVR2411 | - | Jul 14, 12:30 UTC | Jul 14, 12:40 UTC | 10m |
| 2026-07-13 | SVR2611 | - | Jul 13, 08:01 UTC | Jul 13, 08:45 UTC | 45m |
| 2026-07-12 | SVR628 | - | Jul 12, 14:50 UTC | Jul 12, 22:00 UTC | 7h 10m |
| 2026-07-11 | SVR627 | - | Jul 11, 17:50 UTC | Jul 12, 12:55 UTC | 19h 5m |
| 2026-07-11 | SVR627 | - | Jul 11, 17:25 UTC | Jul 12, 12:55 UTC | 19h 30m |
| 2026-07-11 | SVR2461 | - | Jul 11, 00:50 UTC | Jul 11, 18:25 UTC | 17h 35m |
| 2026-07-10 | SVR2772 | - | Jul 10, 06:20 UTC | Jul 11, 01:35 UTC | 19h 15m |
| 2026-07-09 | SVR116 | - | Jul 9, 12:05 UTC | Jul 10, 06:35 UTC | 18h 30m |
| 2026-07-08 | SVR116 | - | Jul 8, 18:10 UTC | Jul 9, 12:20 UTC | 18h 10m |
| 2026-07-07 | SVR2412 | - | Jul 7, 12:25 UTC | Jul 7, 18:25 UTC | 6h 0m |
| 2026-07-06 | SVR2771 | - | Jul 6, 18:10 UTC | Jul 6, 18:25 UTC | 15m |
| 2026-07-05 | SVR144 | - | Jul 5, 13:40 UTC | Jul 5, 14:05 UTC | 25m |
| 2026-07-04 | SVR106 | - | Jul 4, 00:30 UTC | Jul 4, 06:00 UTC | 5h 30m |
| 2026-07-03 | SVR2772 | - | Jul 3, 01:50 UTC | Jul 4, 01:00 UTC | 23h 10m |
| 2026-07-02 | SVR2772 | - | Jul 2, 19:30 UTC | Jul 3, 02:45 UTC | 7h 15m |
| 2026-06-30 | SVR2412 | - | Jun 30, 13:00 UTC | Jul 1, 06:30 UTC | 17h 30m |
| 2026-06-30 | SVR2411 | - | Jun 30, 11:05 UTC | Jun 30, 11:20 UTC | 15m |
| 2026-06-29 | SVR2611 | DME → NMA | Jun 29, 06:05 UTC | Jun 29, 14:09 UTC | 8h 5m |
| 2026-06-28 | SVR2611 | DME → NMA | Jun 28, 11:59 UTC | Jun 29, 06:50 UTC | 18h 50m |
| 2026-06-28 | SVR2772 | - | Jun 28, 03:09 UTC | Jun 28, 03:19 UTC | 10m |
| 2026-06-24 | SVR2950 | - | Jun 24, 17:25 UTC | Jun 24, 17:50 UTC | 25m |
| 2026-06-23 | SVR2806 | - | Jun 23, 22:19 UTC | Jun 24, 15:59 UTC | 17h 40m |
| 2026-06-21 | SVR774 | - | Jun 21, 17:50 UTC | Jun 21, 18:20 UTC | 30m |
| 2026-06-21 | SVR7241 | AER → IST | Jun 21, 15:40 UTC | Jun 21, 16:04 UTC | 25m |
| 2026-06-21 | SVR7242 | - | Jun 21, 09:44 UTC | Jun 21, 10:14 UTC | 30m |
| 2026-06-19 | SVR076 | - | Jun 19, 20:55 UTC | Jun 19, 21:49 UTC | 55m |
| 2026-06-18 | SVR2612 | - | Jun 18, 08:00 UTC | Jun 18, 08:20 UTC | 20m |
| 2026-06-15 | SVR2771 | DME → SKD | Jun 15, 18:15 UTC | Jun 15, 18:29 UTC | 15m |
| 2026-06-14 | SVR2771 | DME → SKD | Jun 14, 19:55 UTC | Jun 15, 18:29 UTC | 22h 34m |
| 2026-06-14 | SVR2804 | FRU → DME | Jun 14, 06:35 UTC | Jun 14, 20:05 UTC | 13h 30m |
| 2026-06-13 | SVR2804 | FRU → DME | Jun 13, 18:10 UTC | Jun 14, 15:15 UTC | 21h 5m |
| 2026-06-13 | SVR2141 | DME → FEG | Jun 13, 07:00 UTC | Jun 13, 18:20 UTC | 11h 20m |
| 2026-06-11 | SVR504 | KGD → SVX | Jun 11, 14:45 UTC | Jun 12, 05:25 UTC | 14h 41m |
| 2026-06-10 | SVR503 | SVX → KGD | Jun 10, 18:35 UTC | Jun 11, 13:00 UTC | 18h 25m |
| 2026-06-10 | SVR149 | SVX → GDZ | Jun 10, 04:25 UTC | Jun 10, 18:40 UTC | 14h 15m |
| 2026-06-08 | SVR2950 | EVN → SVX | Jun 8, 16:10 UTC | Jun 8, 16:25 UTC | 15m |
| 2026-06-08 | SVR2949 | SVX → EVN | Jun 8, 08:35 UTC | Jun 8, 14:30 UTC | 5h 55m |
| 2026-06-08 | SVR2710 | OSS → DME | Jun 8, 05:55 UTC | Jun 8, 06:05 UTC | 10m |
| 2026-06-06 | SVR2804 | FRU → DME | Jun 6, 14:04 UTC | Jun 7, 06:10 UTC | 16h 5m |
| 2026-06-05 | SVR772 | IST → DME | Jun 5, 11:10 UTC | Jun 5, 13:35 UTC | 2h 25m |
| 2026-06-04 | SVR2804 | FRU → DME | Jun 4, 13:45 UTC | Jun 4, 14:25 UTC | 40m |
| 2026-06-02 | SVR2909 | DME → OSS | Jun 2, 17:30 UTC | Jun 3, 07:10 UTC | 13h 40m |
| 2026-06-02 | SVR2909 | DME → OSS | Jun 2, 06:40 UTC | Jun 2, 17:55 UTC | 11h 15m |
| 2026-06-01 | SVR2909 | DME → OSS | Jun 1, 18:05 UTC | Jun 2, 17:45 UTC | 23h 40m |
| 2026-06-01 | SVR2611 | DME → NMA | Jun 1, 06:35 UTC | Jun 1, 18:30 UTC | 11h 55m |
| 2026-05-30 | SVR2803 | DME → FRU | May 30, 22:15 UTC | May 30, 22:40 UTC | 25m |
| 2026-05-29 | SVR2141 | DME → FEG | May 29, 18:15 UTC | May 30, 07:20 UTC | 13h 5m |
| 2026-05-29 | SVR2021 | - | May 29, 06:35 UTC | May 29, 18:25 UTC | 11h 50m |
| 2026-05-28 | SVR2909 | DME → OSS | May 28, 19:10 UTC | May 29, 06:45 UTC | 11h 35m |
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-73831 page for operator, model, and routing details .