BIZTRAC BETA
COMPANY REGISTER PROFILE
990922632 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Production of electricity from hydropower

GIRE KRAFT AS

Org. no. 990922632 Limited company (AS) Nesbyen Incorporated 2007 Active
Ownership graph ↗
Revenue 2025 NOK 2.9m
Operating profit NOK 1.1m
Equity NOK 7.3m
Incorporated 2007
Share capital NOK 207,000

GIRE KRAFT AS is registered as a limited company in Nesbyen, Buskerud with organisation number 990922632. The business is classified under production of electricity from hydropower (NACE 35.121). The company was incorporated in 2007. Registered share capital is NOK 207,000, divided into 2070 shares. The company's stated purpose is: “Bygging og drift av småkraftverk i Sandhåni i Nes kommune, samt omsetning av den energi dette småkraftverk produserer.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.9m in revenue and NOK 1.1m in operating profit.

Key figures · 2025

Revenue
NOK 2.9m
▼ −1 %
Operating profit
NOK 1.1m
▲ +5 %
Equity
NOK 7.3m
▲ +1 %
Est. value
NOK 7.6m

Financial health · 2025

Liquidity
1.56
Good
Current assets ÷ current liabilities
Profitability
8.3%
Satisfactory
Return on total assets
Solidity
52.0%
Very good
Equity as a share of total capital

Who owns GIRE KRAFT AS?

GIRE KRAFT AS has 9 registered shareholders:

All shareholders and roles →

Which companies does GIRE KRAFT AS own?

GIRE KRAFT AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about GIRE KRAFT AS

Who owns GIRE KRAFT AS?

EIRIK NORDHAGEN is the largest registered owner, with 11.1%.

What is the revenue of GIRE KRAFT AS?

GIRE KRAFT AS had revenue of NOK 2.9m in 2025.

Who is the general manager of GIRE KRAFT AS?

Åsmund Grønning is registered as general manager of GIRE KRAFT AS.

Where is GIRE KRAFT AS based?

GIRE KRAFT AS has its business address in Nesbyen.

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

Report a problem

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