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
- 118
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 1d 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 | - | 17 | 2026-07-04 |
| SVR372 | - | 15 | 2026-07-04 |
| SVR168 | Ural Airlines | 15 | 2026-06-27 |
| SVR167 | - | 11 | 2026-07-12 |
| SVR651 | Ural Airlines | 4 | 2026-06-02 |
| SVR2428 | - | 4 | 2026-07-06 |
| SVR9037 | - | 3 | 2026-04-26 |
| SVR8254 | Ural Airlines | 3 | 2026-07-01 |
| SVR628 | Ural Airlines | 3 | 2026-05-12 |
| SVR2970 | - | 3 | 2026-06-23 |
| SVR2426 | Ural Airlines | 3 | 2026-06-19 |
| SVR153 | Ural Airlines | 3 | 2026-06-27 |
| SVR8446 | Ural Airlines | 2 | 2026-06-17 |
| SVR8253 | Ural Airlines | 2 | 2026-05-31 |
| SVR627 | Ural Airlines | 2 | 2026-05-05 |
| SVR460 | - | 2 | 2026-06-13 |
| SVR2804 | Ural Airlines | 2 | 2026-04-30 |
| SVR279 | - | 2 | 2026-06-24 |
| SVR263 | - | 2 | 2026-07-08 |
| SVR154 | - | 2 | 2026-07-09 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-12 | SVR167 | - | Jul 12, 19:30 UTC | Jul 12, 20:05 UTC | 35m |
| 2026-07-10 | SVR624 | - | Jul 10, 16:30 UTC | Jul 10, 16:40 UTC | 10m |
| 2026-07-09 | SVR154 | - | Jul 9, 12:50 UTC | Jul 9, 13:00 UTC | 10m |
| 2026-07-08 | SVR263 | - | Jul 8, 18:35 UTC | Jul 8, 18:50 UTC | 15m |
| 2026-07-06 | SVR2428 | - | Jul 6, 23:20 UTC | Jul 6, 23:35 UTC | 15m |
| 2026-07-05 | SVR2428 | - | Jul 5, 21:30 UTC | Jul 5, 22:25 UTC | 55m |
| 2026-07-04 | SVR372 | - | Jul 4, 12:30 UTC | Jul 4, 18:00 UTC | 5h 30m |
| 2026-07-04 | SVR371 | - | Jul 4, 09:40 UTC | Jul 4, 10:20 UTC | 40m |
| 2026-07-01 | SVR8254 | DYU → DME | Jul 1, 06:30 UTC | Jul 1, 06:55 UTC | 25m |
| 2026-06-27 | SVR153 | DME → MRV | Jun 27, 09:15 UTC | Jun 27, 09:24 UTC | 10m |
| 2026-06-27 | SVR168 | KGD → DME | Jun 27, 05:55 UTC | Jun 27, 07:24 UTC | 1h 30m |
| 2026-06-25 | SVR168 | KGD → DME | Jun 25, 20:19 UTC | Jun 25, 21:55 UTC | 1h 35m |
| 2026-06-25 | SVR167 | - | Jun 25, 17:34 UTC | Jun 25, 18:04 UTC | 30m |
| 2026-06-24 | SVR279 | - | Jun 24, 14:00 UTC | Jun 24, 14:24 UTC | 25m |
| 2026-06-24 | SVR372 | - | Jun 24, 10:30 UTC | Jun 24, 11:45 UTC | 1h 15m |
| 2026-06-24 | SVR371 | - | Jun 24, 06:35 UTC | Jun 24, 08:30 UTC | 1h 55m |
| 2026-06-23 | SVR2970 | - | Jun 23, 08:00 UTC | Jun 23, 08:20 UTC | 20m |
| 2026-06-19 | SVR2426 | LBD → ZIA | Jun 19, 09:09 UTC | Jun 19, 09:59 UTC | 50m |
| 2026-06-18 | SVR2426 | LBD → ZIA | Jun 18, 13:45 UTC | Jun 19, 09:59 UTC | 20h 14m |
| 2026-06-18 | SVR2426 | LBD → ZIA | Jun 18, 09:35 UTC | Jun 19, 09:30 UTC | 23h 54m |
| 2026-06-17 | SVR2428 | - | Jun 17, 20:30 UTC | Jun 18, 13:55 UTC | 17h 25m |
| 2026-06-17 | SVR8446 | DYU → ZIA | Jun 17, 06:45 UTC | Jun 17, 20:45 UTC | 14h 0m |
| 2026-06-15 | SVR2428 | - | Jun 15, 11:19 UTC | Jun 16, 00:24 UTC | 13h 5m |
| 2026-06-14 | SVR8446 | DYU → ZIA | Jun 14, 06:25 UTC | Jun 15, 00:45 UTC | 18h 20m |
| 2026-06-13 | SVR460 | - | Jun 13, 15:35 UTC | Jun 14, 15:00 UTC | 23h 25m |
| 2026-06-13 | SVR460 | - | Jun 13, 15:20 UTC | Jun 14, 06:50 UTC | 15h 30m |
| 2026-06-12 | SVR153 | DME → MRV | Jun 12, 13:30 UTC | Jun 12, 14:15 UTC | 45m |
| 2026-06-11 | SVR167 | DME → KGD | Jun 11, 12:40 UTC | Jun 11, 18:45 UTC | 6h 5m |
| 2026-06-10 | SVR652 | BAX → DME | Jun 10, 04:50 UTC | Jun 10, 05:00 UTC | 10m |
| 2026-06-09 | SVR153 | DME → MRV | Jun 9, 08:40 UTC | Jun 9, 09:00 UTC | 20m |
| 2026-06-06 | SVR168 | KGD → DME | Jun 6, 23:35 UTC | Jun 7, 04:50 UTC | 5h 15m |
| 2026-06-06 | SVR167 | DME → KGD | Jun 6, 15:39 UTC | Jun 6, 21:35 UTC | 5h 55m |
| 2026-06-06 | SVR2970 | TJU → DME | Jun 6, 07:45 UTC | Jun 6, 07:55 UTC | 10m |
| 2026-06-05 | SVR2970 | TJU → DME | Jun 5, 23:05 UTC | Jun 6, 06:45 UTC | 7h 40m |
| 2026-06-05 | SVR9301 | - | Jun 5, 10:20 UTC | Jun 6, 06:45 UTC | 20h 25m |
| 2026-06-04 | SVR263 | DME → SVX | Jun 4, 17:55 UTC | Jun 5, 10:45 UTC | 16h 50m |
| 2026-06-02 | SVR651 | DME → BAX | Jun 2, 20:55 UTC | Jun 2, 21:20 UTC | 25m |
| 2026-06-02 | SVR280 | AER → DME | Jun 2, 17:50 UTC | Jun 2, 18:10 UTC | 20m |
| 2026-06-02 | SVR8254 | DYU → DME | Jun 2, 07:00 UTC | Jun 2, 07:35 UTC | 35m |
| 2026-06-01 | SVR168 | KGD → DME | Jun 1, 17:50 UTC | Jun 1, 19:50 UTC | 2h 0m |
| 2026-06-01 | SVR372 | KGD → DME | Jun 1, 10:30 UTC | Jun 1, 16:15 UTC | 5h 45m |
| 2026-05-31 | SVR371 | DME → KGD | May 31, 20:45 UTC | Jun 1, 08:25 UTC | 11h 40m |
| 2026-05-31 | SVR8253 | DME → DYU | May 31, 00:15 UTC | May 31, 20:55 UTC | 20h 40m |
| 2026-05-30 | SVR8253 | DME → DYU | May 30, 23:20 UTC | May 31, 20:55 UTC | 21h 35m |
| 2026-05-30 | SVR168 | KGD → DME | May 30, 17:55 UTC | May 31, 00:25 UTC | 6h 30m |
| 2026-05-30 | SVR372 | KGD → DME | May 30, 10:15 UTC | May 30, 16:10 UTC | 5h 55m |
| 2026-05-29 | SVR371 | DME → KGD | May 29, 20:40 UTC | May 30, 08:30 UTC | 11h 50m |
| 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 |
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 .