BIZTRAC BETA
Site preparation

OLE P. BAKKEN AS

Org. no. 928195678 Limited company (AS) Holtålen Incorporated 1975 Active
Ownership graph ↗
Revenue 2024 NOK 17.8m
Operating profit NOK 401,000
Equity NOK 4.2m
Incorporated 1975
Employees 9
Share capital NOK 300,000

OLE P. BAKKEN AS is registered as a limited company in Holtålen, Trøndelag with organisation number 928195678. The business is classified under site preparation (NACE 43.120). The company was incorporated in 1975 and has 9 registered employees. Registered share capital is NOK 300,000, divided into 300 shares. The company's stated purpose is: “Entreprenørvirksomhet inn bygg og anlegg, kjøp og salg av grus, samt annen virksomhet som naturlig faller inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 17.8m in revenue and NOK 401,000 in operating profit.

Key figures · 2024

Revenue
NOK 17.8m
Operating profit
NOK 401,000
Equity
NOK 4.2m
Est. value
NOK 2.9m

Financial health · 2024

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

Who owns OLE P. BAKKEN AS?

OLAF BAKKEN
OLE P. BAKKEN AS
NOK 17.8m rev. · NOK 401,000 profit

OLE P. BAKKEN AS has 2 registered shareholders:

All shareholders and roles →

Which companies does OLE P. BAKKEN AS own?

OLE P. BAKKEN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about OLE P. BAKKEN AS

Who owns OLE P. BAKKEN AS?

OLAF BAKKEN is the largest registered owner, with 66.7%.

What is the revenue of OLE P. BAKKEN AS?

OLE P. BAKKEN AS had revenue of NOK 17.8m in 2024.

Who is the general manager of OLE P. BAKKEN AS?

Olaf Bakken is registered as general manager of OLE P. BAKKEN AS.

Where is OLE P. BAKKEN AS based?

OLE P. BAKKEN AS has its business address in Ålen.

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.