BIZTRAC BETA
Rental and operating of own or leased real estate

LA8PV AS

Org. no. 928950778 Limited company (AS) Lier Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 22,000
Operating profit NOK −17,000
Equity NOK −2,000
Incorporated 2022
Share capital NOK 30,000

Signals

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

LA8PV AS is registered as a limited company in Lier, Buskerud with organisation number 928950778. 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 30,000, divided into 30000 shares. The company's stated purpose is: “Kjøp, salg, utvikling, og utleie av fast eiendom og driftsmidler i bygg- og anleggsbransjen, samt annen virksomhet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 22,000 in revenue and NOK −17,000 in operating profit.

Key figures · 2025

Revenue
NOK 22,000
Operating profit
NOK −17,000
Equity
NOK −2,000

Financial health · 2025

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

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

Who owns LA8PV AS?

KENNETH STRYSSE
LA8PV AS
NOK 22,000 rev. · NOK −17,000 profit

LA8PV AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LA8PV AS

Who owns LA8PV AS?

KENNETH STRYSSE is the largest registered owner, with 100.0%.

What is the revenue of LA8PV AS?

LA8PV AS had revenue of NOK 22,000 in 2025.

Where is LA8PV AS based?

LA8PV AS has its business address in Lier.

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.