Нефтерудовоз-32М, ПК-46, Neftec-2 — Photo — FleetPhoto

<

>

Нефтерудовоз-32М, ПК-46, Neftec-2

Нефтерудовоз-32М · ПК-46 · Neftec-2

Река Волга, разделительный бьеф Горьковского гидроузла
Нижегородская область, Городец

Author: genris Date: May 12, 2014

Statistics

License: Copyright ©

Published 18.05.2014 09:52 MSK
Views — 4066

Permanent link to this photo

Нефтерудовоз-32М

Class:	Нефтерудовоз
Design:	1570
Home Port:	Nizhny Novgorod
IMO:	7829637
Registry:	РКО (РРР до 2022)
Registry number:	183493
Registry class:	М-СП3,5(ЛЁД30)
Call sign:	UBUU
Built:	31.08.1979
Builder:	Пермский судостроительный завод "Кама" Perm
Yard number:	831
Current state:	Renamed Operating
Renames:	ок. 2015 Аркадий Минченя
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.

ПК-46

Class:	КПЛ-5-30
Design:	Р-99
Home Port:	Бор
Registry:	РКО (РРР до 2022)
Board number:	В-10-2992
Registry number:	198085
Registry class:	О2,0
Built:	13.09.1978
Builder:	Завод «Нижегородский теплоход» Бор
Yard number:	2038
Current state:	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.

Neftec-2

Class:	Нефтерудовоз
Design:	1570
Home Port:	Turkmenbashi
IMO:	7630270
Registry:	РМРС
Registry number:	750311
Registry class:	КМ(*)Л4[1] IIСП нефтерудовоз
Call sign:	EZAZ
Built:	30.06.1976
Builder:	Пермский судостроительный завод "Кама" Perm
Yard number:	819
Current state:	Registry data changed Модернизация
Renames:	Нефтерудовоз-20М → 01.1999 • → 2019 Стр. №10
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.