Речной-50, Астраханец-003, Астраханец-002 — Photo — FleetPhoto

<

>

Речной-50, Астраханец-003, Астраханец-002

Речной-50 · Астраханец-003 · Астраханец-002

Река Волга, Угличское водохранилище
Московская область, Дубна

Author: Александр Конов Date: May 30, 2015

Statistics

License: Copyright ©

Published 30.05.2015 13:35 MSK
Views — 3200

Permanent link to this photo

Речной-50

Class:	Речной (Московский), проект 908
Home Port:	Moscow
Registry:	РКО (РРР до 2022)
Board number:	М-04-1033
Registry number:	168797
Registry class:	Р1,2А
Built:	30.09.1970
Builder:	Moscow Shipbuilding & Shiprepair Yard Москва
Yard number:	732
Current state:	Registry data changed Operating
Information about the vessel is given on the basis of publicly available sources and observations of users of this site. Site Administration has no associations with these sources and not responsible for this data. The information here may be invalid or outdated.

Астраханец-003

Design:	23020А
Home Port:	Astrakhan
Registry:	РКО (РРР до 2022)
Registry number:	242276
Registry class:	Р1,2А
Keel laid:	28.01.2014
Built:	02.11.2015
Builder:	Moscow Shipbuilding & Shiprepair Yard Moscow
Yard number:	507
Second builder:	ООО Верфь братьев Нобель Rybinsk
Current state:	Registry data changed Operating
Information about the vessel is given on the basis of publicly available sources and observations of users of this site. Site Administration has no associations with these sources and not responsible for this data. The information here may be invalid or outdated.

Астраханец-002

Design:	23020А
Home Port:	Astrakhan
Registry:	РКО (РРР до 2022)
Registry number:	242275
Registry class:	Р1,2А
Keel laid:	19.12.2013
Built:	02.11.2015
Builder:	Moscow Shipbuilding & Shiprepair Yard Moscow
Yard number:	506
Second builder:	ООО Верфь братьев Нобель Rybinsk
Current state:	Registry data changed Operating
Information about the vessel is given on the basis of publicly available sources and observations of users of this site. Site Administration has no associations with these sources and not responsible for this data. The information here may be invalid or outdated.