BIZTRAC BETA
COMPANY REGISTER PROFILE
922753598 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Civil engineering activities

VOSS MIKROKRAFT AS

Org. no. 922753598 Limited company (AS) Voss Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −6,000
Equity NOK 19,000
Incorporated 2019
Share capital NOK 30,000

Signals

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

VOSS MIKROKRAFT AS is registered as a limited company in Voss, Vestland with organisation number 922753598. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Prosjektering, tilvirkning og salg av små vannkraftanlegg. Ingeniør, rådgiving og konsulentvirksomhet, samt prosjektering og bygging av automasjon og styringsanlegg.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −6,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −6,000
Equity
NOK 19,000
Est. value
NOK 30,000

Financial health · 2025

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

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

Who owns VOSS MIKROKRAFT AS?

MORTEN ØREN
VOSS MIKROKRAFT AS
NOK 0 rev. · NOK −6,000 profit

VOSS MIKROKRAFT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VOSS MIKROKRAFT AS

Who owns VOSS MIKROKRAFT AS?

MORTEN ØREN is the largest registered owner, with 100.0%.

What is the revenue of VOSS MIKROKRAFT AS?

VOSS MIKROKRAFT AS had revenue of NOK 0 in 2025.

Where is VOSS MIKROKRAFT AS based?

VOSS MIKROKRAFT AS has its business address in Voss.

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.