biztrac. BETA
COMPANY REGISTER PROFILE
915618405 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Wholesale of other machinery and equipment

BD KLARO AS

Org. no. 915618405 Limited company (AS) Risør Incorporated 2015 Active
Revenue 2025 NOK 67.6m
Operating profit NOK 5.4m
Equity NOK 31.6m
Incorporated 2015
Employees 19
Share capital NOK 997,000

BD KLARO AS is registered as a limited company in Risør, Agder with organisation number 915618405. The business is classified under wholesale of other machinery and equipment (NACE 46.640). The company was incorporated in 2015 and has 19 registered employees. Registered share capital is NOK 997,000, divided into 1993500 shares. The company's stated purpose is: “Salg og service av renseanlegg for hus, hytter og næringsanlegg, samt annen virksomhet som ellers står i naturlig tilknytning til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 67.6m in revenue and NOK 5.4m in operating profit.

Former names: KLARO II AS, KLARO RENSEANLEGG NORGE AS

Key figures · 2025

Revenue
NOK 67.6m
▲ +32 %
Operating profit
NOK 5.4m
▲ +35 %
Equity
NOK 31.6m
▲ +15 %
Est. value
NOK 37.4m

Financial health · 2025

Liquidity
2.52
Very good
Current assets ÷ current liabilities
Profitability
12.2%
Good
Return on total assets
Solidity
63.4%
Very good
Equity as a share of total capital

Who owns BD KLARO AS?

BD KLARO AS
NOK 67.6m rev. · NOK 5.4m profit

BD KLARO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BD KLARO AS

Who owns BD KLARO AS?

Brødrene Dahl A/S is the largest registered owner, with 100.0%.

What is the revenue of BD KLARO AS?

BD KLARO AS had revenue of NOK 67.6m in 2025.

Who is the general manager of BD KLARO AS?

Øystein Vereide is registered as general manager of BD KLARO AS.

Where is BD KLARO AS based?

BD KLARO AS has its business address in Akland.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.