BIZTRAC BETA
Other real estate activities on a fee or contract basis

LYSEGGEN ASSET AS

Org. no. 930481769 Limited company (AS) Stavanger Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −11,000
Equity NOK 9,000
Incorporated 2022
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−11k kr).
  • Nylig endring 2026-04-06 Adresseendring registrert 2026-04-06.

LYSEGGEN ASSET AS is registered as a limited company in Stavanger, Rogaland with organisation number 930481769. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2022. 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 · 2024

Operating profit
NOK −11,000
Equity
NOK 9,000
Est. value
NOK 8,000

Financial health · 2024

Liquidity
3.60
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
1.4%
Weak
Equity as a share of total capital

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

Who owns LYSEGGEN ASSET AS?

KIM STEVE LYSEGGEN
LYSEGGEN ASSET AS
· NOK −11,000 profit

LYSEGGEN ASSET AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LYSEGGEN ASSET AS own?

LYSEGGEN ASSET AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about LYSEGGEN ASSET AS

Who owns LYSEGGEN ASSET AS?

KIM STEVE LYSEGGEN is the largest registered owner, with 100.0%.

Where is LYSEGGEN ASSET AS based?

LYSEGGEN ASSET AS has its business address in Stavanger.

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.