BIZTRAC BETA
Veterinary activities

RINGERIKE DYREKLINIKK AS

Org. no. 929416597 Limited company (AS) Ringerike Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 14.7m
Operating profit NOK 1.9m
Equity NOK 4.0m
Incorporated 2022
Employees 16
Share capital NOK 31,000

RINGERIKE DYREKLINIKK AS is registered as a limited company in Ringerike, Buskerud with organisation number 929416597. The business is classified under veterinary activities (NACE 75.000). The company was incorporated in 2022 and has 16 registered employees. Registered share capital is NOK 31,000, divided into 31 shares. The company's stated purpose is: “Klinikk for undersøkelse og behandling av dyr, kjøp og salg av fôr og utstyr til dyr samt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 14.7m in revenue and NOK 1.9m in operating profit.

Key figures · 2025

Revenue
NOK 14.7m
Operating profit
NOK 1.9m
Equity
NOK 4.0m
Est. value
NOK 11.4m

Financial health · 2025

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

Who owns RINGERIKE DYREKLINIKK AS?

SOAA HOLDING AS
RINGERIKE DYREKLINIKK AS
NOK 14.7m rev. · NOK 1.9m profit

RINGERIKE DYREKLINIKK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RINGERIKE DYREKLINIKK AS

Who owns RINGERIKE DYREKLINIKK AS?

SOAA HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of RINGERIKE DYREKLINIKK AS?

RINGERIKE DYREKLINIKK AS had revenue of NOK 14.7m in 2025.

Who is the general manager of RINGERIKE DYREKLINIKK AS?

Bjørn Erik Strand is registered as general manager of RINGERIKE DYREKLINIKK AS.

Where is RINGERIKE DYREKLINIKK AS based?

RINGERIKE DYREKLINIKK AS has its business address in Hønefoss.

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.