sensors Mode-S transponder
152064
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73828 · AIRBUS A-320
- Hex
- 152064
- Octal
- 05220144
- Decimal
- 1,384,548
- Country
- RU
- Tail
- RA-73828
- Type
- A320
- Flights observed
- 50
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 5h ago
Last known position
Country allocation
The ICAO 24-bit address 152064 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 |
|---|---|---|---|
| RA73828 | - | 6 | 2026-05-06 |
| SVR106 | - | 4 | 2026-07-12 |
| SVR628 | Ural Airlines | 3 | 2026-05-20 |
| SVR627 | Ural Airlines | 3 | 2026-05-20 |
| SVR624 | - | 3 | 2026-07-18 |
| SVR403 | - | 3 | 2026-07-03 |
| SVR366 | - | 3 | 2026-07-15 |
| SVR9138 | - | 2 | 2026-04-14 |
| SVR9137 | - | 2 | 2026-04-14 |
| SVR623 | - | 2 | 2026-06-30 |
| SVR404 | - | 2 | 2026-06-14 |
| SVR391 | - | 2 | 2026-06-16 |
| SVR093 | Ural Airlines | 2 | 2026-06-02 |
| SVR9655 | Ural Airlines | 1 | 2026-05-14 |
| SVR503 | - | 1 | 2026-07-01 |
| SVR392 | Ural Airlines | 1 | 2026-05-08 |
| SVR321 | Ural Airlines | 1 | 2026-05-15 |
| SVR272 | Ural Airlines | 1 | 2026-05-22 |
| SVR266 | Ural Airlines | 1 | 2026-05-23 |
| SVR264 | Ural Airlines | 1 | 2026-05-25 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-18 | SVR624 | - | Jul 18, 00:29 UTC | Jul 18, 01:15 UTC | 45m |
| 2026-07-15 | SVR366 | - | Jul 15, 07:55 UTC | Jul 15, 08:45 UTC | 50m |
| 2026-07-12 | SVR106 | - | Jul 12, 04:10 UTC | Jul 12, 04:55 UTC | 45m |
| 2026-07-09 | SVR106 | - | Jul 9, 20:20 UTC | Jul 10, 02:05 UTC | 5h 45m |
| 2026-07-03 | SVR403 | - | Jul 3, 13:50 UTC | Jul 3, 14:25 UTC | 35m |
| 2026-07-01 | SVR503 | - | Jul 1, 19:05 UTC | Jul 2, 13:20 UTC | 18h 15m |
| 2026-07-01 | SVR403 | - | Jul 1, 16:05 UTC | Jul 1, 16:55 UTC | 50m |
| 2026-06-30 | SVR623 | - | Jun 30, 07:05 UTC | Jun 30, 07:55 UTC | 50m |
| 2026-06-28 | SVR623 | - | Jun 28, 04:50 UTC | Jun 28, 05:15 UTC | 25m |
| 2026-06-25 | SVR366 | - | Jun 25, 16:05 UTC | Jun 26, 08:24 UTC | 16h 20m |
| 2026-06-19 | SVR106 | - | Jun 19, 21:49 UTC | Jun 20, 14:14 UTC | 16h 25m |
| 2026-06-16 | SVR391 | - | Jun 16, 10:15 UTC | Jun 16, 11:15 UTC | 1h 0m |
| 2026-06-14 | SVR404 | - | Jun 14, 08:10 UTC | Jun 14, 18:05 UTC | 9h 55m |
| 2026-06-13 | SVR404 | - | Jun 13, 18:30 UTC | Jun 14, 17:00 UTC | 22h 30m |
| 2026-06-13 | SVR149 | SVX → GDZ | Jun 13, 03:45 UTC | Jun 13, 18:30 UTC | 14h 44m |
| 2026-06-05 | SVR209 | SVX → KRR | Jun 5, 20:25 UTC | Jun 6, 07:45 UTC | 11h 20m |
| 2026-06-05 | SVR106 | IKT → DME | Jun 5, 05:05 UTC | Jun 5, 12:50 UTC | 7h 45m |
| 2026-06-04 | SVR094 | HTA → DME | Jun 4, 02:20 UTC | Jun 4, 03:00 UTC | 40m |
| 2026-06-02 | SVR093 | DME → HTA | Jun 2, 18:15 UTC | Jun 2, 18:35 UTC | 20m |
| 2026-06-01 | SVR093 | DME → HTA | Jun 1, 18:10 UTC | Jun 1, 18:30 UTC | 20m |
| 2026-05-30 | SVR261 | DME → SVX | May 30, 11:10 UTC | May 30, 11:30 UTC | 20m |
| 2026-05-28 | SVR366 | VVO → IKT | May 28, 15:40 UTC | May 29, 08:35 UTC | 16h 55m |
| 2026-05-25 | SVR264 | SVX → DME | May 25, 18:40 UTC | May 26, 03:05 UTC | 8h 24m |
| 2026-05-25 | SVR403 | SVX → KGD | May 25, 11:35 UTC | May 25, 14:40 UTC | 3h 5m |
| 2026-05-23 | SVR266 | SVX → DME | May 23, 14:50 UTC | May 24, 03:20 UTC | 12h 30m |
| 2026-05-22 | SVR173 | SVX → KHV | May 22, 16:10 UTC | May 23, 15:00 UTC | 22h 49m |
| 2026-05-22 | SVR272 | SVX → DME | May 22, 05:05 UTC | May 22, 16:20 UTC | 11h 15m |
| 2026-05-20 | SVR628 | KGD → DME | May 20, 13:25 UTC | May 20, 14:45 UTC | 1h 20m |
| 2026-05-20 | SVR627 | DME → KGD | May 20, 11:20 UTC | May 20, 12:05 UTC | 45m |
| 2026-05-18 | SVR205 | SVX → MRV | May 18, 09:40 UTC | May 18, 10:40 UTC | 1h 0m |
| 2026-05-17 | SVR624 | SVX → HTA | May 17, 00:15 UTC | May 17, 06:50 UTC | 6h 35m |
| 2026-05-15 | SVR321 | SVX → AER | May 15, 16:40 UTC | May 15, 17:40 UTC | 1h 0m |
| 2026-05-14 | SVR9655 | DME → HTA | May 14, 18:10 UTC | May 15, 17:00 UTC | 22h 49m |
| 2026-05-08 | SVR392 | KGD → LED | May 8, 10:14 UTC | May 8, 11:34 UTC | 1h 20m |
| 2026-05-07 | SVR391 | LED → KGD | May 7, 20:20 UTC | May 8, 08:55 UTC | 12h 35m |
| 2026-05-06 | RA73828 | - | May 6, 12:55 UTC | May 6, 13:40 UTC | 45m |
| 2026-05-03 | RA73828 | - | May 3, 06:00 UTC | May 3, 13:00 UTC | 7h 0m |
| 2026-04-30 | SVR628 | KGD → DME | Apr 30, 13:05 UTC | Apr 30, 22:10 UTC | 9h 5m |
| 2026-04-30 | SVR627 | DME → KGD | Apr 30, 10:40 UTC | Apr 30, 10:55 UTC | 15m |
| 2026-04-29 | RA73828 | - | Apr 29, 13:55 UTC | Apr 29, 14:30 UTC | 35m |
| 2026-04-23 | SVR624 | SVX → HTA | Apr 23, 23:00 UTC | Apr 24, 00:40 UTC | 1h 40m |
| 2026-04-18 | SVR628 | KGD → DME | Apr 18, 12:35 UTC | Apr 18, 14:40 UTC | 2h 5m |
| 2026-04-18 | SVR627 | DME → KGD | Apr 18, 10:20 UTC | Apr 18, 10:55 UTC | 35m |
| 2026-04-14 | SVR9137 | - | Apr 14, 22:55 UTC | Apr 14, 23:15 UTC | 20m |
| 2026-04-14 | SVR9137 | - | Apr 14, 22:25 UTC | Apr 14, 22:50 UTC | 25m |
| 2026-04-14 | SVR9138 | - | Apr 14, 16:50 UTC | Apr 14, 18:20 UTC | 1h 30m |
| 2026-04-14 | SVR9138 | - | Apr 14, 14:50 UTC | Apr 14, 16:45 UTC | 1h 55m |
| 2026-04-14 | RA73828 | - | Apr 14, 07:00 UTC | Apr 14, 07:10 UTC | 10m |
| 2026-04-13 | RA73828 | - | Apr 13, 08:20 UTC | Apr 13, 08:45 UTC | 25m |
| 2026-04-13 | RA73828 | - | Apr 13, 08:00 UTC | Apr 13, 08:15 UTC | 15m |
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-73828 page for operator, model, and routing details .