BIZTRAC BETA
Business and other management consultancy activities

LYKKEJÆGER AS

Org. no. 926959948 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −9,000
Equity NOK −28,000
Incorporated 2021
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−28k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−9k kr).

LYKKEJÆGER AS is registered as a limited company in Oslo, Oslo with organisation number 926959948. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2021. Registered share capital is NOK 100,000, divided into 2 shares. The company's stated purpose is: “Eie og forvalte investeringer for selskapets aksjonærer.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −9,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −9,000
Equity
NOK −28,000

Financial health · 2024

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

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

Who owns LYKKEJÆGER AS?

Kjartan Tollefsen Laupstad
LYKKEJÆGER AS
NOK 0 rev. · NOK −9,000 profit

LYKKEJÆGER AS has 2 registered shareholders:

All shareholders and roles →

Which companies does LYKKEJÆGER AS own?

LYKKEJÆGER AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LYKKEJÆGER AS

Who owns LYKKEJÆGER AS?

Kjartan Tollefsen Laupstad is the largest registered owner, with 50.0%.

What is the revenue of LYKKEJÆGER AS?

LYKKEJÆGER AS had revenue of NOK 0 in 2024.

Where is LYKKEJÆGER AS based?

LYKKEJÆGER 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 15.06.2026.

Report a problem

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