BIZTRAC BETA
Other technical consultancy

BW SPRINKLER AS

Org. no. 916893612 Limited company (AS) Asker Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 199,000
Operating profit NOK 152,000
Equity NOK 61,000
Incorporated 2016
Share capital NOK 30,000

BW SPRINKLER AS is registered as a limited company in Asker, Akershus with organisation number 916893612. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Prosjektering av sprinkleranlegg. Kontroll av vannbaserte automatiske slokkeanlegg. Annen brannteknisk konsulentvirksomhet. Tilby tekniske tjenester og rådgivning innen brannforebyggende tiltak.”. The most recent filed accounts, for the 2024 financial year, show NOK 199,000 in revenue and NOK 152,000 in operating profit.

Key figures · 2024

Revenue
NOK 199,000
Operating profit
NOK 152,000
Equity
NOK 61,000
Est. value
NOK 481,000

Financial health · 2024

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns BW SPRINKLER AS?

BJØRN WILLY BRAATHEN
BW SPRINKLER AS
NOK 199,000 rev. · NOK 152,000 profit

BW SPRINKLER AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about BW SPRINKLER AS

Who owns BW SPRINKLER AS?

BJØRN WILLY BRAATHEN is the largest registered owner, with 70.0%.

What is the revenue of BW SPRINKLER AS?

BW SPRINKLER AS had revenue of NOK 199,000 in 2024.

Who is the general manager of BW SPRINKLER AS?

Bjørn Willy Braathen is registered as general manager of BW SPRINKLER AS.

Where is BW SPRINKLER AS based?

BW SPRINKLER AS has its business address in Borgen.

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.