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

LYSETS HOLDING AS

Org. no. 933716740 Limited company (AS) Drammen Incorporated 2024 Active
Revenue 2025 NOK 0
Operating profit NOK −19,000
Equity NOK 1.7m
Incorporated 2024
Share capital NOK 30,000

Signals

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

LYSETS HOLDING AS is registered as a limited company in Drammen, Buskerud with organisation number 933716740. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Eie aksjer i andre selskaper og investeringer i fast eiendom, samt det som naturlig faller inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −19,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −19,000
▼ −124 %
Equity
NOK 1.7m
▲ +15 %
Est. value
NOK 2.9m

Financial health · 2025

Liquidity
2.48
Very good
Current assets ÷ current liabilities
Profitability
16.9%
Very good
Return on total assets
Solidity
85.3%
Very good
Equity as a share of total capital

Who owns LYSETS HOLDING AS?

LYSETS HOLDING AS
NOK 0 rev. · NOK −19,000 profit

LYSETS HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LYSETS HOLDING AS own?

LYSETS HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LYSETS HOLDING AS

Who owns LYSETS HOLDING AS?

Erik Olstad is the largest registered owner, with 100.0%.

What is the revenue of LYSETS HOLDING AS?

LYSETS HOLDING AS had revenue of NOK 0 in 2025.

Where is LYSETS HOLDING AS based?

LYSETS HOLDING AS has its business address in Drammen.

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.