BIZTRAC BETA
Plumbing installation

ASAP RØRSERVICE AS

Org. no. 912273911 Limited company (AS) Bærum Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 3.3m
Operating profit NOK 306,000
Equity NOK 972,000
Incorporated 2013
Share capital NOK 30,000

ASAP RØRSERVICE AS is registered as a limited company in Bærum, Akershus with organisation number 912273911. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Byggtjenester, herunder rør, installasjon, import og eksport samt eiendom og tilhørende aktiviteter.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.3m in revenue and NOK 306,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.3m
Operating profit
NOK 306,000
Equity
NOK 972,000
Est. value
NOK 1.4m

Financial health · 2024

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

Who owns ASAP RØRSERVICE AS?

MUZAFFAR AHMAD CHAUDHRY
ASAP RØRSERVICE AS
NOK 3.3m rev. · NOK 306,000 profit

ASAP RØRSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ASAP RØRSERVICE AS own?

ASAP RØRSERVICE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ASAP RØRSERVICE AS

Who owns ASAP RØRSERVICE AS?

MUZAFFAR AHMAD CHAUDHRY is the largest registered owner, with 100.0%.

What is the revenue of ASAP RØRSERVICE AS?

ASAP RØRSERVICE AS had revenue of NOK 3.3m in 2024.

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

Talat Mahmooda Memon is registered as general manager of ASAP RØRSERVICE AS.

Where is ASAP RØRSERVICE AS based?

ASAP RØRSERVICE AS has its business address in Blommenholm.

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.