BIZTRAC BETA
Plumbing installation

GRANDAHL RØR AS

Org. no. 931940236 Limited company (AS) Halden Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 6.5m
Operating profit NOK 289,000
Equity NOK 446,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

GRANDAHL RØR AS is registered as a limited company in Halden, Østfold with organisation number 931940236. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Rørleggervirksomhet og hva dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.5m in revenue and NOK 289,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.5m
Operating profit
NOK 289,000
Equity
NOK 446,000
Est. value
NOK 1.2m

Financial health · 2025

Liquidity
1.06
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
13.6%
Satisfactory
Equity as a share of total capital

Who owns GRANDAHL RØR AS?

RIKELEKTRO AS
GRANDAHL RØR AS
NOK 6.5m rev. · NOK 289,000 profit

GRANDAHL RØR AS has 4 registered shareholders:

All shareholders and roles →

Group structure

GRANDAHL RØR AS er morselskap for 1 datterselskap:

Frequently asked questions about GRANDAHL RØR AS

Who owns GRANDAHL RØR AS?

RIKELEKTRO AS is the largest registered owner, with 70.0%.

What is the revenue of GRANDAHL RØR AS?

GRANDAHL RØR AS had revenue of NOK 6.5m in 2025.

Who is the general manager of GRANDAHL RØR AS?

Christer Bentsen Grandahl is registered as general manager of GRANDAHL RØR AS.

Where is GRANDAHL RØR AS based?

GRANDAHL RØR AS has its business address in Halden.

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.