BIZTRAC BETA
Uoppgitt

MYKLEBUSTDALEN BIOENERGI AS

Org. no. 924382708 Limited company (AS) Kvinnherad Incorporated 2019 Active
Ownership graph ↗
Operating profit NOK −10,000
Equity NOK 104,000
Incorporated 2019
Share capital NOK 30,000

Signals

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

MYKLEBUSTDALEN BIOENERGI AS is registered as a limited company in Kvinnherad, Vestland with organisation number 924382708. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 20 shares. The company's stated purpose is: “Å eie i selskap som driver med og/eller drive virksomhet knyttet til bioenergi og annen fornybar energi. Investere i økonomisk virksomhet av enhver art og alt som står i forbindelse med dette, herunder deltakelse i andre selskaper.”.

Key figures · 2024

Operating profit
NOK −10,000
Equity
NOK 104,000
Est. value
NOK 864,000

Financial health · 2024

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

Who owns MYKLEBUSTDALEN BIOENERGI AS?

TORE EIK
MYKLEBUSTDALEN BIOENERGI AS
· NOK −10,000 profit

MYKLEBUSTDALEN BIOENERGI AS has 2 registered shareholders:

All shareholders and roles →

Which companies does MYKLEBUSTDALEN BIOENERGI AS own?

MYKLEBUSTDALEN BIOENERGI AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about MYKLEBUSTDALEN BIOENERGI AS

Who owns MYKLEBUSTDALEN BIOENERGI AS?

TORE EIK is the largest registered owner, with 50.0%.

Who is the general manager of MYKLEBUSTDALEN BIOENERGI AS?

Tore Eik is registered as general manager of MYKLEBUSTDALEN BIOENERGI AS.

Where is MYKLEBUSTDALEN BIOENERGI AS based?

MYKLEBUSTDALEN BIOENERGI AS has its business address in Dimmelsvik.

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.