sensors Mode-S transponder
155C34
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-89140 · SUKHOI Superjet 100-95
- Hex
- 155C34
- Octal
- 05256064
- Decimal
- 1,399,860
- Country
- RU
- Tail
- RA-89140
- Type
- SU95
- Flights observed
- 61
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 20d ago
Last known position
Country allocation
The ICAO 24-bit address 155C34 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 |
|---|---|---|---|
| RWZ4332 | Red Wings | 16 | 2026-06-02 |
| RWZ4331 | Red Wings | 14 | 2026-06-02 |
| RWZ4531 | - | 4 | 2026-06-22 |
| RWZ4532 | - | 2 | 2026-06-20 |
| RWZ911 | Red Wings | 1 | 2026-04-22 |
| RWZ4704 | Red Wings | 1 | 2026-06-26 |
| RWZ4684 | - | 1 | 2026-06-15 |
| RWZ4683 | - | 1 | 2026-06-15 |
| RWZ4655 | Red Wings | 1 | 2026-06-19 |
| RWZ4528 | Red Wings | 1 | 2026-06-23 |
| RWZ4527 | - | 1 | 2026-06-20 |
| RWZ4318 | Red Wings | 1 | 2026-04-19 |
| RWZ4312 | Red Wings | 1 | 2026-05-09 |
| RWZ4311 | Red Wings | 1 | 2026-05-09 |
| RWZ4302 | Red Wings | 1 | 2026-06-24 |
| RWZ2003 | Red Wings | 1 | 2026-06-08 |
| RWZ1952 | - | 1 | 2026-06-12 |
| RWZ1951 | - | 1 | 2026-06-12 |
| RWZ1564 | Red Wings | 1 | 2026-06-21 |
| RWZ1505 | Red Wings | 1 | 2026-06-05 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-28 | RWZ1370 | - | Jun 28, 08:34 UTC | Jun 28, 08:55 UTC | 20m |
| 2026-06-28 | RWZ1369 | KUF → TBS | Jun 28, 06:34 UTC | Jun 28, 06:44 UTC | 10m |
| 2026-06-27 | RWZ1356 | - | Jun 27, 19:49 UTC | Jun 27, 20:14 UTC | 25m |
| 2026-06-27 | RWZ1302 | - | Jun 27, 10:54 UTC | Jun 27, 18:15 UTC | 7h 20m |
| 2026-06-27 | RWZ1301 | - | Jun 27, 09:04 UTC | Jun 27, 09:50 UTC | 45m |
| 2026-06-26 | RWZ4704 | MSQ → CEK | Jun 26, 05:44 UTC | Jun 26, 06:04 UTC | 20m |
| 2026-06-24 | RWZ4302 | NQZ → MRV | Jun 24, 06:25 UTC | Jun 24, 07:30 UTC | 1h 5m |
| 2026-06-23 | RWZ4528 | BJV → KRR | Jun 23, 07:35 UTC | Jun 24, 06:59 UTC | 23h 25m |
| 2026-06-22 | RWZ4531 | - | Jun 22, 14:59 UTC | Jun 22, 17:15 UTC | 2h 15m |
| 2026-06-21 | RWZ1564 | TBS → KRR | Jun 21, 15:34 UTC | Jun 21, 16:30 UTC | 55m |
| 2026-06-20 | RWZ4532 | - | Jun 20, 17:59 UTC | Jun 20, 18:45 UTC | 45m |
| 2026-06-20 | RWZ4527 | - | Jun 20, 11:05 UTC | Jun 20, 16:59 UTC | 5h 55m |
| 2026-06-19 | RWZ4531 | - | Jun 19, 15:04 UTC | Jun 20, 10:04 UTC | 19h 0m |
| 2026-06-19 | RWZ4531 | - | Jun 19, 14:59 UTC | Jun 20, 10:04 UTC | 19h 5m |
| 2026-06-19 | RWZ4655 | MRV → IST | Jun 19, 13:04 UTC | Jun 19, 13:29 UTC | 25m |
| 2026-06-15 | RWZ4684 | - | Jun 15, 23:35 UTC | Jun 16, 00:15 UTC | 40m |
| 2026-06-15 | RWZ4683 | - | Jun 15, 21:55 UTC | Jun 15, 22:10 UTC | 15m |
| 2026-06-15 | RWZ1042 | KEJ → SVX | Jun 15, 07:20 UTC | Jun 15, 07:50 UTC | 30m |
| 2026-06-15 | RWZ1052 | UUD → KEJ | Jun 15, 05:30 UTC | Jun 15, 06:00 UTC | 30m |
| 2026-06-12 | RWZ1952 | - | Jun 12, 18:30 UTC | Jun 12, 19:45 UTC | 1h 15m |
| 2026-06-12 | RWZ1951 | - | Jun 12, 15:35 UTC | Jun 12, 16:55 UTC | 1h 20m |
| 2026-06-11 | RWZ1504 | BUS → KZN | Jun 11, 01:55 UTC | Jun 11, 15:50 UTC | 13h 55m |
| 2026-06-09 | RWZ1059 | TOF → HTA | Jun 9, 01:25 UTC | Jun 9, 01:50 UTC | 25m |
| 2026-06-08 | RWZ2003 | SVX → TOF | Jun 8, 22:20 UTC | Jun 8, 22:30 UTC | 10m |
| 2026-06-05 | RWZ1505 | NUX → NBC | Jun 5, 07:50 UTC | Jun 5, 08:10 UTC | 20m |
| 2026-06-02 | RWZ4332 | EVN → MRV | Jun 2, 15:10 UTC | Jun 2, 15:50 UTC | 40m |
| 2026-06-02 | RWZ4331 | MRV → EVN | Jun 2, 13:30 UTC | Jun 2, 13:40 UTC | 10m |
| 2026-05-31 | RWZ4332 | EVN → MRV | May 31, 14:05 UTC | May 31, 14:50 UTC | 45m |
| 2026-05-31 | RWZ4331 | MRV → EVN | May 31, 12:35 UTC | May 31, 12:45 UTC | 10m |
| 2026-05-30 | RWZ4332 | EVN → MRV | May 30, 19:25 UTC | May 30, 20:10 UTC | 45m |
| 2026-05-30 | RWZ4532 | - | May 30, 13:40 UTC | May 30, 18:05 UTC | 4h 25m |
| 2026-05-30 | RWZ4531 | - | May 30, 11:55 UTC | May 30, 12:40 UTC | 45m |
| 2026-05-26 | RWZ4332 | EVN → MRV | May 26, 15:20 UTC | May 26, 15:49 UTC | 30m |
| 2026-05-26 | RWZ4331 | MRV → EVN | May 26, 13:34 UTC | May 26, 13:45 UTC | 10m |
| 2026-05-24 | RWZ4332 | EVN → MRV | May 24, 14:00 UTC | May 24, 14:45 UTC | 45m |
| 2026-05-24 | RWZ4331 | MRV → EVN | May 24, 12:00 UTC | May 24, 12:45 UTC | 45m |
| 2026-05-19 | RWZ4332 | EVN → MRV | May 19, 15:45 UTC | May 19, 16:15 UTC | 30m |
| 2026-05-19 | RWZ4331 | MRV → EVN | May 19, 13:50 UTC | May 19, 14:00 UTC | 10m |
| 2026-05-17 | RWZ4332 | EVN → MRV | May 17, 13:50 UTC | May 17, 14:15 UTC | 25m |
| 2026-05-17 | RWZ4331 | MRV → EVN | May 17, 11:55 UTC | May 17, 12:35 UTC | 40m |
| 2026-05-12 | RWZ4332 | EVN → MRV | May 12, 15:05 UTC | May 12, 15:50 UTC | 45m |
| 2026-05-12 | RWZ4331 | MRV → EVN | May 12, 13:30 UTC | May 12, 13:40 UTC | 10m |
| 2026-05-09 | RWZ4312 | TLV → AER | May 9, 19:00 UTC | May 9, 20:15 UTC | 1h 15m |
| 2026-05-09 | RWZ4311 | AER → TLV | May 9, 12:45 UTC | May 9, 17:45 UTC | 5h 0m |
| 2026-05-05 | RWZ4332 | EVN → MRV | May 5, 15:01 UTC | May 5, 15:50 UTC | 50m |
| 2026-05-05 | RWZ4331 | MRV → EVN | May 5, 13:00 UTC | May 5, 13:35 UTC | 35m |
| 2026-05-03 | RWZ4332 | EVN → MRV | May 3, 19:20 UTC | May 3, 19:55 UTC | 35m |
| 2026-05-03 | RWZ4331 | MRV → EVN | May 3, 17:29 UTC | May 3, 17:40 UTC | 10m |
| 2026-05-02 | RWZ4332 | EVN → MRV | May 2, 18:10 UTC | May 2, 18:45 UTC | 35m |
| 2026-05-02 | RWZ4331 | MRV → EVN | May 2, 16:00 UTC | May 2, 16:45 UTC | 45m |
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-89140 page for operator, model, and routing details .