BIZTRAC BETA
Other recreational activities

OLLEBUKTA MARINA AS

Org. no. 979875770 Limited company (AS) Tønsberg Incorporated 1998 Active
Ownership graph ↗
Revenue 2024 NOK 6.2m
Operating profit NOK −125,000
Equity NOK 1.1m
Incorporated 1998
Employees 5
Share capital NOK 600,000

Signals

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

OLLEBUKTA MARINA AS is registered as a limited company in Tønsberg, Vestfold with organisation number 979875770. The business is classified under other recreational activities (NACE 93.292). The company was incorporated in 1998 and has 5 registered employees. Registered share capital is NOK 600,000, divided into 600 shares. The company's stated purpose is: “Drift av marina og alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.2m in revenue and NOK −125,000 in operating profit.

Key figures · 2024

Revenue
NOK 6.2m
Operating profit
NOK −125,000
Equity
NOK 1.1m
Est. value
NOK 6.7m

Financial health · 2025

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

Who owns OLLEBUKTA MARINA AS?

TØNSBERG BÅTFORENING
OLLEBUKTA MARINA AS
NOK 6.2m rev. · NOK −125,000 profit

OLLEBUKTA MARINA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OLLEBUKTA MARINA AS

Who owns OLLEBUKTA MARINA AS?

TØNSBERG BÅTFORENING is the largest registered owner, with 100.0%.

What is the revenue of OLLEBUKTA MARINA AS?

OLLEBUKTA MARINA AS had revenue of NOK 6.2m in 2024.

Who is the general manager of OLLEBUKTA MARINA AS?

Tom Morten Brynildsen is registered as general manager of OLLEBUKTA MARINA AS.

Where is OLLEBUKTA MARINA AS based?

OLLEBUKTA MARINA AS has its business address in Tønsberg.

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.