BIZTRAC BETA
Site preparation

BARKENÆS HOLDING AS

Org. no. 915772242 Limited company (AS) Sel Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −7,000
Equity NOK 51,000
Incorporated 2015
Share capital NOK 100,000

Signals

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

BARKENÆS HOLDING AS is registered as a limited company in Sel, Innlandet with organisation number 915772242. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2015. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Eie aksjer og andeler i andre selskaper, samt det som har naturlig tilknytning til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −7,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −7,000
Equity
NOK 51,000
Est. value
NOK 53,000

Financial health · 2024

Liquidity
0.03
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
2.0%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns BARKENÆS HOLDING AS?

HELGE INGAR BARKENÆS
BARKENÆS HOLDING AS
NOK 0 rev. · NOK −7,000 profit

BARKENÆS HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BARKENÆS HOLDING AS own?

BARKENÆS HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about BARKENÆS HOLDING AS

Who owns BARKENÆS HOLDING AS?

HELGE INGAR BARKENÆS is the largest registered owner, with 100.0%.

What is the revenue of BARKENÆS HOLDING AS?

BARKENÆS HOLDING AS had revenue of NOK 0 in 2024.

Where is BARKENÆS HOLDING AS based?

BARKENÆS HOLDING AS has its business address in Heidal.

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.