BIZTRAC BETA
Plumbing installation

LISLEBY RØR OG REPARASJONER AS

Org. no. 966472952 Limited company (AS) Vestby Incorporated 1993 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −16,000
Equity NOK −186,000
Incorporated 1993
Share capital NOK 100,000

Signals

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

LISLEBY RØR OG REPARASJONER AS is registered as a limited company in Vestby, Akershus with organisation number 966472952. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 1993. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Salg og produksjon av varer og tjenester, eksport og import.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −16,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −16,000
Equity
NOK −186,000

Financial health · 2024

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

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

Who owns LISLEBY RØR OG REPARASJONER AS?

TORENETH EIENDOM AS
LISLEBY RØR OG REPARASJONER AS
NOK 0 rev. · NOK −16,000 profit

LISLEBY RØR OG REPARASJONER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LISLEBY RØR OG REPARASJONER AS

Who owns LISLEBY RØR OG REPARASJONER AS?

TORENETH EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of LISLEBY RØR OG REPARASJONER AS?

LISLEBY RØR OG REPARASJONER AS had revenue of NOK 0 in 2024.

Where is LISLEBY RØR OG REPARASJONER AS based?

LISLEBY RØR OG REPARASJONER AS has its business address in Son.

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.