sensors Mode-S transponder
152074
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73844 · AIRBUS A-321
- Hex
- 152074
- Octal
- 05220164
- Decimal
- 1,384,564
- Country
- RU
- Tail
- RA-73844
- Type
- A321
- Flights observed
- 35
- Distinct callsigns
- 18
- Country
- RU
- Last broadcast
- 4d ago
Last known position
Country allocation
The ICAO 24-bit address 152074 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 18 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| SVR371 | Ural Airlines | 4 | 2026-05-22 |
| SVR372 | Ural Airlines | 3 | 2026-05-22 |
| SVR279 | Ural Airlines | 3 | 2026-05-16 |
| SVR269 | Ural Airlines | 3 | 2026-05-29 |
| SVR263 | Ural Airlines | 3 | 2026-05-28 |
| SVR9695 | Ural Airlines | 2 | 2026-05-17 |
| SVR697 | Ural Airlines | 2 | 2026-05-11 |
| SVR628 | Ural Airlines | 2 | 2026-05-09 |
| SVR388 | Ural Airlines | 2 | 2026-04-27 |
| SVR2909 | Ural Airlines | 2 | 2026-05-14 |
| SVR280 | Ural Airlines | 2 | 2026-05-12 |
| SVR9896 | Ural Airlines | 1 | 2026-04-17 |
| SVR8253 | Ural Airlines | 1 | 2026-05-20 |
| SVR2956 | Ural Airlines | 1 | 2026-05-27 |
| SVR168 | Ural Airlines | 1 | 2026-05-22 |
| SVR153 | Ural Airlines | 1 | 2026-04-21 |
| SVR1344 | Ural Airlines | 1 | 2026-05-21 |
| SVR1343 | Ural Airlines | 1 | 2026-05-15 |
Recent flights last 35
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | SVR269 | DME → SVX | May 29, 13:00 UTC | May 30, 03:30 UTC | 14h 30m |
| 2026-05-29 | SVR269 | DME → SVX | May 29, 05:35 UTC | May 30, 03:30 UTC | 21h 55m |
| 2026-05-28 | SVR269 | DME → SVX | May 28, 19:40 UTC | May 29, 13:20 UTC | 17h 40m |
| 2026-05-28 | SVR263 | DME → SVX | May 28, 02:20 UTC | May 28, 23:35 UTC | 21h 15m |
| 2026-05-27 | SVR263 | DME → SVX | May 27, 21:05 UTC | May 28, 19:55 UTC | 22h 50m |
| 2026-05-27 | SVR2956 | LBD → SVX | May 27, 15:35 UTC | May 28, 02:30 UTC | 10h 55m |
| 2026-05-25 | SVR263 | DME → SVX | May 25, 18:50 UTC | May 25, 19:25 UTC | 34m |
| 2026-05-22 | SVR168 | KGD → DME | May 22, 18:25 UTC | May 22, 19:30 UTC | 1h 5m |
| 2026-05-22 | SVR372 | KGD → DME | May 22, 10:45 UTC | May 22, 16:35 UTC | 5h 50m |
| 2026-05-22 | SVR371 | DME → KGD | May 22, 07:45 UTC | May 22, 08:30 UTC | 45m |
| 2026-05-21 | SVR1344 | MCX → DME | May 21, 14:50 UTC | May 21, 15:20 UTC | 30m |
| 2026-05-20 | SVR8253 | DME → DYU | May 20, 21:45 UTC | May 20, 22:15 UTC | 30m |
| 2026-05-17 | SVR9695 | DME → MCX | May 17, 20:35 UTC | May 17, 20:55 UTC | 20m |
| 2026-05-16 | SVR9695 | DME → MCX | May 16, 22:00 UTC | May 17, 20:55 UTC | 22h 55m |
| 2026-05-16 | SVR279 | DME → AER | May 16, 12:35 UTC | May 16, 22:05 UTC | 9h 30m |
| 2026-05-15 | SVR279 | DME → AER | May 15, 22:35 UTC | May 16, 12:55 UTC | 14h 21m |
| 2026-05-15 | SVR1343 | DME → MCX | May 15, 09:30 UTC | May 15, 22:45 UTC | 13h 14m |
| 2026-05-14 | SVR2909 | DME → OSS | May 14, 18:00 UTC | May 15, 09:50 UTC | 15h 50m |
| 2026-05-12 | SVR280 | AER → DME | May 12, 23:01 UTC | May 13, 16:50 UTC | 17h 50m |
| 2026-05-12 | SVR279 | DME → AER | May 12, 11:30 UTC | May 13, 07:30 UTC | 20h 0m |
| 2026-05-11 | SVR697 | DME → KGD | May 11, 06:55 UTC | May 11, 07:40 UTC | 45m |
| 2026-05-10 | SVR697 | DME → KGD | May 10, 11:40 UTC | May 11, 07:40 UTC | 20h 0m |
| 2026-05-09 | SVR628 | KGD → DME | May 9, 13:05 UTC | May 10, 11:55 UTC | 22h 50m |
| 2026-05-09 | SVR628 | KGD → DME | May 9, 12:35 UTC | May 9, 14:30 UTC | 1h 55m |
| 2026-05-04 | SVR372 | KGD → DME | May 4, 10:30 UTC | May 4, 12:30 UTC | 2h 0m |
| 2026-05-04 | SVR371 | DME → KGD | May 4, 07:45 UTC | May 4, 08:45 UTC | 1h 0m |
| 2026-05-02 | SVR280 | AER → DME | May 2, 15:25 UTC | May 2, 15:35 UTC | 10m |
| 2026-04-29 | SVR2909 | DME → OSS | Apr 29, 17:55 UTC | Apr 29, 18:10 UTC | 15m |
| 2026-04-27 | SVR372 | KGD → DME | Apr 27, 12:15 UTC | Apr 27, 14:20 UTC | 2h 5m |
| 2026-04-27 | SVR371 | DME → KGD | Apr 27, 09:40 UTC | Apr 27, 10:35 UTC | 55m |
| 2026-04-27 | SVR388 | OMS → DME | Apr 27, 03:55 UTC | Apr 27, 04:25 UTC | 30m |
| 2026-04-26 | SVR388 | OMS → DME | Apr 26, 22:00 UTC | Apr 27, 03:15 UTC | 5h 15m |
| 2026-04-22 | SVR371 | DME → KGD | Apr 22, 18:10 UTC | Apr 23, 09:50 UTC | 15h 40m |
| 2026-04-21 | SVR153 | DME → MRV | Apr 21, 09:20 UTC | Apr 21, 09:35 UTC | 15m |
| 2026-04-17 | SVR9896 | NJC → UFA | Apr 17, 06:45 UTC | Apr 17, 06:55 UTC | 10m |
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-73844 page for operator, model, and routing details .