BIZTRAC BETA
Plumbing installation

HØYANGER RØR AS

Org. no. 925927546 Limited company (AS) Høyanger Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 3.4m
Operating profit NOK −183,000
Equity NOK 443,000
Incorporated 2020
Share capital NOK 30,000

Signals

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

HØYANGER RØR AS is registered as a limited company in Høyanger, Vestland with organisation number 925927546. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selskapet skal selge tjenester og varer innen rørleggertjenester - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.4m in revenue and NOK −183,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.4m
Operating profit
NOK −183,000
Equity
NOK 443,000
Est. value
NOK 1.4m

Financial health · 2024

Liquidity
-2.39
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
125.0%
Very good
Equity as a share of total capital

Who owns HØYANGER RØR AS?

LINN FJÆREN LUND
HØYANGER RØR AS
NOK 3.4m rev. · NOK −183,000 profit

HØYANGER RØR AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HØYANGER RØR AS

Who owns HØYANGER RØR AS?

LINN FJÆREN LUND is the largest registered owner, with 50.0%.

What is the revenue of HØYANGER RØR AS?

HØYANGER RØR AS had revenue of NOK 3.4m in 2024.

Who is the general manager of HØYANGER RØR AS?

Linn Fjæren Lund is registered as general manager of HØYANGER RØR AS.

Where is HØYANGER RØR AS based?

HØYANGER RØR AS has its business address in Høyanger.

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.