BIZTRAC BETA
Development of building projects

LEKMO AS

Org. no. 924583940 Limited company (AS) Bjørnafjorden Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −22,000
Equity NOK −57,000
Incorporated 2020
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−57k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−22k kr).

LEKMO AS is registered as a limited company in Bjørnafjorden, Vestland with organisation number 924583940. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”.

Key figures · 2025

Operating profit
NOK −22,000
Equity
NOK −57,000

Financial health · 2025

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

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

Who owns LEKMO AS?

ANNA LISA LEKVEN
LEKMO AS
· NOK −22,000 profit

LEKMO AS has 2 registered shareholders:

All shareholders and roles →

Which companies does LEKMO AS own?

LEKMO AS holds stakes in 2 companies:

See the full ownership structure →

Group structure

LEKMO AS er morselskap for 1 datterselskap:

Frequently asked questions about LEKMO AS

Who owns LEKMO AS?

ANNA LISA LEKVEN is the largest registered owner, with 50.0%.

Who is the general manager of LEKMO AS?

Stein Ole Moberg is registered as general manager of LEKMO AS.

Where is LEKMO AS based?

LEKMO AS has its business address in Os.

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.