biztrac. BETA
COMPANY REGISTER PROFILE
920998194 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Other captive investment companies

LYCKE INVEST AS

Org. no. 920998194 Limited company (AS) Oslo Incorporated 2018 Active
Revenue 2025 NOK 35,000
Operating profit NOK 19,000
Equity NOK 1.7m
Incorporated 2018
Share capital NOK 240,000

Signals

1 flags
  • Nylig endring 2026-06-05 Aksjekapital registrert 2026-06-05.

LYCKE INVEST AS is registered as a limited company in Oslo, Oslo with organisation number 920998194. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2018. Registered share capital is NOK 240,000, divided into 200000 shares. The company's stated purpose is: “Investere i og rådgi ulike selskaper med formål om å skape verdier for aksjonærene og samfunnet.”. The most recent filed accounts, for the 2025 financial year, show NOK 35,000 in revenue and NOK 19,000 in operating profit.

Key figures · 2025

Revenue
NOK 35,000
▲ +180 %
Operating profit
NOK 19,000
▲ +1054 %
Equity
NOK 1.7m
▲ +15 %
Est. value
NOK 960,000

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
0.4%
Not satisfactory
Return on total assets
Solidity
26.8%
Good
Equity as a share of total capital

Who owns LYCKE INVEST AS?

LYCKE INVEST AS
NOK 35,000 rev. · NOK 19,000 profit

LYCKE INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LYCKE INVEST AS own?

LYCKE INVEST AS holds stakes in 17 companies:

See the full ownership structure →

Frequently asked questions about LYCKE INVEST AS

Who owns LYCKE INVEST AS?

Martin Lycke is the largest registered owner, with 100.0%.

What is the revenue of LYCKE INVEST AS?

LYCKE INVEST AS had revenue of NOK 35,000 in 2025.

Where is LYCKE INVEST AS based?

LYCKE INVEST AS has its business address in Oslo.

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.