BIZTRAC BETA
Trade of electricity

LADEKRAFT AS

Org. no. 932128330 Limited company (AS) Tokke Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −8,000
Equity NOK 9,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

LADEKRAFT AS is registered as a limited company in Tokke, Telemark with organisation number 932128330. The business is classified under trade of electricity (NACE 35.150). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Skal selge varer og tjenester innen lading av elbiler, og annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −8,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −8,000
Equity
NOK 9,000
Est. value
NOK 10,000

Financial health · 2025

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

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

Who owns LADEKRAFT AS?

ANNE HEGSETH SESSENG
LADEKRAFT AS
NOK 0 rev. · NOK −8,000 profit

LADEKRAFT AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about LADEKRAFT AS

Who owns LADEKRAFT AS?

ANNE HEGSETH SESSENG is the largest registered owner, with 25.0%.

What is the revenue of LADEKRAFT AS?

LADEKRAFT AS had revenue of NOK 0 in 2025.

Who is the general manager of LADEKRAFT AS?

Anne Hegseth Sesseng is registered as general manager of LADEKRAFT AS.

Where is LADEKRAFT AS based?

LADEKRAFT AS has its business address in Høydalsmo.

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.