biztrac. BETA
COMPANY REGISTER PROFILE
988986275 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Development of building projects

BARØFOSS INVEST AS

Org. no. 988986275 Limited company (AS) Notodden Incorporated 2005 Active
Revenue 2025 NOK 0
Operating profit NOK −235,000
Equity NOK 167.1m
Incorporated 2005
Share capital NOK 144,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−235k kr).

BARØFOSS INVEST AS is registered as a limited company in Notodden, Telemark with organisation number 988986275. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2005. Registered share capital is NOK 144,000, divided into 741 shares. The company's stated purpose is: “Investerings- og holdingsvirksomhet og alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −235,000 in operating profit.

Former names: KRISTEN BAKKEN AS

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −235,000
▲ +11 %
Equity
NOK 167.1m
▲ +16 %
Est. value
NOK 211.5m

Financial health · 2025

Liquidity
6.92
Very good
Current assets ÷ current liabilities
Profitability
12.8%
Good
Return on total assets
Solidity
90.2%
Very good
Equity as a share of total capital

Who owns BARØFOSS INVEST AS?

BARØFOSS INVEST AS has 4 registered shareholders:

All shareholders and roles →

Which companies does BARØFOSS INVEST AS own?

BARØFOSS INVEST AS holds stakes in 15 companies:

See the full ownership structure →

Frequently asked questions about BARØFOSS INVEST AS

Who owns BARØFOSS INVEST AS?

Kristen Bakken is the largest registered owner, with 80.2%.

What is the revenue of BARØFOSS INVEST AS?

BARØFOSS INVEST AS had revenue of NOK 0 in 2025.

Where is BARØFOSS INVEST AS based?

BARØFOSS INVEST AS has its business address in Notodden.

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

Report a problem

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