sensors Mode-S transponder
155C5B
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-89179 · SUKHOI Superjet 100-95
- Hex
- 155C5B
- Octal
- 05256133
- Decimal
- 1,399,899
- Country
- RU
- Tail
- RA-89179
- Type
- SU95
- Flights observed
- 52
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 4h ago
Last known position
Country allocation
The ICAO 24-bit address 155C5B 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
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| AZO6068 | Azimuth Airlines | 3 | 2026-06-13 |
| AZO6216 | Azimuth Airlines | 2 | 2026-06-11 |
| AZO6215 | Azimuth Airlines | 2 | 2026-06-11 |
| AZO6074 | - | 2 | 2026-06-18 |
| AZO6073 | Azimuth Airlines | 2 | 2026-06-18 |
| AZO6066 | Azimuth Airlines | 2 | 2026-06-08 |
| AZO6032 | Azimuth Airlines | 2 | 2026-06-14 |
| AZO5071 | Azimuth Airlines | 2 | 2026-06-07 |
| AZO5070 | Azimuth Airlines | 2 | 2026-06-06 |
| AZO5025 | Azimuth Airlines | 2 | 2026-05-28 |
| AZO4066 | Azimuth Airlines | 2 | 2026-06-19 |
| AZO4065 | Azimuth Airlines | 2 | 2026-06-26 |
| AZO3052 | - | 2 | 2026-06-27 |
| AZO3026 | Azimuth Airlines | 2 | 2026-05-28 |
| AZO9116 | - | 1 | 2026-06-08 |
| AZO8002 | - | 1 | 2026-05-22 |
| AZO6220 | - | 1 | 2026-06-26 |
| AZO6219 | - | 1 | 2026-06-26 |
| AZO6218 | - | 1 | 2026-05-14 |
| AZO6202 | Azimuth Airlines | 1 | 2026-05-30 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-28 | AZO4081 | - | Jun 28, 20:59 UTC | Jun 28, 21:10 UTC | 10m |
| 2026-06-27 | AZO3052 | - | Jun 27, 04:39 UTC | Jun 27, 04:59 UTC | 20m |
| 2026-06-26 | AZO6220 | - | Jun 26, 21:15 UTC | Jun 27, 03:15 UTC | 6h 0m |
| 2026-06-26 | AZO6219 | - | Jun 26, 06:09 UTC | Jun 26, 19:39 UTC | 13h 30m |
| 2026-06-26 | AZO4065 | UFA → TBS | Jun 26, 04:34 UTC | Jun 26, 04:45 UTC | 10m |
| 2026-06-19 | AZO4066 | TBS → UFA | Jun 19, 06:14 UTC | Jun 19, 06:39 UTC | 25m |
| 2026-06-18 | AZO6074 | - | Jun 18, 14:45 UTC | Jun 18, 15:20 UTC | 35m |
| 2026-06-18 | AZO3069 | KRR → IST | Jun 18, 12:30 UTC | Jun 18, 12:55 UTC | 25m |
| 2026-06-18 | AZO3070 | - | Jun 18, 07:20 UTC | Jun 18, 07:50 UTC | 30m |
| 2026-06-18 | AZO6073 | MRV → IST | Jun 18, 05:30 UTC | Jun 18, 05:40 UTC | 10m |
| 2026-06-17 | AZO6154 | TBS → MRV | Jun 17, 19:15 UTC | Jun 17, 19:55 UTC | 40m |
| 2026-06-17 | AZO6153 | - | Jun 17, 17:45 UTC | Jun 17, 18:00 UTC | 15m |
| 2026-06-15 | AZO4066 | TBS → UFA | Jun 15, 05:40 UTC | Jun 15, 06:00 UTC | 20m |
| 2026-06-15 | AZO4065 | UFA → TBS | Jun 15, 03:50 UTC | Jun 15, 04:00 UTC | 10m |
| 2026-06-14 | AZO6032 | EVN → MRV | Jun 14, 18:00 UTC | Jun 14, 18:40 UTC | 40m |
| 2026-06-14 | AZO6074 | - | Jun 14, 10:55 UTC | Jun 14, 16:25 UTC | 5h 30m |
| 2026-06-14 | AZO6073 | MRV → IST | Jun 14, 08:50 UTC | Jun 14, 09:15 UTC | 25m |
| 2026-06-13 | AZO6068 | NJC → MRV | Jun 13, 04:30 UTC | Jun 13, 05:40 UTC | 1h 10m |
| 2026-06-12 | AZO6068 | NJC → MRV | Jun 12, 07:25 UTC | Jun 13, 05:40 UTC | 22h 14m |
| 2026-06-11 | AZO6216 | AYT → MRV | Jun 11, 20:10 UTC | Jun 12, 08:15 UTC | 12h 5m |
| 2026-06-11 | AZO6215 | MRV → AYT | Jun 11, 08:00 UTC | Jun 11, 08:15 UTC | 15m |
| 2026-06-08 | AZO9116 | - | Jun 8, 16:10 UTC | Jun 8, 16:50 UTC | 40m |
| 2026-06-08 | AZO6066 | HMA → MRV | Jun 8, 03:25 UTC | Jun 8, 14:50 UTC | 11h 25m |
| 2026-06-07 | AZO6066 | HMA → MRV | Jun 7, 15:35 UTC | Jun 8, 14:45 UTC | 23h 10m |
| 2026-06-07 | AZO5071 | AER → IST | Jun 7, 13:55 UTC | Jun 7, 14:25 UTC | 30m |
| 2026-06-07 | AZO5092 | - | Jun 7, 07:45 UTC | Jun 7, 13:20 UTC | 5h 35m |
| 2026-06-06 | AZO5070 | IST → AER | Jun 6, 21:20 UTC | Jun 6, 21:40 UTC | 20m |
| 2026-06-05 | AZO5070 | IST → AER | Jun 5, 15:45 UTC | Jun 5, 16:20 UTC | 35m |
| 2026-06-05 | AZO5069 | AER → IST | Jun 5, 14:15 UTC | Jun 5, 14:35 UTC | 20m |
| 2026-06-04 | AZO5113 | AER → KLF | Jun 4, 12:05 UTC | Jun 4, 12:40 UTC | 35m |
| 2026-06-03 | AZO6120 | AER → MRV | Jun 3, 07:40 UTC | Jun 3, 08:10 UTC | 30m |
| 2026-06-02 | AZO5072 | IST → AER | Jun 2, 19:05 UTC | Jun 2, 19:35 UTC | 30m |
| 2026-06-02 | AZO5071 | AER → IST | Jun 2, 15:20 UTC | Jun 2, 16:40 UTC | 1h 20m |
| 2026-05-31 | AZO6216 | AYT → MRV | May 31, 14:55 UTC | Jun 1, 01:20 UTC | 10h 25m |
| 2026-05-31 | AZO6215 | MRV → AYT | May 31, 13:10 UTC | May 31, 13:35 UTC | 25m |
| 2026-05-30 | AZO6202 | SGC → CSY | May 30, 16:10 UTC | May 30, 16:35 UTC | 25m |
| 2026-05-28 | AZO3026 | TLV → KRR | May 28, 10:35 UTC | May 28, 18:50 UTC | 8h 15m |
| 2026-05-28 | AZO5025 | AER → TLV | May 28, 07:35 UTC | May 28, 09:00 UTC | 1h 25m |
| 2026-05-27 | AZO5025 | AER → TLV | May 27, 10:40 UTC | May 28, 08:45 UTC | 22h 5m |
| 2026-05-26 | AZO5030 | EVN → AER | May 26, 18:50 UTC | May 26, 19:34 UTC | 45m |
| 2026-05-26 | AZO5029 | AER → EVN | May 26, 13:19 UTC | May 26, 17:20 UTC | 4h 0m |
| 2026-05-25 | AZO3052 | AYT → KRR | May 25, 09:30 UTC | May 25, 11:00 UTC | 1h 30m |
| 2026-05-22 | AZO8002 | - | May 22, 19:00 UTC | May 22, 20:10 UTC | 1h 10m |
| 2026-05-20 | AZO6032 | EVN → MRV | May 20, 19:10 UTC | May 20, 19:55 UTC | 45m |
| 2026-05-19 | AZO6034 | TJM → MRV | May 19, 01:25 UTC | May 19, 02:25 UTC | 1h 0m |
| 2026-05-16 | AZO6068 | NJC → MRV | May 16, 08:11 UTC | May 16, 09:06 UTC | 55m |
| 2026-05-14 | AZO6218 | - | May 14, 22:40 UTC | May 14, 22:50 UTC | 10m |
| 2026-05-14 | AZO3051 | KRR → AYT | May 14, 21:10 UTC | May 14, 21:25 UTC | 15m |
| 2026-05-14 | AZO3026 | TLV → KRR | May 14, 15:15 UTC | May 14, 16:25 UTC | 1h 10m |
| 2026-05-13 | AZO5026 | TLV → AER | May 13, 20:45 UTC | May 14, 06:55 UTC | 10h 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-89179 page for operator, model, and routing details .