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

OKSEKRAFT AS

Org. no. 987255072 Limited company (AS) Kvinesdal Incorporated 2004 Active
Ownership graph ↗
Revenue 2025 NOK 572,000
Operating profit NOK 184,000
Equity NOK −641,000
Incorporated 2004
Share capital NOK 450,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−641k kr).

OKSEKRAFT AS is registered as a limited company in Kvinesdal, Agder with organisation number 987255072. The business is classified under production of electricity from hydropower (NACE 35.121). The company was incorporated in 2004. Registered share capital is NOK 450,000, divided into 450 shares. The company's stated purpose is: “Bygge og drive kraftverk samt yte konsulenttjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 572,000 in revenue and NOK 184,000 in operating profit.

Key figures · 2025

Revenue
NOK 572,000
▲ +29 %
Operating profit
NOK 184,000
▲ +92 %
Equity
NOK −641,000
▲ +5 %
Est. value
NOK 772,000

Financial health · 2025

Liquidity
0.18
Not satisfactory
Current assets ÷ current liabilities
Profitability
8.3%
Satisfactory
Return on total assets
Solidity
-27.3%
Weak
Equity as a share of total capital

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

Who owns OKSEKRAFT AS?

OKSEKRAFT AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about OKSEKRAFT AS

Who owns OKSEKRAFT AS?

OKSEFJELL INVEST AS is the largest registered owner, with 88.9%.

What is the revenue of OKSEKRAFT AS?

OKSEKRAFT AS had revenue of NOK 572,000 in 2025.

Who is the general manager of OKSEKRAFT AS?

Sigmund Arne Oksefjell is registered as general manager of OKSEKRAFT AS.

Where is OKSEKRAFT AS based?

OKSEKRAFT AS has its business address in Kvinesdal.

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.