BIZTRAC BETA
COMPANY REGISTER PROFILE
924287586 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Plumbing installation

RØRLEGGER1 NARVIK AS

Org. no. 924287586 Limited company (AS) Narvik Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 325,000
Operating profit NOK 5,000
Equity NOK 568,000
Incorporated 2019
Share capital NOK 30,000

RØRLEGGER1 NARVIK AS is registered as a limited company in Narvik, Nordland with organisation number 924287586. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 10 shares. The company's stated purpose is: “Drive rørleggervirksomhet og dertil relaterte aktiviteter, samt kunne delta i annen økonomisk virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 325,000 in revenue and NOK 5,000 in operating profit.

Key figures · 2025

Revenue
NOK 325,000
Operating profit
NOK 5,000
Equity
NOK 568,000
Est. value
NOK 277,000

Financial health · 2025

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

Who owns RØRLEGGER1 NARVIK AS?

VEGARD SIMONSEN
RØRLEGGER1 NARVIK AS
NOK 325,000 rev. · NOK 5,000 profit

RØRLEGGER1 NARVIK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RØRLEGGER1 NARVIK AS

Who owns RØRLEGGER1 NARVIK AS?

VEGARD SIMONSEN is the largest registered owner, with 100.0%.

What is the revenue of RØRLEGGER1 NARVIK AS?

RØRLEGGER1 NARVIK AS had revenue of NOK 325,000 in 2025.

Who is the general manager of RØRLEGGER1 NARVIK AS?

Vegard Simonsen is registered as general manager of RØRLEGGER1 NARVIK AS.

Where is RØRLEGGER1 NARVIK AS based?

RØRLEGGER1 NARVIK AS has its business address in Ankenes.

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.