BIZTRAC BETA
Development of building projects

LYSERSTØLEN AS

Org. no. 915874363 Limited company (AS) Nesbyen Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 438,000
Operating profit NOK 47,000
Equity NOK 1.1m
Incorporated 2015
Share capital NOK 30,000

LYSERSTØLEN AS is registered as a limited company in Nesbyen, Buskerud with organisation number 915874363. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg, drift og utvikling av fast eiendom. Entreprenør innen bygg- og anleggstjenester, kjøp og salg av produkter og tjenester i tilknytning til bygg- og anleggsvirksomhet. Vaktmestertjenester, snøbrøyting og tilsvarende tjenesteytende tjenester. Deltakelse i andre selskaper, samt kjøp og salg av aksjer og andeler.”. The most recent filed accounts, for the 2024 financial year, show NOK 438,000 in revenue and NOK 47,000 in operating profit.

Key figures · 2024

Revenue
NOK 438,000
Operating profit
NOK 47,000
Equity
NOK 1.1m
Est. value
NOK 932,000

Financial health · 2024

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

Who owns LYSERSTØLEN AS?

TOM KLYPE
LYSERSTØLEN AS
NOK 438,000 rev. · NOK 47,000 profit

LYSERSTØLEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LYSERSTØLEN AS

Who owns LYSERSTØLEN AS?

TOM KLYPE is the largest registered owner, with 100.0%.

What is the revenue of LYSERSTØLEN AS?

LYSERSTØLEN AS had revenue of NOK 438,000 in 2024.

Who is the general manager of LYSERSTØLEN AS?

Tom Klype is registered as general manager of LYSERSTØLEN AS.

Where is LYSERSTØLEN AS based?

LYSERSTØLEN AS has its business address in Nesbyen.

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.