BIZTRAC BETA
Plumbing installation

LØKEN VVS HOLDING AS

Org. no. 920924786 Limited company (AS) Trysil Incorporated 2018 Active
Ownership graph ↗
Operating profit NOK −30,000
Equity NOK 1.8m
Incorporated 2018
Share capital NOK 293,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−30k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

LØKEN VVS HOLDING AS is registered as a limited company in Trysil, Innlandet with organisation number 920924786. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2018. Registered share capital is NOK 293,000, divided into 1300 shares. The company's stated purpose is: “Kjøp og salg av aksjer, samt investere i virksomheter av enhver art. I tillegg andre produkter/tjenester som naturlig hører sammen med dette.”.

Key figures · 2024

Operating profit
NOK −30,000
Equity
NOK 1.8m
Est. value
NOK 1.8m

Financial health · 2024

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

Who owns LØKEN VVS HOLDING AS?

LØKEN VVS HOLDING AS
LØKEN VVS HOLDING AS
· NOK −30,000 profit

LØKEN VVS HOLDING AS has 6 registered shareholders:

All shareholders and roles →

Which companies does LØKEN VVS HOLDING AS own?

LØKEN VVS HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about LØKEN VVS HOLDING AS

Who owns LØKEN VVS HOLDING AS?

LØKEN VVS HOLDING AS is the largest registered owner, with 50.0%.

Who is the general manager of LØKEN VVS HOLDING AS?

Lars Erik Støbak is registered as general manager of LØKEN VVS HOLDING AS.

Where is LØKEN VVS HOLDING AS based?

LØKEN VVS HOLDING AS has its business address in Trysil.

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.