BIZTRAC BETA
Trade of electricity

KINECT ENERGY SPOT AS

Org. no. 976820592 Limited company (AS) Bergen Incorporated 1996 Active
Ownership graph ↗
Revenue 2024 NOK 2.1bn
Operating profit NOK 103.4m
Equity NOK 20.8m
Incorporated 1996
Share capital NOK 151,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

KINECT ENERGY SPOT AS is registered as a limited company in Bergen, Vestland with organisation number 976820592. The business is classified under trade of electricity (NACE 35.150). The company was incorporated in 1996. Registered share capital is NOK 151,000, divided into 1500 shares. The company's stated purpose is: “Forestå forvaltning av elektrisk kraft for kunder, være rådgiver innen energisektoren og alt hva derved er forbundet.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.1bn in revenue and NOK 103.4m in operating profit.

Key figures · 2024

Revenue
NOK 2.1bn
Operating profit
NOK 103.4m
Equity
NOK 20.8m
Est. value
NOK 259.2m

Financial health · 2024

Liquidity
0.98
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
3.9%
Weak
Equity as a share of total capital

Who owns KINECT ENERGY SPOT AS?

KINECT ENERGY AS
KINECT ENERGY SPOT AS
NOK 2.1bn rev. · NOK 103.4m profit

KINECT ENERGY SPOT AS has 1 registered shareholder:

All shareholders and roles →

Group structure

KINECT ENERGY SPOT AS er morselskap for 5 datterselskaper:

Frequently asked questions about KINECT ENERGY SPOT AS

Who owns KINECT ENERGY SPOT AS?

KINECT ENERGY AS is the largest registered owner, with 100.0%.

What is the revenue of KINECT ENERGY SPOT AS?

KINECT ENERGY SPOT AS had revenue of NOK 2.1bn in 2024.

Where is KINECT ENERGY SPOT AS based?

KINECT ENERGY SPOT AS has its business address in Bergen.

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.