BIZTRAC BETA
Plumbing installation

HADELAND RØRSERVICE AS

Org. no. 918906029 Limited company (AS) Gran Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 2.9m
Operating profit NOK 757,000
Equity NOK 889,000
Incorporated 2017
Share capital NOK 30,000

HADELAND RØRSERVICE AS is registered as a limited company in Gran, Innlandet with organisation number 918906029. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Montering av hvitevarer på kjøkken og service. Montering av varmtvannstanker, blandebatterier, rør og automatisk lekkasje stoppere. Og det som ligger under rørarbeid og vvs.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.9m in revenue and NOK 757,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.9m
Operating profit
NOK 757,000
Equity
NOK 889,000
Est. value
NOK 2.7m

Financial health · 2024

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

Who owns HADELAND RØRSERVICE AS?

ABDUL SABOOR QADIR
HADELAND RØRSERVICE AS
NOK 2.9m rev. · NOK 757,000 profit

HADELAND RØRSERVICE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HADELAND RØRSERVICE AS

Who owns HADELAND RØRSERVICE AS?

ABDUL SABOOR QADIR is the largest registered owner, with 51.0%.

What is the revenue of HADELAND RØRSERVICE AS?

HADELAND RØRSERVICE AS had revenue of NOK 2.9m in 2024.

Who is the general manager of HADELAND RØRSERVICE AS?

Qais Ata Abedalqader Ibdah is registered as general manager of HADELAND RØRSERVICE AS.

Where is HADELAND RØRSERVICE AS based?

HADELAND RØRSERVICE AS has its business address in Brandbu.

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.