BIZTRAC BETA
Uoppgitt

KE BAKKEN HOLDING AS

Org. no. 822147372 Limited company (AS) Nordre Land Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −8,000
Equity NOK 22,000
Incorporated 2019
Share capital NOK 30,000

Signals

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

KE BAKKEN HOLDING AS is registered as a limited company in Nordre Land, Innlandet with organisation number 822147372. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investering i andre selskaper samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −8,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −8,000
Equity
NOK 22,000
Est. value
NOK 26,000

Financial health · 2024

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

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

Who owns KE BAKKEN HOLDING AS?

KJELL ERIK BAKKEN
KE BAKKEN HOLDING AS
NOK 0 rev. · NOK −8,000 profit

KE BAKKEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KE BAKKEN HOLDING AS own?

KE BAKKEN HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KE BAKKEN HOLDING AS

Who owns KE BAKKEN HOLDING AS?

KJELL ERIK BAKKEN is the largest registered owner, with 100.0%.

What is the revenue of KE BAKKEN HOLDING AS?

KE BAKKEN HOLDING AS had revenue of NOK 0 in 2024.

Where is KE BAKKEN HOLDING AS based?

KE BAKKEN HOLDING AS has its business address in Aust-Torpa.

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.