BIZTRAC BETA
Plumbing installation

LØHRE VVS AS

Org. no. 980397009 Limited company (AS) Midtre Gauldal Incorporated 1998 Active
Ownership graph ↗
Revenue 2024 NOK 32.1m
Operating profit NOK −61,000
Equity NOK 7.8m
Incorporated 1998
Employees 18
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−61k kr).

LØHRE VVS AS is registered as a limited company in Midtre Gauldal, Trøndelag with organisation number 980397009. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 1998 and has 18 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Rørleggervirksomhet med tilhørende utsalg innen VVS.”. The most recent filed accounts, for the 2024 financial year, show NOK 32.1m in revenue and NOK −61,000 in operating profit.

Key figures · 2024

Revenue
NOK 32.1m
Operating profit
NOK −61,000
Equity
NOK 7.8m
Est. value
NOK 14.2m

Financial health · 2024

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

Who owns LØHRE VVS AS?

LØHRE EIENDOM AS
LØHRE VVS AS
NOK 32.1m rev. · NOK −61,000 profit

LØHRE VVS AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LØHRE VVS AS own?

LØHRE VVS AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LØHRE VVS AS

Who owns LØHRE VVS AS?

LØHRE EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of LØHRE VVS AS?

LØHRE VVS AS had revenue of NOK 32.1m in 2024.

Who is the general manager of LØHRE VVS AS?

Frank Løhre is registered as general manager of LØHRE VVS AS.

Where is LØHRE VVS AS based?

LØHRE VVS AS has its business address in Støren.

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.