BIZTRAC BETA
Rental and operating of own or leased real estate

LYSEVEIEN 16 AS

Org. no. 929722728 Limited company (AS) Hole Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 804,000
Operating profit NOK 640,000
Equity NOK 4.9m
Incorporated 2022
Share capital NOK 75,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

LYSEVEIEN 16 AS is registered as a limited company in Hole, Buskerud with organisation number 929722728. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 75,000, divided into 30 shares. The company's stated purpose is: “Utleie og drift og kjøp og salg av fast eiendom og verdipapirer, herunder deltagelse i andre selskaper og virksomheter med tilsvarende formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 804,000 in revenue and NOK 640,000 in operating profit.

Key figures · 2025

Revenue
NOK 804,000
Operating profit
NOK 640,000
Equity
NOK 4.9m
Est. value
NOK 4.9m

Financial health · 2025

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

Who owns LYSEVEIEN 16 AS?

RUSTFRIE STÅLPRODUKTER AS
LYSEVEIEN 16 AS
NOK 804,000 rev. · NOK 640,000 profit

LYSEVEIEN 16 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LYSEVEIEN 16 AS

Who owns LYSEVEIEN 16 AS?

RUSTFRIE STÅLPRODUKTER AS is the largest registered owner, with 100.0%.

What is the revenue of LYSEVEIEN 16 AS?

LYSEVEIEN 16 AS had revenue of NOK 804,000 in 2025.

Where is LYSEVEIEN 16 AS based?

LYSEVEIEN 16 AS has its business address in Krokkleiva.

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.