sensors Mode-S transponder

151FDD

ICAO 24-bit transponder address · allocated to Russia

Currently assigned to RA-73693 · AIRBUS A-321

Hex
151FDD
Octal
05217735
Decimal
1,384,413
Country
RU
Tail
RA-73693
Type
A321
Broadcasting now · callsign SBI5003 · 34,025 ft
Flights observed
95
Distinct callsigns
20
Country
RU
Last broadcast
2h ago

Current position

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

Country allocation

The ICAO 24-bit address 151FDD 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-30 SBI5003 OVB → LED May 30, 05:20 UTCMay 30, 05:40 UTC20m
2026-05-29 SBI5262 YKS → OVB May 29, 17:15 UTCMay 30, 01:40 UTC8h 25m
2026-05-28 SBI5262 YKS → OVB May 28, 17:15 UTCMay 29, 01:40 UTC8h 25m
2026-05-28 SBI5004 LED → OVB May 28, 11:00 UTCMay 28, 15:05 UTC4h 5m
2026-05-28 SBI5003 OVB → LED May 28, 05:25 UTCMay 28, 07:45 UTC2h 20m
2026-05-27 SBI5224 HTA → OVB May 27, 08:45 UTCMay 28, 01:55 UTC17h 10m
2026-05-26 SBI5241 OVB → MJZ May 26, 22:29 UTCMay 27, 05:04 UTC6h 35m
2026-05-26 SBI5545 OVB → OSS May 26, 08:39 UTCMay 26, 13:54 UTC5h 15m
2026-05-25 SBI5545 OVB → OSS May 25, 12:35 UTCMay 26, 09:04 UTC20h 30m
2026-05-24 SBI5003 OVB → LED May 24, 17:20 UTCMay 25, 12:45 UTC19h 25m
2026-05-24 SBI5003 OVB → LED May 24, 17:10 UTCMay 25, 12:45 UTC19h 35m
2026-05-23 SBI5210 BQS → OVB May 23, 17:50 UTCMay 24, 03:20 UTC9h 30m
2026-05-23 SBI5545 OVB → OSS May 23, 08:45 UTCMay 23, 14:00 UTC5h 15m
2026-05-22 SBI5004 LED → OVB May 22, 14:25 UTCMay 22, 14:40 UTC15m
2026-05-22 SBI5004 LED → OVB May 22, 11:00 UTCMay 22, 11:20 UTC20m
2026-05-22 - - May 22, 07:30 UTCMay 22, 07:40 UTC10m
2026-05-21 SBI5004 LED → OVB May 21, 12:15 UTCMay 22, 07:40 UTC19h 25m
2026-05-21 SBI5004 LED → OVB May 21, 07:40 UTCMay 21, 12:40 UTC5h 0m
2026-05-20 SBI5724 PKX → OVB May 20, 22:50 UTCMay 21, 02:35 UTC3h 45m
2026-05-20 SBI5723 OVB → PKX May 20, 20:40 UTCMay 20, 20:55 UTC15m
2026-05-20 SBI5723 OVB → PKX May 20, 17:15 UTCMay 20, 17:45 UTC30m
2026-05-20 SBI5127 OVB → MRV May 20, 00:35 UTCMay 20, 08:50 UTC8h 16m
2026-05-18 SBI5003 OVB → LED May 18, 14:25 UTCMay 19, 07:55 UTC17h 29m
2026-05-18 SBI5003 OVB → LED May 18, 08:01 UTCMay 18, 14:40 UTC6h 40m
2026-05-17 SBI5262 YKS → OVB May 17, 07:40 UTCMay 18, 01:30 UTC17h 50m
2026-05-16 SBI5004 LED → OVB May 16, 14:25 UTCMay 16, 14:41 UTC15m
2026-05-16 SBI5004 LED → OVB May 16, 10:55 UTCMay 16, 11:16 UTC20m
2026-05-16 SBI5003 OVB → LED May 16, 03:00 UTCMay 16, 08:16 UTC5h 16m
2026-05-15 SBI5209 OVB → BQS May 15, 18:05 UTCMay 15, 18:30 UTC25m
2026-05-14 SBI5127 OVB → MRV May 14, 14:15 UTCMay 15, 09:05 UTC18h 50m
2026-05-14 SBI5127 OVB → MRV May 14, 11:05 UTCMay 15, 09:05 UTC22h 0m
2026-05-14 SBI5004 LED → OVB May 14, 08:00 UTCMay 15, 01:30 UTC17h 30m
2026-05-13 SBI5003 OVB → LED May 13, 13:10 UTCMay 14, 11:10 UTC22h 0m
2026-05-11 SBI5127 OVB → MRV May 11, 01:55 UTCMay 11, 12:05 UTC10h 10m
2026-05-10 SBI5127 OVB → MRV May 10, 12:30 UTCMay 11, 09:00 UTC20h 30m
2026-05-10 SBI5127 OVB → MRV May 10, 10:55 UTCMay 11, 09:00 UTC22h 5m
2026-05-10 SBI5003 OVB → LED May 10, 07:40 UTCMay 10, 08:20 UTC40m
2026-05-09 SBI5262 YKS → OVB May 9, 07:45 UTCMay 10, 01:55 UTC18h 10m
2026-05-08 SBI5262 YKS → OVB May 8, 17:20 UTCMay 9, 12:45 UTC19h 25m
2026-05-08 SBI5004 LED → OVB May 8, 07:29 UTCMay 8, 14:25 UTC6h 55m
2026-05-07 SBI5261 OVB → YKS May 7, 17:10 UTCMay 8, 01:40 UTC8h 29m
2026-05-06 SBI5003 OVB → LED May 6, 07:55 UTCMay 7, 01:40 UTC17h 45m
2026-05-03 SBI5724 PKX → OVB May 3, 22:25 UTCMay 4, 02:39 UTC4h 15m
2026-05-03 SBI5723 OVB → PKX May 3, 16:45 UTCMay 3, 20:00 UTC3h 15m
2026-05-03 SBI5003 OVB → LED May 3, 05:15 UTCMay 3, 12:40 UTC7h 25m
2026-05-02 SBI5262 YKS → OVB May 2, 17:15 UTCMay 3, 01:40 UTC8h 25m
2026-05-02 SBI5003 OVB → LED May 2, 07:40 UTCMay 2, 08:30 UTC50m
2026-05-01 SBI5262 YKS → OVB May 1, 17:05 UTCMay 2, 01:40 UTC8h 35m
2026-04-30 SBI5261 OVB → YKS Apr 30, 17:20 UTCMay 1, 01:55 UTC8h 35m
2026-04-29 SBI5724 PKX → OVB Apr 29, 23:35 UTCApr 30, 12:45 UTC13h 10m

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

Mode-S 151FDD frequently asked

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