sensors Mode-S transponder

151E5E

ICAO 24-bit transponder address · allocated to Russia

Currently assigned to RA-73310 · AIRBUS A-321

Hex
151E5E
Octal
05217136
Decimal
1,384,030
Country
RU
Tail
RA-73310
Type
A321
No current signal · last broadcast 1h ago
Flights observed
126
Distinct callsigns
20
Country
RU
Last broadcast
1h ago

Last known position

Most recent position reported by Mode-S 151E5E.

Country allocation

The ICAO 24-bit address 151E5E 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

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-06-06 SBI5003 OVB → LED Jun 6, 10:00 UTCJun 6, 10:20 UTC20m
2026-06-05 SBI5724 PKX → OVB Jun 5, 22:30 UTCJun 6, 02:20 UTC3h 50m
2026-06-05 SBI5723 OVB → PKX Jun 5, 20:05 UTCJun 5, 20:15 UTC10m
2026-06-05 SBI5723 OVB → PKX Jun 5, 16:50 UTCJun 5, 17:25 UTC35m
2026-06-05 SBI5541 OVB → FRU Jun 5, 08:25 UTCJun 5, 12:55 UTC4h 30m
2026-06-04 SBI5724 PKX → OVB Jun 4, 22:25 UTCJun 5, 02:20 UTC3h 55m
2026-06-04 SBI5723 OVB → PKX Jun 4, 20:05 UTCJun 4, 20:15 UTC10m
2026-06-04 SBI5723 OVB → PKX Jun 4, 16:50 UTCJun 4, 17:25 UTC35m
2026-06-04 SBI5004 LED → OVB Jun 4, 11:00 UTCJun 4, 11:20 UTC20m
2026-06-04 SBI5003 OVB → LED Jun 4, 07:35 UTCJun 4, 08:15 UTC40m
2026-06-03 SBI5724 PKX → OVB Jun 3, 22:25 UTCJun 4, 02:25 UTC4h 0m
2026-06-03 SBI5723 OVB → PKX Jun 3, 20:10 UTCJun 3, 20:20 UTC10m
2026-06-03 SBI5723 OVB → PKX Jun 3, 17:05 UTCJun 3, 17:40 UTC35m
2026-06-02 SBI5724 PKX → OVB Jun 2, 22:35 UTCJun 3, 02:35 UTC4h 0m
2026-06-02 SBI5723 OVB → PKX Jun 2, 20:10 UTCJun 2, 20:20 UTC10m
2026-06-02 SBI5723 OVB → PKX Jun 2, 17:00 UTCJun 2, 17:35 UTC35m
2026-06-01 SBI5723 OVB → PKX Jun 1, 16:50 UTCJun 2, 02:15 UTC9h 25m
2026-05-31 SBI5724 PKX → OVB May 31, 16:40 UTCJun 1, 02:45 UTC10h 5m
2026-05-30 SBI5724 PKX → OVB May 30, 22:20 UTCMay 31, 12:50 UTC14h 30m
2026-05-30 SBI5723 OVB → PKX May 30, 19:55 UTCMay 30, 20:05 UTC10m
2026-05-30 SBI5723 OVB → PKX May 30, 16:50 UTCMay 30, 17:20 UTC30m
2026-05-29 SBI5724 PKX → OVB May 29, 22:15 UTCMay 30, 02:20 UTC4h 5m
2026-05-29 SBI5723 OVB → PKX May 29, 20:00 UTCMay 29, 20:10 UTC10m
2026-05-29 SBI5723 OVB → PKX May 29, 16:40 UTCMay 29, 17:15 UTC35m
2026-05-28 SBI5541 OVB → FRU May 28, 08:35 UTCMay 28, 12:40 UTC4h 5m
2026-05-28 SBI5724 PKX → OVB May 28, 00:00 UTCMay 28, 04:00 UTC4h 0m
2026-05-27 SBI5723 OVB → PKX May 27, 21:45 UTCMay 27, 21:55 UTC10m
2026-05-27 SBI5723 OVB → PKX May 27, 18:35 UTCMay 27, 19:10 UTC35m
2026-05-27 SBI5128 MRV → OVB May 27, 11:10 UTCMay 27, 11:20 UTC10m
2026-05-26 SBI5724 PKX → OVB May 26, 22:25 UTCMay 27, 02:24 UTC4h 0m
2026-05-26 SBI5723 OVB → PKX May 26, 20:20 UTCMay 26, 20:34 UTC15m
2026-05-26 SBI5723 OVB → PKX May 26, 16:59 UTCMay 26, 17:35 UTC35m
2026-05-26 SBI5004 LED → OVB May 26, 11:00 UTCMay 26, 11:20 UTC20m
2026-05-26 SBI5003 OVB → LED May 26, 07:29 UTCMay 26, 07:59 UTC30m
2026-05-25 SBI5724 PKX → OVB May 25, 22:30 UTCMay 26, 02:15 UTC3h 45m
2026-05-25 SBI5723 OVB → PKX May 25, 16:55 UTCMay 25, 20:30 UTC3h 35m
2026-05-25 SBI5036 KZN → OVB May 25, 08:25 UTCMay 25, 11:05 UTC2h 40m
2026-05-24 SBI5723 OVB → PKX May 24, 16:40 UTCMay 25, 02:20 UTC9h 40m
2026-05-23 SBI5724 PKX → OVB May 23, 16:55 UTCMay 24, 02:40 UTC9h 46m
2026-05-22 SBI5723 OVB → PKX May 22, 16:45 UTCMay 23, 02:35 UTC9h 49m
2026-05-21 SBI5724 PKX → OVB May 21, 22:30 UTCMay 22, 02:30 UTC4h 0m
2026-05-21 SBI5723 OVB → PKX May 21, 20:15 UTCMay 21, 20:25 UTC10m
2026-05-21 SBI5723 OVB → PKX May 21, 16:50 UTCMay 21, 17:20 UTC30m
2026-05-20 SBI5545 OVB → OSS May 20, 08:35 UTCMay 20, 08:55 UTC20m
2026-05-19 SBI5541 OVB → FRU May 19, 08:30 UTCMay 20, 01:45 UTC17h 15m
2026-05-19 SBI5724 PKX → OVB May 19, 02:20 UTCMay 20, 01:30 UTC23h 10m
2026-05-18 SBI5724 PKX → OVB May 18, 22:55 UTCMay 19, 17:40 UTC18h 45m
2026-05-18 SBI5723 OVB → PKX May 18, 20:45 UTCMay 18, 20:55 UTC10m
2026-05-18 SBI5723 OVB → PKX May 18, 17:30 UTCMay 18, 18:05 UTC35m
2026-05-17 SBI5724 PKX → OVB May 17, 22:30 UTCMay 18, 12:05 UTC13h 35m

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-73310 page for operator, model, and routing details .

Mode-S 151E5E frequently asked

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