Apparatus

Try JFK, AAL1290, BAW, or N225AN.

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
No current signal · last broadcast 19h ago
Flights observed
50
Distinct callsigns
3
Country
RU
Last broadcast
19h ago

Last known position

Most recent position reported by Mode-S 151E72.

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 3 distinct

Callsign Airline Flights Last seen
RWZ3202 Red Wings 36 2026-05-23
RWZ3201 Red Wings 13 2026-05-29
RWZ3206 - 1 2026-04-14

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-05-29 RWZ3201 DME → CXR May 29, 02:20 UTCMay 29, 10:55 UTC8h 35m
2026-05-23 RWZ3202 CXR → DME May 23, 10:10 UTCMay 23, 18:40 UTC8h 30m
2026-05-22 RWZ3201 DME → CXR May 22, 02:15 UTCMay 22, 05:20 UTC3h 5m
2026-05-20 RWZ3202 CXR → DME May 20, 12:30 UTCMay 20, 21:15 UTC8h 45m
2026-05-19 RWZ3201 DME → CXR May 19, 02:30 UTCMay 19, 09:35 UTC7h 5m
2026-05-13 RWZ3202 CXR → DME May 13, 18:15 UTCMay 13, 18:25 UTC10m
2026-05-12 RWZ3201 DME → CXR May 12, 03:00 UTCMay 12, 06:00 UTC3h 0m
2026-05-10 RWZ3202 CXR → DME May 10, 04:00 UTCMay 10, 21:14 UTC17h 15m
2026-05-10 RWZ3202 CXR → DME May 10, 00:20 UTCMay 10, 21:14 UTC20h 55m
2026-05-09 RWZ3202 CXR → DME May 9, 18:50 UTCMay 10, 16:44 UTC21h 55m
2026-05-09 RWZ3202 CXR → DME May 9, 14:35 UTCMay 10, 14:30 UTC23h 55m
2026-05-09 RWZ3202 CXR → DME May 9, 12:35 UTCMay 10, 12:30 UTC23h 55m
2026-05-09 RWZ3202 CXR → DME May 9, 10:35 UTCMay 10, 06:35 UTC20h 0m
2026-05-09 RWZ3202 CXR → DME May 9, 10:25 UTCMay 10, 06:35 UTC20h 10m
2026-05-08 RWZ3201 DME → CXR May 8, 03:49 UTCMay 8, 07:50 UTC4h 0m
2026-05-06 RWZ3202 CXR → DME May 6, 09:25 UTCMay 6, 18:45 UTC9h 19m
2026-05-05 RWZ3201 DME → CXR May 5, 03:10 UTCMay 5, 07:05 UTC3h 55m
2026-05-03 RWZ3202 CXR → DME May 3, 04:05 UTCMay 3, 16:15 UTC12h 10m
2026-05-02 RWZ3202 CXR → DME May 2, 18:45 UTCMay 3, 16:15 UTC21h 29m
2026-05-02 RWZ3202 CXR → DME May 2, 14:35 UTCMay 3, 14:30 UTC23h 54m
2026-05-02 RWZ3202 CXR → DME May 2, 12:35 UTCMay 3, 12:30 UTC23h 54m
2026-05-02 RWZ3202 CXR → DME May 2, 10:35 UTCMay 3, 07:05 UTC20h 29m
2026-05-02 RWZ3202 CXR → DME May 2, 10:15 UTCMay 3, 07:05 UTC20h 49m
2026-05-01 RWZ3201 DME → CXR May 1, 02:15 UTCMay 1, 06:00 UTC3h 45m
2026-04-29 RWZ3202 CXR → DME Apr 29, 09:45 UTCApr 29, 18:40 UTC8h 55m
2026-04-28 RWZ3201 DME → CXR Apr 28, 03:25 UTCApr 28, 07:20 UTC3h 55m
2026-04-26 RWZ3202 CXR → DME Apr 26, 03:50 UTCApr 26, 20:50 UTC17h 0m
2026-04-25 RWZ3202 CXR → DME Apr 25, 18:45 UTCApr 26, 16:20 UTC21h 35m
2026-04-25 RWZ3202 CXR → DME Apr 25, 14:35 UTCApr 26, 14:30 UTC23h 55m
2026-04-25 RWZ3202 CXR → DME Apr 25, 12:35 UTCApr 26, 12:30 UTC23h 55m
2026-04-25 RWZ3202 CXR → DME Apr 25, 10:35 UTCApr 26, 06:55 UTC20h 20m
2026-04-25 RWZ3202 CXR → DME Apr 25, 09:45 UTCApr 26, 06:55 UTC21h 10m
2026-04-22 RWZ3202 CXR → DME Apr 22, 09:40 UTCApr 22, 18:20 UTC8h 40m
2026-04-21 RWZ3201 DME → CXR Apr 21, 02:45 UTCApr 21, 05:05 UTC2h 20m
2026-04-19 RWZ3202 CXR → DME Apr 19, 04:00 UTCApr 19, 20:35 UTC16h 35m
2026-04-19 RWZ3202 CXR → DME Apr 19, 00:45 UTCApr 19, 20:35 UTC19h 50m
2026-04-18 RWZ3202 CXR → DME Apr 18, 18:35 UTCApr 19, 16:05 UTC21h 30m
2026-04-18 RWZ3202 CXR → DME Apr 18, 12:35 UTCApr 19, 12:25 UTC23h 50m
2026-04-18 RWZ3202 CXR → DME Apr 18, 10:35 UTCApr 19, 07:35 UTC21h 0m
2026-04-18 RWZ3202 CXR → DME Apr 18, 09:40 UTCApr 19, 07:35 UTC21h 55m
2026-04-17 RWZ3201 DME → CXR Apr 17, 03:20 UTCApr 17, 04:45 UTC1h 26m
2026-04-17 RWZ3201 DME → CXR Apr 17, 02:25 UTCApr 17, 03:15 UTC50m
2026-04-16 RWZ3201 DME → CXR Apr 16, 22:34 UTCApr 16, 23:00 UTC25m
2026-04-15 RWZ3202 CXR → DME Apr 15, 18:00 UTCApr 15, 18:40 UTC40m
2026-04-15 RWZ3202 CXR → DME Apr 15, 13:01 UTCApr 15, 14:10 UTC1h 10m
2026-04-15 RWZ3202 CXR → DME Apr 15, 11:00 UTCApr 15, 12:55 UTC1h 55m
2026-04-15 RWZ3202 CXR → DME Apr 15, 09:40 UTCApr 15, 10:55 UTC1h 15m
2026-04-14 RWZ3206 - Apr 14, 18:35 UTCApr 14, 18:45 UTC10m
2026-04-14 RWZ3201 DME → CXR Apr 14, 05:15 UTCApr 14, 05:25 UTC10m
2026-04-12 RWZ3202 - Apr 12, 19:55 UTCApr 12, 20:15 UTC20m

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 .

Mode-S 151E72 frequently asked

What is Mode-S code 151E72?
151E72 is an ICAO 24-bit transponder address. Allocated to Russia. Assigned to RA-73330.
Where is Mode-S 151E72 registered?
Mode-S code 151E72 is allocated to Russia (RU). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 151E72 broadcasting right now?
No active broadcast right now. Last signal was 19h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 151E72, octal 05217162, decimal 1,384,050.
What flights does 151E72 operate?
Mode-S 151E72 has broadcast 3 distinct callsigns, including RWZ3202, RWZ3201, RWZ3206.