sensors Mode-S transponder

151EC5

ICAO 24-bit transponder address · allocated to Russia

Currently assigned to RA-73413 · AIRBUS A-321

Hex
151EC5
Octal
05217305
Decimal
1,384,133
Country
RU
Tail
RA-73413
Type
A321
Broadcasting now · callsign SBI2506 · 34,000 ft
Flights observed
56
Distinct callsigns
20
Country
RU
Last broadcast
6h ago

Current position

151EC5 is currently broadcasting. Map zoomed to live position.

Country allocation

The ICAO 24-bit address 151EC5 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-05-29 SBI5224 HTA → OVB May 29, 19:00 UTCMay 30, 01:45 UTC6h 45m
2026-05-29 SBI5005 OVB → LED May 29, 09:20 UTCMay 29, 14:15 UTC4h 55m
2026-05-28 SBI5238 KHV → OVB May 28, 16:45 UTCMay 29, 03:45 UTC11h 0m
2026-05-28 SBI5551 OVB → DYU May 28, 07:10 UTCMay 28, 13:50 UTC6h 40m
2026-05-27 SBI5219 OVB → GDX May 27, 16:50 UTCMay 28, 04:20 UTC11h 30m
2026-05-27 SBI2506 OVB → DME May 27, 07:05 UTCMay 27, 08:10 UTC1h 5m
2026-05-26 SBI5237 OVB → KHV May 26, 16:55 UTCMay 27, 03:45 UTC10h 50m
2026-05-25 SBI5258 UUS → OVB May 25, 16:25 UTCMay 26, 04:35 UTC12h 10m
2026-05-25 SBI5552 DYU → OVB May 25, 13:25 UTCMay 25, 13:50 UTC25m
2026-05-24 SBI5552 DYU → OVB May 24, 17:20 UTCMay 25, 13:50 UTC20h 30m
2026-05-24 SBI5237 OVB → KHV May 24, 16:45 UTCMay 25, 13:50 UTC21h 5m
2026-05-24 SBI2507 DME → OVB May 24, 07:35 UTCMay 24, 14:00 UTC6h 25m
2026-05-23 SBI5238 KHV → OVB May 23, 17:00 UTCMay 24, 03:30 UTC10h 30m
2026-05-08 SBI5006 LED → OVB May 8, 16:20 UTCMay 8, 16:30 UTC10m
2026-05-07 SBI5237 OVB → KHV May 7, 17:20 UTCMay 8, 16:30 UTC23h 10m
2026-05-05 SBI5005 OVB → LED May 5, 16:35 UTCMay 6, 10:35 UTC18h 0m
2026-05-05 SBI5555 OVB → LBD May 5, 07:30 UTCMay 5, 08:05 UTC35m
2026-05-04 SBI5257 OVB → UUS May 4, 16:20 UTCMay 5, 04:35 UTC12h 16m
2026-05-04 SBI5552 DYU → OVB May 4, 13:35 UTCMay 4, 14:05 UTC30m
2026-05-03 SBI5219 OVB → GDX May 3, 16:55 UTCMay 4, 04:05 UTC11h 10m
2026-05-03 SBI2506 OVB → DME May 3, 05:25 UTCMay 3, 05:35 UTC10m
2026-05-02 SBI5552 DYU → OVB May 2, 07:15 UTCMay 2, 14:00 UTC6h 45m
2026-05-01 SBI5258 UUS → OVB May 1, 16:15 UTCMay 2, 04:05 UTC11h 50m
2026-04-30 SBI5223 OVB → HTA Apr 30, 19:00 UTCMay 1, 01:40 UTC6h 40m
2026-04-30 SBI5005 OVB → LED Apr 30, 09:55 UTCApr 30, 16:35 UTC6h 40m
2026-04-29 SBI5219 OVB → GDX Apr 29, 17:01 UTCApr 30, 04:10 UTC11h 9m
2026-04-28 SBI5219 OVB → GDX Apr 28, 16:55 UTCApr 29, 04:20 UTC11h 25m
2026-04-28 SBI5556 LBD → OVB Apr 28, 12:10 UTCApr 28, 12:40 UTC30m
2026-04-27 S75223 OVB → HTA Apr 27, 19:00 UTCApr 28, 01:45 UTC6h 45m
2026-04-26 SBI5262 YKS → OVB Apr 26, 17:00 UTCApr 27, 01:40 UTC8h 40m
2026-04-26 SBI2506 OVB → DME Apr 26, 05:25 UTCApr 26, 08:10 UTC2h 45m
2026-04-25 SBI5237 OVB → KHV Apr 25, 16:50 UTCApr 26, 03:25 UTC10h 35m
2026-04-24 SBI5258 UUS → OVB Apr 24, 16:20 UTCApr 25, 04:15 UTC11h 55m
2026-04-24 SBI2506 OVB → DME Apr 24, 05:25 UTCApr 24, 08:10 UTC2h 45m
2026-04-23 SBI5238 KHV → OVB Apr 23, 16:55 UTCApr 24, 03:25 UTC10h 30m
2026-04-23 SBI5555 OVB → LBD Apr 23, 07:01 UTCApr 23, 12:40 UTC5h 40m
2026-04-22 SBI5219 - Apr 22, 16:50 UTCApr 23, 04:10 UTC11h 20m
2026-04-22 SBI2506 OVB → DME Apr 22, 05:20 UTCApr 22, 05:35 UTC15m
2026-04-21 SBI5556 - Apr 21, 12:15 UTCApr 21, 12:45 UTC30m
2026-04-20 SBI5220 GDX → OVB Apr 20, 16:55 UTCApr 21, 04:20 UTC11h 25m
2026-04-20 SBI5551 OVB → DYU Apr 20, 07:00 UTCApr 20, 13:55 UTC6h 55m
2026-04-19 SBI5258 UUS → OVB Apr 19, 16:30 UTCApr 20, 04:25 UTC11h 54m
2026-04-18 SBI5238 KHV → OVB Apr 18, 17:30 UTCApr 19, 04:10 UTC10h 40m
2026-04-18 SBI5003 OVB → LED Apr 18, 08:00 UTCApr 18, 08:40 UTC40m
2026-04-18 SBI5003 OVB → LED Apr 18, 05:25 UTCApr 18, 05:35 UTC10m
2026-04-17 SBI5372 - Apr 17, 09:45 UTCApr 17, 11:15 UTC1h 30m
2026-04-17 SBI5238 KHV → OVB Apr 17, 03:20 UTCApr 17, 03:30 UTC10m
2026-04-17 SBI5238 KHV → OVB Apr 17, 02:55 UTCApr 17, 03:15 UTC20m
2026-04-16 SBI5237 - Apr 16, 16:55 UTCApr 16, 17:10 UTC15m
2026-04-16 SBI5258 UUS → OVB Apr 16, 04:20 UTCApr 16, 04:29 UTC10m

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

Mode-S 151EC5 frequently asked

What is Mode-S code 151EC5?
151EC5 is an ICAO 24-bit transponder address. Allocated to Russia. Assigned to RA-73413.
Where is Mode-S 151EC5 registered?
Mode-S code 151EC5 is allocated to Russia (RU). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 151EC5 broadcasting right now?
Yes. Mode-S 151EC5 is currently airborne.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 151EC5, octal 05217305, decimal 1,384,133.
What flights does 151EC5 operate?
Mode-S 151EC5 has broadcast 20 distinct callsigns, including SBI5238, SBI5237, SBI5258, SBI5219, SBI2506.