sensors Mode-S transponder
151E72
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73330 · BOEING 777-200
- Hex
- 151E72
- Octal
- 05217162
- Decimal
- 1,384,050
- Country
- RU
- Tail
- RA-73330
- Type
- B772
- Flights observed
- 148
- Distinct callsigns
- 5
- Country
- RU
- Last broadcast
- Jul 26, 20:30 UTC
Last known position
Country allocation
The ICAO 24-bit address 151E72 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 5 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | RWZ3202 | CXR → DME | Jul 26, 00:45 UTC | Jul 26, 20:30 UTC | 19h 46m |
| 2026-07-25 | RWZ3202 | CXR → DME | Jul 25, 18:05 UTC | Jul 26, 16:30 UTC | 22h 26m |
| 2026-07-25 | RWZ3202 | CXR → DME | Jul 25, 12:35 UTC | Jul 26, 12:30 UTC | 23h 56m |
| 2026-07-25 | RWZ3202 | CXR → DME | Jul 25, 10:35 UTC | Jul 26, 07:45 UTC | 21h 11m |
| 2026-07-25 | RWZ3202 | CXR → DME | Jul 25, 10:20 UTC | Jul 26, 07:45 UTC | 21h 26m |
| 2026-07-25 | RWZ3202 | CXR → DME | Jul 25, 05:45 UTC | Jul 26, 00:50 UTC | 19h 5m |
| 2026-07-24 | RWZ3205 | SVX → CXR | Jul 24, 11:10 UTC | Jul 25, 10:30 UTC | 23h 20m |
| 2026-07-23 | 00000000 | - | Jul 23, 22:45 UTC | Jul 24, 11:25 UTC | 12h 40m |
| 2026-07-21 | RWZ3202 | - | Jul 21, 23:45 UTC | Jul 22, 18:10 UTC | 18h 25m |
| 2026-07-21 | RWZ3205 | SVX → CXR | Jul 21, 11:00 UTC | Jul 22, 10:25 UTC | 23h 25m |
| 2026-07-21 | RWZ3205 | SVX → CXR | Jul 21, 06:35 UTC | Jul 22, 05:05 UTC | 22h 30m |
| 2026-07-21 | RWZ3201 | DME → CXR | Jul 21, 06:25 UTC | Jul 21, 23:55 UTC | 17h 30m |
| 2026-07-20 | RWZ3201 | DME → CXR | Jul 20, 23:15 UTC | Jul 21, 11:20 UTC | 12h 4m |
| 2026-07-19 | RWZ3202 | - | Jul 19, 00:35 UTC | Jul 19, 20:10 UTC | 19h 35m |
| 2026-07-19 | RWZ3202 | - | Jul 19, 00:15 UTC | Jul 19, 20:10 UTC | 19h 55m |
| 2026-07-18 | RWZ3202 | - | Jul 18, 13:00 UTC | Jul 19, 12:30 UTC | 23h 30m |
| 2026-07-18 | RWZ3202 | - | Jul 18, 10:35 UTC | Jul 19, 07:45 UTC | 21h 10m |
| 2026-07-18 | RWZ3202 | - | Jul 18, 10:05 UTC | Jul 19, 07:45 UTC | 21h 40m |
| 2026-07-18 | RWZ3202 | - | Jul 18, 05:00 UTC | Jul 19, 00:50 UTC | 19h 50m |
| 2026-07-17 | RWZ3202 | - | Jul 17, 12:35 UTC | Jul 18, 12:30 UTC | 23h 56m |
| 2026-07-17 | RWZ3206 | CXR → SVX | Jul 17, 10:35 UTC | Jul 18, 10:30 UTC | 23h 56m |
| 2026-07-17 | RWZ3206 | CXR → SVX | Jul 17, 10:25 UTC | Jul 18, 05:20 UTC | 18h 56m |
| 2026-07-16 | RWZ3206 | CXR → SVX | Jul 16, 22:59 UTC | Jul 17, 14:20 UTC | 15h 20m |
| 2026-07-15 | RWZ3202 | - | Jul 15, 04:45 UTC | Jul 15, 18:00 UTC | 13h 15m |
| 2026-07-14 | RWZ3202 | - | Jul 14, 11:15 UTC | Jul 15, 10:30 UTC | 23h 14m |
| 2026-07-14 | RWZ3201 | - | Jul 14, 06:35 UTC | Jul 15, 05:05 UTC | 22h 29m |
| 2026-07-14 | RWZ3201 | - | Jul 14, 06:25 UTC | Jul 14, 11:30 UTC | 5h 5m |
| 2026-07-12 | RWZ3201 | - | Jul 12, 04:10 UTC | Jul 12, 16:20 UTC | 12h 10m |
| 2026-07-11 | RWZ3201 | - | Jul 11, 14:35 UTC | Jul 12, 14:30 UTC | 23h 55m |
| 2026-07-11 | RWZ3201 | - | Jul 11, 12:35 UTC | Jul 12, 12:30 UTC | 23h 55m |
| 2026-07-11 | RWZ3202 | - | Jul 11, 07:05 UTC | Jul 12, 06:30 UTC | 23h 25m |
| 2026-07-10 | RWZ3201 | - | Jul 10, 05:40 UTC | Jul 10, 10:35 UTC | 4h 55m |
| 2026-07-08 | RWZ3202 | - | Jul 8, 04:40 UTC | Jul 8, 17:40 UTC | 13h 0m |
| 2026-07-07 | RWZ3202 | - | Jul 7, 11:30 UTC | Jul 8, 10:30 UTC | 23h 0m |
| 2026-07-07 | RWZ3206 | - | Jul 7, 06:35 UTC | Jul 8, 05:00 UTC | 22h 25m |
| 2026-07-07 | RWZ3206 | - | Jul 7, 06:25 UTC | Jul 7, 12:05 UTC | 5h 40m |
| 2026-07-04 | RWZ3202 | - | Jul 4, 18:35 UTC | Jul 5, 16:25 UTC | 21h 50m |
| 2026-07-04 | RWZ3202 | - | Jul 4, 18:20 UTC | Jul 5, 16:25 UTC | 22h 5m |
| 2026-07-04 | RWZ3202 | - | Jul 4, 14:35 UTC | Jul 5, 14:30 UTC | 23h 55m |
| 2026-07-04 | RWZ3202 | - | Jul 4, 12:35 UTC | Jul 5, 12:30 UTC | 23h 55m |
| 2026-07-04 | RWZ3202 | - | Jul 4, 10:40 UTC | Jul 5, 08:05 UTC | 21h 25m |
| 2026-07-04 | RWZ3202 | - | Jul 4, 06:35 UTC | Jul 5, 01:15 UTC | 18h 40m |
| 2026-07-04 | RWZ3202 | - | Jul 4, 04:35 UTC | Jul 5, 01:15 UTC | 20h 40m |
| 2026-07-04 | RWZ3202 | - | Jul 4, 02:35 UTC | Jul 5, 01:15 UTC | 22h 40m |
| 2026-07-03 | RWZ3205 | - | Jul 3, 10:35 UTC | Jul 4, 06:50 UTC | 20h 15m |
| 2026-07-03 | RWZ3205 | - | Jul 3, 10:25 UTC | Jul 4, 06:50 UTC | 20h 25m |
| 2026-07-03 | RWZ3201 | - | Jul 3, 04:35 UTC | Jul 4, 04:30 UTC | 23h 55m |
| 2026-07-02 | RWZ3201 | - | Jul 2, 22:45 UTC | Jul 3, 10:50 UTC | 12h 5m |
| 2026-07-01 | RWZ3202 | - | Jul 1, 05:00 UTC | Jul 1, 13:45 UTC | 8h 45m |
| 2026-06-30 | RWZ3202 | - | Jun 30, 11:50 UTC | Jul 1, 10:30 UTC | 22h 40m |
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-73330 page for operator, model, and routing details .