biztrac. BETA
COMPANY REGISTER PROFILE
920804039 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Production of electricity from hydropower

GRAFFER KRAFT AS

Org. no. 920804039 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 2.4m
Operating profit NOK −35,000
Equity NOK 7.8m
Incorporated 2018
Share capital NOK 6.0m

Signals

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

GRAFFER KRAFT AS is registered as a limited company in Oslo, Oslo with organisation number 920804039. The business is classified under production of electricity from hydropower (NACE 35.121). The company was incorporated in 2018. Registered share capital is NOK 6.0m, divided into 30000 shares. The company's stated purpose is: “Utvikle, bygge, eie og drive kraftverk. Herunder delta i selskaper med samme formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.4m in revenue and NOK −35,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.4m
▼ −4 %
Operating profit
NOK −35,000
▼ −153 %
Equity
NOK 7.8m
▼ −19 %
Est. value
NOK 5.2m

Financial health · 2025

Liquidity
0.01
Not satisfactory
Current assets ÷ current liabilities
Profitability
-0.0%
Not satisfactory
Return on total assets
Solidity
17.2%
Satisfactory
Equity as a share of total capital

Who owns GRAFFER KRAFT AS?

GRAFFER KRAFT AS
NOK 2.4m rev. · NOK −35,000 profit

GRAFFER KRAFT AS has 1 registered shareholder:

All shareholders and roles →

Group structure

GRAFFER KRAFT AS er morselskap for 1 datterselskap:

Frequently asked questions about GRAFFER KRAFT AS

Who owns GRAFFER KRAFT AS?

CLEMENS KRAFTVERK AS is the largest registered owner, with 100.0%.

What is the revenue of GRAFFER KRAFT AS?

GRAFFER KRAFT AS had revenue of NOK 2.4m in 2025.

Where is GRAFFER KRAFT AS based?

GRAFFER KRAFT AS has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.