BIZTRAC BETA
COMPANY REGISTER PROFILE
997510399 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Freight ocean transport

GSE SHIPPING I KS

Org. no. 997510399 Limited partnership (KS) Fitjar Incorporated 2011 Active
Ownership graph ↗
Operating profit NOK −228,000
Equity NOK 9.6m
Incorporated 2011
Share capital NOK 1.0m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−228k kr).

GSE SHIPPING I KS is registered as a limited partnership in Fitjar, Vestland with organisation number 997510399. The business is classified under freight ocean transport (NACE 50.201). The company was incorporated in 2011. Registered share capital is NOK 1.0m. The company's stated purpose is: “Rederivirksomhet, herunder å eie og bortbefrakte VS 485 PSV (plattform supply skip) og hva dermed hører til.”.

Key figures · 2024

Operating profit
NOK −228,000
Equity
NOK 9.6m
Est. value
NOK 18.9m

Financial health · 2025

Liquidity
46.83
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
97.9%
Very good
Equity as a share of total capital

Who owns GSE SHIPPING I KS?

No shareholders are registered for GSE SHIPPING I KS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about GSE SHIPPING I KS

Where is GSE SHIPPING I KS based?

GSE SHIPPING I KS has its business address in Fitjar.

Property

Business address Havnavegen 63, 5419 Fitjar
Cadastral unit 4615-67/84/0/0
Building Stort frittliggende boligbygg på 5 etg el mer · 8 units

14 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.