sensors Mode-S transponder
152046
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73798 · AIRBUS A-321
- Hex
- 152046
- Octal
- 05220106
- Decimal
- 1,384,518
- Country
- RU
- Tail
- RA-73798
- Type
- A321
- Flights observed
- 72
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 3h ago
Last known position
Country allocation
The ICAO 24-bit address 152046 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 |
|---|---|---|---|
| SVR371 | Ural Airlines | 13 | 2026-05-28 |
| SVR372 | Ural Airlines | 11 | 2026-05-28 |
| SVR168 | Ural Airlines | 10 | 2026-05-28 |
| SVR167 | Ural Airlines | 7 | 2026-05-28 |
| SVR9037 | - | 3 | 2026-04-26 |
| SVR651 | Ural Airlines | 3 | 2026-05-15 |
| SVR628 | Ural Airlines | 3 | 2026-05-12 |
| SVR627 | Ural Airlines | 2 | 2026-05-05 |
| SVR2804 | Ural Airlines | 2 | 2026-04-30 |
| SVR9904 | Ural Airlines | 1 | 2026-04-20 |
| SVR9876 | Ural Airlines | 1 | 2026-04-16 |
| SVR9875 | - | 1 | 2026-04-15 |
| SVR9584 | Ural Airlines | 1 | 2026-04-22 |
| SVR9356 | - | 1 | 2026-04-18 |
| SVR9057 | Ural Airlines | 1 | 2026-04-18 |
| SVR9056 | Ural Airlines | 1 | 2026-04-16 |
| SVR8254 | Ural Airlines | 1 | 2026-05-27 |
| SVR388 | Ural Airlines | 1 | 2026-05-20 |
| SVR387 | Ural Airlines | 1 | 2026-05-29 |
| SVR2910 | - | 1 | 2026-04-13 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | SVR387 | DME → OMS | May 29, 20:40 UTC | May 29, 22:00 UTC | 1h 20m |
| 2026-05-28 | SVR168 | KGD → DME | May 28, 17:40 UTC | May 29, 07:35 UTC | 13h 55m |
| 2026-05-28 | SVR167 | DME → KGD | May 28, 14:50 UTC | May 28, 16:00 UTC | 1h 10m |
| 2026-05-28 | SVR372 | KGD → DME | May 28, 10:25 UTC | May 28, 12:20 UTC | 1h 55m |
| 2026-05-28 | SVR371 | DME → KGD | May 28, 06:30 UTC | May 28, 08:25 UTC | 1h 55m |
| 2026-05-27 | SVR8254 | DYU → DME | May 27, 06:29 UTC | May 27, 06:40 UTC | 10m |
| 2026-05-24 | SVR168 | KGD → DME | May 24, 18:15 UTC | May 24, 20:10 UTC | 1h 55m |
| 2026-05-24 | SVR372 | KGD → DME | May 24, 10:40 UTC | May 24, 16:20 UTC | 5h 40m |
| 2026-05-24 | SVR371 | DME → KGD | May 24, 07:20 UTC | May 24, 08:25 UTC | 1h 5m |
| 2026-05-21 | SVR279 | DME → AER | May 21, 09:50 UTC | May 21, 10:05 UTC | 15m |
| 2026-05-20 | SVR388 | OMS → DME | May 20, 21:30 UTC | May 21, 03:50 UTC | 6h 20m |
| 2026-05-18 | SVR168 | KGD → DME | May 18, 17:40 UTC | May 18, 19:00 UTC | 1h 19m |
| 2026-05-18 | SVR372 | KGD → DME | May 18, 10:25 UTC | May 18, 16:15 UTC | 5h 50m |
| 2026-05-17 | SVR168 | KGD → DME | May 17, 18:30 UTC | May 18, 08:50 UTC | 14h 20m |
| 2026-05-17 | SVR372 | KGD → DME | May 17, 10:45 UTC | May 17, 16:55 UTC | 6h 10m |
| 2026-05-17 | SVR371 | DME → KGD | May 17, 08:15 UTC | May 17, 09:10 UTC | 55m |
| 2026-05-15 | SVR651 | DME → BAX | May 15, 20:50 UTC | May 15, 21:10 UTC | 20m |
| 2026-05-14 | SVR651 | DME → BAX | May 14, 22:25 UTC | May 15, 21:10 UTC | 22h 44m |
| 2026-05-14 | SVR168 | KGD → DME | May 14, 17:45 UTC | May 14, 22:40 UTC | 4h 55m |
| 2026-05-14 | SVR167 | DME → KGD | May 14, 15:15 UTC | May 14, 16:10 UTC | 55m |
| 2026-05-14 | SVR372 | KGD → DME | May 14, 10:35 UTC | May 14, 12:15 UTC | 1h 40m |
| 2026-05-14 | SVR371 | DME → KGD | May 14, 07:50 UTC | May 14, 08:35 UTC | 45m |
| 2026-05-12 | SVR628 | KGD → DME | May 12, 12:35 UTC | May 12, 14:40 UTC | 2h 5m |
| 2026-05-11 | SVR651 | DME → BAX | May 11, 19:45 UTC | May 12, 11:00 UTC | 15h 15m |
| 2026-05-10 | SVR2803 | DME → FRU | May 10, 23:05 UTC | May 11, 14:55 UTC | 15h 50m |
| 2026-05-09 | SVR154 | MRV → DME | May 9, 14:25 UTC | May 9, 19:05 UTC | 4h 40m |
| 2026-05-05 | SVR628 | KGD → DME | May 5, 15:55 UTC | May 5, 17:10 UTC | 1h 15m |
| 2026-05-05 | SVR627 | DME → KGD | May 5, 13:15 UTC | May 5, 14:00 UTC | 45m |
| 2026-05-02 | SVR371 | DME → KGD | May 2, 10:50 UTC | May 2, 11:25 UTC | 35m |
| 2026-05-01 | SVR168 | KGD → DME | May 1, 18:00 UTC | May 1, 20:00 UTC | 2h 0m |
| 2026-05-01 | SVR167 | DME → KGD | May 1, 15:45 UTC | May 1, 16:35 UTC | 50m |
| 2026-05-01 | SVR372 | KGD → DME | May 1, 12:15 UTC | May 1, 12:25 UTC | 10m |
| 2026-05-01 | SVR372 | KGD → DME | May 1, 10:20 UTC | May 1, 11:45 UTC | 1h 25m |
| 2026-05-01 | SVR371 | DME → KGD | May 1, 02:40 UTC | May 1, 08:30 UTC | 5h 50m |
| 2026-04-30 | SVR2804 | FRU → DME | Apr 30, 06:40 UTC | May 1, 03:15 UTC | 20h 35m |
| 2026-04-29 | SVR168 | KGD → DME | Apr 29, 17:55 UTC | Apr 30, 07:15 UTC | 13h 19m |
| 2026-04-29 | SVR167 | DME → KGD | Apr 29, 15:15 UTC | Apr 29, 16:15 UTC | 1h 0m |
| 2026-04-29 | SVR371 | DME → KGD | Apr 29, 07:45 UTC | Apr 29, 08:40 UTC | 55m |
| 2026-04-28 | SVR628 | KGD → DME | Apr 28, 13:25 UTC | Apr 28, 15:30 UTC | 2h 5m |
| 2026-04-28 | SVR627 | DME → KGD | Apr 28, 11:00 UTC | Apr 28, 11:55 UTC | 55m |
| 2026-04-27 | SVR2804 | FRU → DME | Apr 27, 23:35 UTC | Apr 28, 07:40 UTC | 8h 5m |
| 2026-04-27 | SVR264 | SVX → DME | Apr 27, 03:55 UTC | Apr 27, 04:20 UTC | 25m |
| 2026-04-26 | SVR9037 | - | Apr 26, 13:15 UTC | Apr 26, 18:15 UTC | 5h 0m |
| 2026-04-25 | SVR168 | KGD → DME | Apr 25, 18:05 UTC | Apr 26, 09:05 UTC | 15h 0m |
| 2026-04-25 | SVR167 | DME → KGD | Apr 25, 15:30 UTC | Apr 25, 16:20 UTC | 50m |
| 2026-04-25 | SVR372 | KGD → DME | Apr 25, 10:10 UTC | Apr 25, 12:10 UTC | 2h 0m |
| 2026-04-24 | SVR168 | KGD → DME | Apr 24, 18:05 UTC | Apr 25, 08:40 UTC | 14h 35m |
| 2026-04-24 | SVR372 | KGD → DME | Apr 24, 10:05 UTC | Apr 24, 16:40 UTC | 6h 35m |
| 2026-04-24 | SVR371 | DME → KGD | Apr 24, 07:45 UTC | Apr 24, 08:35 UTC | 50m |
| 2026-04-23 | SVR371 | DME → KGD | Apr 23, 12:10 UTC | Apr 24, 08:35 UTC | 20h 24m |
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-73798 page for operator, model, and routing details .