BIZTRAC BETA
Production of electricity from hydropower

FELLESKRAFT AS

Org. no. 978684769 Limited company (AS) Nannestad Incorporated 1997 Active
Ownership graph ↗
Revenue 2024 NOK 918,000
Operating profit NOK 36,000
Equity NOK 1.3m
Incorporated 1997
Share capital NOK 140,000

FELLESKRAFT AS is registered as a limited company in Nannestad, Akershus with organisation number 978684769. The business is classified under production of electricity from hydropower (NACE 35.121). The company was incorporated in 1997. Registered share capital is NOK 140,000, divided into 1400 shares. The company's stated purpose is: “Bygge og drive kraftverk, samt hva som står i forbindelse med dette, herunder deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 918,000 in revenue and NOK 36,000 in operating profit.

Key figures · 2024

Revenue
NOK 918,000
Operating profit
NOK 36,000
Equity
NOK 1.3m
Est. value
NOK 962,000

Financial health · 2024

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

Who owns FELLESKRAFT AS?

TOR ARNE HAFSTAD
FELLESKRAFT AS
NOK 918,000 rev. · NOK 36,000 profit

FELLESKRAFT AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FELLESKRAFT AS own?

FELLESKRAFT AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FELLESKRAFT AS

Who owns FELLESKRAFT AS?

TOR ARNE HAFSTAD is the largest registered owner, with 100.0%.

What is the revenue of FELLESKRAFT AS?

FELLESKRAFT AS had revenue of NOK 918,000 in 2024.

Who is the general manager of FELLESKRAFT AS?

Tor Arne Hafstad is registered as general manager of FELLESKRAFT AS.

Where is FELLESKRAFT AS based?

FELLESKRAFT AS has its business address in Nannestad.

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.