BIZTRAC BETA
COMPANY REGISTER PROFILE
986296948 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Other business support service activities n.e.c.

DRAMMEN FJORDPARK KS

Org. no. 986296948 Limited partnership (KS) Oslo Incorporated 2003 Active
Ownership graph ↗
Operating profit NOK −34,000
Equity NOK 72.9m
Incorporated 2003
Share capital NOK 31.3m

Signals

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

DRAMMEN FJORDPARK KS is registered as a limited partnership in Oslo, Oslo with organisation number 986296948. The business is classified under other business support service activities n.e.c. (NACE 82.990). The company was incorporated in 2003. Registered share capital is NOK 31.3m. The company's stated purpose is: “Være deltaker i Drammen Fjordpark ANS.”.

Key figures · 2024

Operating profit
NOK −34,000
Equity
NOK 72.9m
Est. value
NOK 66.3m

Financial health · 2024

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

Who owns DRAMMEN FJORDPARK KS?

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

Frequently asked questions about DRAMMEN FJORDPARK KS

Where is DRAMMEN FJORDPARK KS based?

DRAMMEN FJORDPARK KS has its business address in Oslo.

Property

Business address Tyveholmen kontorfellesskap Tjuvholmen allé 19, 0252 Oslo
Cadastral unit 301-210/43/0/0
Building Kontor- og administrasjonsbygning, rådhus · 6 units

77 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.