Речной-63, Узола-2, Нефтерудовоз-2 — Photo — FleetPhoto

<

>

Речной-63, Узола-2, Нефтерудовоз-2

Речной-63 · Узола-2 · Нефтерудовоз-2

Река Волга, Иваньковское водохранилище
Тверская область, Конаково

Author: Конюхов Юрий · Конаково Date: September 21, 2018

Statistics

License: Copyright ©

Published 14.02.2019 23:22 MSK
Views — 1967

Permanent link to this photo

Речной-63

Class:	Речной (Московский), проект 908
Home Port:	Moscow
Registry:	РКО (РРР до 2022)
Board number:	М-04-1046
Registry number:	175977
Registry class:	Р1,2А
Built:	1971
Builder:	Moscow Shipbuilding & Shiprepair Yard Москва
Yard number:	744
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.

Узола-2

Class:	Узола, проект Р-164
Home Port:	Тверь
Registry:	РКО (РРР до 2022)
Board number:	М-01-123
Registry number:	226922
Registry class:	О2,0 (ЛЁД10)А
MMSI:	273320550
Built:	27.06.1990
Builder:	Gorodetsky Shiprepair-Machinery Yard SE Gorodets
Yard number:	2
Current state:	Не работает с 2020
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.

Нефтерудовоз-2

Class:	Нефтерудовоз
Design:	1553
Home Port:	Saint Petersburg
IMO:	8986884
Registry:	РКО (РРР до 2022)
Registry number:	092102
Registry class:	М-СП3,5(ЛЕД20)
Call sign:	UFZD
MMSI:	273446860
Built:	03.10.1969
Builder:	Пермский судостроительный завод "Кама" Perm
Yard number:	802
Current state:	Operating
Renames:	Нефтерудовоз-2 → 05.2008 Pranik → 05.2010
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.