biztrac. BETA
COMPANY REGISTER PROFILE
925144509 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

LEKON INVEST AS

Org. no. 925144509 Limited company (AS) Bergen Incorporated 2020 Active
Revenue 2025 NOK 0
Operating profit NOK −4,000
Equity NOK 7,000
Incorporated 2020
Share capital NOK 30,000

Signals

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

LEKON INVEST AS is registered as a limited company in Bergen, Vestland with organisation number 925144509. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Investering i andre selskaper samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −4,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −4,000
▲ +25 %
Equity
NOK 7,000
▼ −34 %
Est. value
NOK 9,000

Financial health · 2025

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

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

Who owns LEKON INVEST AS?

LEKON INVEST AS
NOK 0 rev. · NOK −4,000 profit

LEKON INVEST AS has 2 registered shareholders:

All shareholders and roles →

Which companies does LEKON INVEST AS own?

LEKON INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LEKON INVEST AS

Who owns LEKON INVEST AS?

Cherin Myrdal Vervik is the largest registered owner, with 50.0%.

What is the revenue of LEKON INVEST AS?

LEKON INVEST AS had revenue of NOK 0 in 2025.

Where is LEKON INVEST AS based?

LEKON INVEST AS has its business address in Flaktveit.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.