BIZTRAC BETA
Production of electricity from solar power

BUER SOLKRAFTVERK AS

Org. no. 930462837 Limited company (AS) Sarpsborg Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 301,000
Operating profit NOK −106,000
Equity NOK −492,000
Incorporated 2022
Share capital NOK 300,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−492k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−106k kr).

BUER SOLKRAFTVERK AS is registered as a limited company in Sarpsborg, Østfold with organisation number 930462837. The business is classified under production of electricity from solar power (NACE 35.123). The company was incorporated in 2022. Registered share capital is NOK 300,000, divided into 300 shares. The company's stated purpose is: “Utvikle, bygge, drifte og eie solkraftanlegg samt det som naturlig hører inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 301,000 in revenue and NOK −106,000 in operating profit.

Key figures · 2025

Revenue
NOK 301,000
Operating profit
NOK −106,000
Equity
NOK −492,000

Financial health · 2024

Liquidity
5.08
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-5.2%
Weak
Equity as a share of total capital

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

Who owns BUER SOLKRAFTVERK AS?

PER ANDERS BUER
BUER SOLKRAFTVERK AS
NOK 301,000 rev. · NOK −106,000 profit

BUER SOLKRAFTVERK AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about BUER SOLKRAFTVERK AS

Who owns BUER SOLKRAFTVERK AS?

PER ANDERS BUER is the largest registered owner, with 50.0%.

What is the revenue of BUER SOLKRAFTVERK AS?

BUER SOLKRAFTVERK AS had revenue of NOK 301,000 in 2025.

Where is BUER SOLKRAFTVERK AS based?

BUER SOLKRAFTVERK AS has its business address in Ise.

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.