BIZTRAC BETA
Uoppgitt

KRAFTPARTNER AS

Org. no. 920178790 Limited company (AS) Vestnes Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −95,000
Equity NOK 18.2m
Incorporated 2017
Share capital NOK 7.5m

Signals

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

KRAFTPARTNER AS is registered as a limited company in Vestnes, Møre og Romsdal with organisation number 920178790. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2017. Registered share capital is NOK 7.5m, divided into 150000 shares. The company's stated purpose is: “Investering i aksjer og eiendom og andre tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −95,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −95,000
Equity
NOK 18.2m
Est. value
NOK 30.3m

Financial health · 2024

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

Who owns KRAFTPARTNER AS?

ALSCO INDUSTRI AS
KRAFTPARTNER AS
NOK 0 rev. · NOK −95,000 profit

KRAFTPARTNER AS has 7 registered shareholders:

All shareholders and roles →

Which companies does KRAFTPARTNER AS own?

KRAFTPARTNER AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KRAFTPARTNER AS

Who owns KRAFTPARTNER AS?

ALSCO INDUSTRI AS is the largest registered owner, with 40.0%.

What is the revenue of KRAFTPARTNER AS?

KRAFTPARTNER AS had revenue of NOK 0 in 2024.

Where is KRAFTPARTNER AS based?

KRAFTPARTNER AS has its business address in Vikebukt.

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.