sensors Mode-S transponder

151F14

ICAO 24-bit transponder address · allocated to Russia

Currently assigned to RA-73492 · AIRBUS A-320neo

Hex
151F14
Octal
05217424
Decimal
1,384,212
Country
RU
Tail
RA-73492
Type
A20N
No current signal · last broadcast 2h ago
Flights observed
60
Distinct callsigns
8
Country
RU
Last broadcast
2h ago

Last known position

Most recent position reported by Mode-S 151F14.

Country allocation

The ICAO 24-bit address 151F14 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 8 distinct

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-05-29 SBI3045 DME → HTA May 29, 06:15 UTCMay 30, 02:55 UTC20h 40m
2026-05-28 SBI3045 DME → HTA May 28, 19:40 UTCMay 29, 18:00 UTC22h 20m
2026-05-28 SBI3005 DME → YKS May 28, 18:30 UTCMay 28, 18:50 UTC20m
2026-05-27 SBI3006 YKS → DME May 27, 18:30 UTCMay 28, 07:15 UTC12h 45m
2026-05-26 SBI3061 DME → BQS May 26, 21:20 UTCMay 27, 12:30 UTC15h 10m
2026-05-26 SBI3006 YKS → DME May 26, 05:45 UTCMay 26, 22:20 UTC16h 35m
2026-05-25 SBI3006 YKS → DME May 25, 19:30 UTCMay 26, 07:19 UTC11h 50m
2026-05-25 SBI3005 DME → YKS May 25, 18:25 UTCMay 25, 18:40 UTC15m
2026-05-24 SBI3045 DME → HTA May 24, 14:15 UTCMay 25, 03:10 UTC12h 55m
2026-05-24 SBI3006 YKS → DME May 24, 05:40 UTCMay 24, 06:20 UTC40m
2026-05-23 SBI3060 NER → DME May 23, 07:05 UTCMay 24, 06:20 UTC23h 16m
2026-05-23 SBI3060 NER → DME May 23, 06:55 UTCMay 23, 08:15 UTC1h 20m
2026-05-22 SBI3059 DME → NER May 22, 18:50 UTCMay 22, 19:00 UTC10m
2026-05-22 SBI3006 YKS → DME May 22, 06:05 UTCMay 22, 07:35 UTC1h 30m
2026-05-20 SBI3046 HTA → DME May 20, 07:05 UTCMay 21, 02:55 UTC19h 50m
2026-05-20 SBI3046 HTA → DME May 20, 05:45 UTCMay 21, 02:55 UTC21h 10m
2026-05-19 SBI3045 DME → HTA May 19, 19:35 UTCMay 20, 17:55 UTC22h 21m
2026-05-19 SBI3005 DME → YKS May 19, 02:00 UTCMay 19, 19:50 UTC17h 50m
2026-05-18 SBI3046 HTA → DME May 18, 23:40 UTCMay 19, 19:50 UTC20h 10m
2026-05-16 SBI3060 NER → DME May 16, 07:41 UTCMay 16, 09:10 UTC1h 30m
2026-05-15 SBI3060 NER → DME May 15, 11:50 UTCMay 16, 09:10 UTC21h 20m
2026-05-12 SBI3046 HTA → DME May 12, 04:10 UTCMay 12, 04:50 UTC40m
2026-05-11 SBI3045 DME → HTA May 11, 14:25 UTCMay 12, 03:25 UTC13h 1m
2026-05-11 SBI3046 HTA → DME May 11, 01:34 UTCMay 11, 15:35 UTC14h 0m
2026-05-10 SBI3045 DME → HTA May 10, 17:15 UTCMay 11, 15:35 UTC22h 20m
2026-05-10 SBI3046 HTA → DME May 10, 14:25 UTCMay 11, 02:55 UTC12h 30m
2026-05-07 SBI3046 HTA → DME May 7, 23:55 UTCMay 8, 02:14 UTC2h 20m
2026-05-03 SBI3006 YKS → DME May 3, 19:34 UTCMay 4, 07:15 UTC11h 40m
2026-05-01 SBI3046 HTA → DME May 1, 22:10 UTCMay 2, 03:00 UTC4h 50m
2026-05-01 SBI3006 YKS → DME May 1, 06:00 UTCMay 1, 07:35 UTC1h 35m
2026-04-28 SBI3045 DME → HTA Apr 28, 15:20 UTCApr 29, 00:30 UTC9h 10m
2026-04-28 SBI3046 HTA → DME Apr 28, 03:05 UTCApr 29, 00:30 UTC21h 25m
2026-04-28 SBI3046 HTA → DME Apr 28, 02:40 UTCApr 29, 00:30 UTC21h 50m
2026-04-27 SBI3045 DME → HTA Apr 27, 19:20 UTCApr 28, 18:00 UTC22h 40m
2026-04-27 SBI3045 DME → HTA Apr 27, 17:40 UTCApr 28, 15:35 UTC21h 55m
2026-04-27 SBI3046 HTA → DME Apr 27, 04:05 UTCApr 27, 04:30 UTC25m
2026-04-26 SBI3046 HTA → DME Apr 26, 15:35 UTCApr 27, 03:20 UTC11h 45m
2026-04-24 SBI3006 YKS → DME Apr 24, 19:30 UTCApr 25, 07:15 UTC11h 45m
2026-04-24 SBI3006 YKS → DME Apr 24, 07:50 UTCApr 24, 08:00 UTC10m
2026-04-24 SBI3006 YKS → DME Apr 24, 05:35 UTCApr 24, 06:20 UTC45m
2026-04-23 SBI3006 YKS → DME Apr 23, 07:55 UTCApr 23, 08:15 UTC20m
2026-04-22 SBI3005 DME → YKS Apr 22, 18:10 UTCApr 23, 06:25 UTC12h 15m
2026-04-21 SBI3060 NER → DME Apr 21, 06:50 UTCApr 21, 19:00 UTC12h 10m
2026-04-20 SBI3060 NER → DME Apr 20, 19:05 UTCApr 21, 19:00 UTC23h 55m
2026-04-20 SBI3060 NER → DME Apr 20, 18:55 UTCApr 21, 15:40 UTC20h 45m
2026-04-20 SBI3006 YKS → DME Apr 20, 05:50 UTCApr 20, 07:15 UTC1h 25m
2026-04-19 SBI3005 DME → YKS Apr 19, 18:30 UTCApr 19, 18:40 UTC10m
2026-04-18 SBI3062 BQS → DME Apr 18, 21:15 UTCApr 19, 12:05 UTC14h 50m
2026-04-18 SBI3006 YKS → DME Apr 18, 08:10 UTCApr 18, 08:20 UTC10m
2026-04-18 SBI3006 YKS → DME Apr 18, 06:05 UTCApr 18, 07:05 UTC1h 0m

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

Mode-S 151F14 frequently asked

What is Mode-S code 151F14?
151F14 is an ICAO 24-bit transponder address. Allocated to Russia. Assigned to RA-73492.
Where is Mode-S 151F14 registered?
Mode-S code 151F14 is allocated to Russia (RU). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 151F14 broadcasting right now?
No active broadcast right now. Last signal was 2h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 151F14, octal 05217424, decimal 1,384,212.
What flights does 151F14 operate?
Mode-S 151F14 has broadcast 8 distinct callsigns, including SBI3006, SBI3046, SBI3045, SBI3060, SBI3005.