BIZTRAC BETA
Rental and operating of own or leased real estate

OLLEBUKTA 2 AS

Org. no. 985610487 Limited company (AS) Tønsberg Incorporated 2003 Active
Ownership graph ↗
Revenue 2024 NOK 1.8m
Operating profit NOK 1.4m
Equity NOK 4.3m
Incorporated 2003
Share capital NOK 100,000

OLLEBUKTA 2 AS is registered as a limited company in Tønsberg, Vestfold with organisation number 985610487. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2003. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Eiendomsdrift, eiendomsutvikling, utleie og handel samt hva hermed står i forbindelse, herunder å delta i andre selskaper med lignede virksomnhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.8m in revenue and NOK 1.4m in operating profit.

Key figures · 2024

Revenue
NOK 1.8m
Operating profit
NOK 1.4m
Equity
NOK 4.3m
Est. value
NOK 5.9m

Financial health · 2024

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

Who owns OLLEBUKTA 2 AS?

HARFAG HOLDING AS
OLLEBUKTA 2 AS
NOK 1.8m rev. · NOK 1.4m profit

OLLEBUKTA 2 AS has 2 registered shareholders:

All shareholders and roles →

Which companies does OLLEBUKTA 2 AS own?

OLLEBUKTA 2 AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about OLLEBUKTA 2 AS

Who owns OLLEBUKTA 2 AS?

HARFAG HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of OLLEBUKTA 2 AS?

OLLEBUKTA 2 AS had revenue of NOK 1.8m in 2024.

Who is the general manager of OLLEBUKTA 2 AS?

Harald Fagereng is registered as general manager of OLLEBUKTA 2 AS.

Where is OLLEBUKTA 2 AS based?

OLLEBUKTA 2 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.