KSP LEO
Description
KSP LEO built in 2006 is a vessel in the Tug. Its IMO number is 9370604 and the current MMSI number is 533000296. The vessel has callsign 9MQA6. Summer deadweight is 259. Her current width is reported to be 23 / 10 m meters. Her length overall (LOA) is 30 meters. KSP LEO is sailing under the flag of Malaysia. Latest reported draught is 0 meters.
Similar vessels
| Vessel | Built | GT | DWT | Size (m) | |
|---|---|---|---|---|---|
MAJU LOYALTYTug | 2018 | 497 | 267 | 32 / 13 m | |
UNION PANDATug | 2009 | 479 | 261 | 32 / 12 m | |
DIRTug | 2011 | 494 | 262 | 34 / 13 m | |
OMISALJTug | 1992 | 291 | 251 | 30 / 10 m | |
SVITZER AMAZONASTug | 2008 | 439 | 260 | 31 / 10 m | |
LAMARTug | 2009 | 399 | 258 | 30 / 12 m | |
SD TEMPESTTug | 2017 | 495 | 267 | 32 / 13 m | |
UKKOTug | 2002 | 583 | 260 | 34 / 13 m | |
UNION 8Tug | 1996 | 398 | 256 | 32 / 12 m | |
SIGNET STARSSTRIPESTug | 2011 | 485 | 266 | 28 / 13 m | |
SST ORCATug | 2018 | 492 | 260 | 32 / 13 m | |
SVITZER CASTLETug | 2005 | 374 | 260 | 33 / 10 m | |
NEPTUNTug | 2011 | 469 | 261 | 32 / 11 m | |
KARAPIPERIS NEW GENETug | 1994 | 305 | 251 | ||
SST GRIZZLYTug | 2018 | 492 | 265 | 32 / 13 m | |
EVELENATug | 2008 | 399 | 258 | 30 / 12 m | |
VOLODYMYR IVANOVTug | 2012 | 453 | 255 | 32 / 12 m | |
BALTICTug | 2007 | 489 | 270 | 35 / 13 m | |
SVITZER FALCONTug | 2009 | 439 | 249 | 30 / 11 m | |
AKATSUKI MARUPusher Tug | 1995 | 285 | 255 | 32 / 9 m | |
MAJU LOYALTY
Tug
UNION PANDA
Tug
DIR
Tug
OMISALJ
Tug
SVITZER AMAZONAS
Tug
LAMAR
Tug
SD TEMPEST
Tug
UKKO
Tug
UNION 8
Tug
SIGNET STARSSTRIPES
Tug
SST ORCA
Tug
SVITZER CASTLE
Tug
NEPTUN
Tug
KARAPIPERIS NEW GENE
Tug
SST GRIZZLY
Tug
EVELENA
Tug
VOLODYMYR IVANOV
Tug
BALTIC
Tug
SVITZER FALCON
Tug
AKATSUKI MARU
Pusher Tug
Disclaimer: KSP LEO current position and history of port calls are received by AIS. Maritime Database provides technical specifications, tonnages, and management information. The information is provided by Maritime Database for free and without any assurance. KSP LEO data is provided for informational reasons only, and Maritime Database assumes no responsibility for its accuracy or reliability.