biztrac. BETA
COMPANY REGISTER PROFILE
935786428 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Plumbing installation

ARCTIC RØR AS

Org. no. 935786428 Limited company (AS) Hammerfest Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 4.0m
Operating profit NOK 1.5m
Equity NOK 860,000
Incorporated 2025
Share capital NOK 30,000

ARCTIC RØR AS is registered as a limited company in Hammerfest, Finnmark with organisation number 935786428. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Rørleggervirksomhet. I tillegg utføres tjenester innenfor montering av kjøkken og garderobeinnredninger og snekkertjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.0m in revenue and NOK 1.5m in operating profit.

Former names: SHAR ARCTIC RØR AS

Key figures · 2025

Revenue
NOK 4.0m
Operating profit
NOK 1.5m
Equity
NOK 860,000
Est. value
NOK 4.7m

Financial health · 2025

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

Who owns ARCTIC RØR AS?

ARCTIC RØR AS
NOK 4.0m rev. · NOK 1.5m profit

ARCTIC RØR AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ARCTIC RØR AS own?

ARCTIC RØR AS holds a stake in 1 company:

See the full ownership structure →

Group structure

ARCTIC RØR AS er morselskap for 2 datterselskaper:

Frequently asked questions about ARCTIC RØR AS

Who owns ARCTIC RØR AS?

SHAR HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of ARCTIC RØR AS?

ARCTIC RØR AS had revenue of NOK 4.0m in 2025.

Where is ARCTIC RØR AS based?

ARCTIC RØR AS has its business address in Kvalsund.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.