BIZTRAC BETA
General medical practice activities

LEGEKRAFT AS

Org. no. 931756877 Limited company (AS) Lillestrøm Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −20,000
Equity NOK 4,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−20k kr).

LEGEKRAFT AS is registered as a limited company in Lillestrøm, Akershus with organisation number 931756877. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Utleie av helsepersonell.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −20,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −20,000
Equity
NOK 4,000
Est. value
NOK 7,000

Financial health · 2024

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

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

Who owns LEGEKRAFT AS?

A&V INVEST AS
LEGEKRAFT AS
NOK 0 rev. · NOK −20,000 profit

LEGEKRAFT AS has 4 registered shareholders:

All shareholders and roles →

Which companies does LEGEKRAFT AS own?

LEGEKRAFT AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LEGEKRAFT AS

Who owns LEGEKRAFT AS?

A&V INVEST AS is the largest registered owner, with 40.0%.

What is the revenue of LEGEKRAFT AS?

LEGEKRAFT AS had revenue of NOK 0 in 2024.

Who is the general manager of LEGEKRAFT AS?

Joanna Maria Lankut is registered as general manager of LEGEKRAFT AS.

Where is LEGEKRAFT AS based?

LEGEKRAFT AS has its business address in Lillestrøm.

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.