sensors Mode-S transponder
152072
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73842 · AIRBUS A-321
- Hex
- 152072
- Octal
- 05220162
- Decimal
- 1,384,562
- Country
- RU
- Tail
- RA-73842
- Type
- A321
- Flights observed
- 70
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 4d ago
Last known position
Country allocation
The ICAO 24-bit address 152072 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 |
|---|---|---|---|
| SVR168 | Ural Airlines | 12 | 2026-05-31 |
| SVR372 | - | 11 | 2026-06-16 |
| SVR371 | Ural Airlines | 10 | 2026-05-24 |
| SVR8445 | - | 4 | 2026-07-03 |
| SVR2442 | Ural Airlines | 4 | 2026-07-07 |
| SVR2441 | Ural Airlines | 3 | 2026-07-06 |
| SVR8446 | - | 2 | 2026-07-01 |
| SVR2930 | - | 2 | 2026-07-09 |
| SVR2428 | - | 2 | 2026-06-18 |
| SVR2427 | - | 2 | 2026-06-26 |
| SVR2426 | - | 2 | 2026-06-21 |
| SVR167 | Ural Airlines | 2 | 2026-05-25 |
| SVR154 | Ural Airlines | 2 | 2026-04-19 |
| SVR1344 | Ural Airlines | 2 | 2026-06-03 |
| SVR9876 | Ural Airlines | 1 | 2026-05-15 |
| SVR9056 | Ural Airlines | 1 | 2026-05-15 |
| SVR8254 | Ural Airlines | 1 | 2026-06-05 |
| SVR628 | Ural Airlines | 1 | 2026-04-24 |
| SVR387 | Ural Airlines | 1 | 2026-05-17 |
| SVR2969 | Ural Airlines | 1 | 2026-06-01 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-09 | SVR2930 | - | Jul 9, 01:15 UTC | Jul 9, 12:10 UTC | 10h 55m |
| 2026-07-08 | SVR2930 | - | Jul 8, 09:40 UTC | Jul 9, 08:30 UTC | 22h 50m |
| 2026-07-07 | SVR2442 | DYU → ZIA | Jul 7, 12:20 UTC | Jul 8, 10:25 UTC | 22h 5m |
| 2026-07-06 | SVR2441 | ZIA → DYU | Jul 6, 20:40 UTC | Jul 7, 12:30 UTC | 15h 50m |
| 2026-07-03 | SVR8445 | - | Jul 3, 09:15 UTC | Jul 3, 09:25 UTC | 10m |
| 2026-07-01 | SVR8446 | - | Jul 1, 15:40 UTC | Jul 2, 09:55 UTC | 18h 15m |
| 2026-06-30 | SVR8446 | - | Jun 30, 21:05 UTC | Jul 1, 16:05 UTC | 19h 0m |
| 2026-06-26 | SVR2427 | - | Jun 26, 21:50 UTC | Jun 27, 13:35 UTC | 15h 45m |
| 2026-06-26 | SVR2427 | - | Jun 26, 17:50 UTC | Jun 27, 13:35 UTC | 19h 45m |
| 2026-06-25 | SVR2441 | ZIA → DYU | Jun 25, 21:44 UTC | Jun 26, 17:59 UTC | 20h 15m |
| 2026-06-23 | SVR8445 | - | Jun 23, 16:44 UTC | Jun 24, 08:14 UTC | 15h 30m |
| 2026-06-21 | SVR2426 | - | Jun 21, 06:04 UTC | Jun 21, 06:24 UTC | 20m |
| 2026-06-19 | SVR2441 | ZIA → DYU | Jun 19, 21:59 UTC | Jun 19, 22:09 UTC | 10m |
| 2026-06-18 | SVR2428 | - | Jun 18, 07:45 UTC | Jun 18, 08:20 UTC | 35m |
| 2026-06-16 | SVR372 | - | Jun 16, 09:50 UTC | Jun 16, 19:45 UTC | 9h 55m |
| 2026-06-13 | SVR2442 | DYU → ZIA | Jun 13, 23:45 UTC | Jun 14, 07:30 UTC | 7h 45m |
| 2026-06-13 | SVR2442 | DYU → ZIA | Jun 13, 11:25 UTC | Jun 14, 07:30 UTC | 20h 5m |
| 2026-06-10 | SVR2442 | DYU → ZIA | Jun 10, 21:05 UTC | Jun 11, 04:45 UTC | 7h 40m |
| 2026-06-08 | SVR2425 | ZIA → LBD | Jun 8, 23:40 UTC | Jun 9, 00:00 UTC | 20m |
| 2026-06-08 | SVR2426 | LBD → ZIA | Jun 8, 08:45 UTC | Jun 8, 09:35 UTC | 50m |
| 2026-06-07 | SVR8445 | ZIA → DYU | Jun 7, 11:50 UTC | Jun 8, 09:35 UTC | 21h 45m |
| 2026-06-06 | SVR8445 | ZIA → DYU | Jun 6, 13:20 UTC | Jun 7, 12:10 UTC | 22h 50m |
| 2026-06-06 | SVR2428 | DYU → ZIA | Jun 6, 01:10 UTC | Jun 6, 13:30 UTC | 12h 20m |
| 2026-06-05 | SVR8254 | DYU → DME | Jun 5, 06:55 UTC | Jun 5, 14:05 UTC | 7h 10m |
| 2026-06-03 | SVR1344 | MCX → DME | Jun 3, 12:55 UTC | Jun 3, 21:00 UTC | 8h 5m |
| 2026-06-02 | SVR1344 | MCX → DME | Jun 2, 21:40 UTC | Jun 3, 13:25 UTC | 15h 45m |
| 2026-06-01 | SVR2969 | DME → TJU | Jun 1, 20:40 UTC | Jun 1, 21:10 UTC | 30m |
| 2026-05-31 | SVR168 | KGD → DME | May 31, 18:20 UTC | May 31, 20:10 UTC | 1h 50m |
| 2026-05-30 | SVR372 | KGD → DME | May 30, 21:15 UTC | May 31, 16:25 UTC | 19h 10m |
| 2026-05-30 | SVR372 | KGD → DME | May 30, 20:10 UTC | May 31, 16:25 UTC | 20h 15m |
| 2026-05-30 | SVR279 | DME → AER | May 30, 10:35 UTC | May 30, 12:55 UTC | 2h 20m |
| 2026-05-28 | SVR280 | AER → DME | May 28, 15:00 UTC | May 28, 22:05 UTC | 7h 5m |
| 2026-05-27 | SVR168 | KGD → DME | May 27, 18:35 UTC | May 28, 13:10 UTC | 18h 35m |
| 2026-05-27 | SVR168 | KGD → DME | May 27, 18:05 UTC | May 28, 13:10 UTC | 19h 5m |
| 2026-05-27 | SVR168 | KGD → DME | May 27, 10:35 UTC | May 27, 19:55 UTC | 9h 20m |
| 2026-05-25 | SVR168 | KGD → DME | May 25, 20:04 UTC | May 26, 00:35 UTC | 4h 30m |
| 2026-05-25 | SVR167 | DME → KGD | May 25, 15:45 UTC | May 25, 16:30 UTC | 45m |
| 2026-05-24 | SVR371 | DME → KGD | May 24, 21:20 UTC | May 25, 08:35 UTC | 11h 15m |
| 2026-05-23 | SVR168 | KGD → DME | May 23, 19:35 UTC | May 23, 21:20 UTC | 1h 45m |
| 2026-05-23 | SVR372 | KGD → DME | May 23, 11:40 UTC | May 23, 17:40 UTC | 6h 0m |
| 2026-05-22 | SVR371 | DME → KGD | May 22, 21:15 UTC | May 23, 09:55 UTC | 12h 39m |
| 2026-05-19 | SVR372 | KGD → DME | May 19, 10:35 UTC | May 20, 05:55 UTC | 19h 21m |
| 2026-05-19 | SVR372 | KGD → DME | May 19, 10:25 UTC | May 20, 05:55 UTC | 19h 31m |
| 2026-05-17 | SVR387 | DME → OMS | May 17, 22:50 UTC | May 17, 23:35 UTC | 45m |
| 2026-05-15 | SVR9056 | KUF → DME | May 15, 16:50 UTC | May 15, 17:20 UTC | 30m |
| 2026-05-15 | SVR9876 | NOJ → KUF | May 15, 02:55 UTC | May 15, 14:10 UTC | 11h 15m |
| 2026-05-10 | SVR371 | DME → KGD | May 10, 07:25 UTC | May 10, 08:25 UTC | 1h 0m |
| 2026-05-09 | SVR167 | DME → KGD | May 9, 15:25 UTC | May 9, 16:35 UTC | 1h 10m |
| 2026-05-09 | SVR371 | DME → KGD | May 9, 02:30 UTC | May 9, 08:50 UTC | 6h 20m |
| 2026-04-24 | SVR628 | KGD → DME | Apr 24, 12:55 UTC | Apr 24, 15:00 UTC | 2h 5m |
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-73842 page for operator, model, and routing details .