Петр Стрелков, Бойкий, ГТ-361 — Photo — FleetPhoto

<

>

Петр Стрелков, Бойкий, ГТ-361

Петр Стрелков · Бойкий · ГТ-361

Река Дон
Ростовская область, Азов
Азовский морской порт

Author: Павел Емельянов · Samara Date: September 24, 2013

Statistics

License: Copyright ©

Published 20.02.2014 23:31 MSK
Views — 2194

Permanent link to this photo

Петр Стрелков

Class:	Волжский
Design:	05074М
Home Port:	Saint Petersburg
IMO:	8866840
Registry:	РМРС
Registry number:	905913
Registry class:	KM* L4 R3-RSN
Call sign:	UGNV
Keel laid:	20.06.1990
Built:	31.08.1990
Builder:	Судостроительный завод «Ока» МСП СССР (ССЗ №342, предприятие п/я В-2566, предприятие п/я №31) Навашино
Yard number:	1038
Current state:	Renamed Operating
Renames:	Волжский-36 → 01.2002 • → 06.2016 Svyatogor → 05.2018 Святогор
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.

Бойкий

Class:	Ярославец (пр. 376 всех модификаций)
Design:	Р-376У
Home Port:	Rostov-on-Don
Registry:	РКО (РРР до 2022)
Registry number:	181412
Registry class:	О2,0
Built:	04.05.1973
Builder:	Sosnovka Shipyard Сосновка
Yard number:	1842
Current state:	Operating
Renames:	Бойкий → ок. 1997 Полковник Шаров → 04.2008
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.

ГТ-361

Class:	ГТ
Design:	926
Home Port:	Rostov-on-Don
Registry:	РКО (РРР до 2022)
Board number:	Д-02-1415
Registry number:	081420
Registry class:	Р1,2
Built:	18.07.1962
Builder:	Судоремонтный завод "Красный Дон" Ростов-на-Дону
Yard number:	240
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.