BIZTRAC BETA
Rental and operating of own or leased real estate

STAVERN MARINA AS

Org. no. 951722723 Limited company (AS) Larvik Incorporated 1989 Active
Ownership graph ↗
Revenue 2024 NOK 1.1m
Operating profit NOK −196,000
Equity NOK 10.4m
Incorporated 1989
Share capital NOK 750,000

Signals

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

STAVERN MARINA AS is registered as a limited company in Larvik, Vestfold with organisation number 951722723. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1989. Registered share capital is NOK 750,000, divided into 100 shares. The company's stated purpose is: “Handel, servicevirksomhet og restaurantvirksomhet, utleie av driftsmidler og arbeidskraft, samt annen maritim konsulentvirksomhet, og alt som står i forbindelse med dette, likeledes deltagelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.1m in revenue and NOK −196,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.1m
Operating profit
NOK −196,000
Equity
NOK 10.4m
Est. value
NOK 8.7m

Financial health · 2024

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

Who owns STAVERN MARINA AS?

BRYGGESLENGEN EIENDOM AS
STAVERN MARINA AS
NOK 1.1m rev. · NOK −196,000 profit

STAVERN MARINA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STAVERN MARINA AS

Who owns STAVERN MARINA AS?

BRYGGESLENGEN EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of STAVERN MARINA AS?

STAVERN MARINA AS had revenue of NOK 1.1m in 2024.

Where is STAVERN MARINA AS based?

STAVERN MARINA AS has its business address in Stavern.

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

Report a problem

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