BIZTRAC BETA
Plumbing installation

ASKER OG BÆRUM RØRLEGGERBEDRIFT AS

Org. no. 929464427 Limited company (AS) Asker Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 6.5m
Operating profit NOK 292,000
Equity NOK 1.4m
Incorporated 2022
Share capital NOK 100,000

ASKER OG BÆRUM RØRLEGGERBEDRIFT AS is registered as a limited company in Asker, Akershus with organisation number 929464427. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2022. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Rørleggertjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.5m in revenue and NOK 292,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.5m
Operating profit
NOK 292,000
Equity
NOK 1.4m
Est. value
NOK 1.7m

Financial health · 2025

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

Who owns ASKER OG BÆRUM RØRLEGGERBEDRIFT AS?

HENRIK ALEXANDER HILL
ASKER OG BÆRUM RØRLEGGERBEDRIFT AS
NOK 6.5m rev. · NOK 292,000 profit

ASKER OG BÆRUM RØRLEGGERBEDRIFT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ASKER OG BÆRUM RØRLEGGERBEDRIFT AS

Who owns ASKER OG BÆRUM RØRLEGGERBEDRIFT AS?

HENRIK ALEXANDER HILL is the largest registered owner, with 100.0%.

What is the revenue of ASKER OG BÆRUM RØRLEGGERBEDRIFT AS?

ASKER OG BÆRUM RØRLEGGERBEDRIFT AS had revenue of NOK 6.5m in 2025.

Who is the general manager of ASKER OG BÆRUM RØRLEGGERBEDRIFT AS?

Henrik Alexander Hill is registered as general manager of ASKER OG BÆRUM RØRLEGGERBEDRIFT AS.

Where is ASKER OG BÆRUM RØRLEGGERBEDRIFT AS based?

ASKER OG BÆRUM RØRLEGGERBEDRIFT AS has its business address in Nesbru.

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.