BIZTRAC BETA
Veterinary activities

RØYKEN OG OMEGN DYREKLINIKK AS

Org. no. 991719202 Limited company (AS) Asker Incorporated 2007 Active
Ownership graph ↗
Revenue 2025 NOK 13.1m
Operating profit NOK 1.2m
Equity NOK 3.6m
Incorporated 2007
Employees 8
Share capital NOK 100,000

RØYKEN OG OMEGN DYREKLINIKK AS is registered as a limited company in Asker, Akershus with organisation number 991719202. The business is classified under veterinary activities (NACE 75.000). The company was incorporated in 2007 and has 8 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Veterinærtjenester og beslektet virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 13.1m in revenue and NOK 1.2m in operating profit.

Key figures · 2025

Revenue
NOK 13.1m
Operating profit
NOK 1.2m
Equity
NOK 3.6m
Est. value
NOK 8.1m

Financial health · 2025

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

Who owns RØYKEN OG OMEGN DYREKLINIKK AS?

CHRISTINE RØNNING KVAM
RØYKEN OG OMEGN DYREKLINIKK AS
NOK 13.1m rev. · NOK 1.2m profit

RØYKEN OG OMEGN DYREKLINIKK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RØYKEN OG OMEGN DYREKLINIKK AS

Who owns RØYKEN OG OMEGN DYREKLINIKK AS?

CHRISTINE RØNNING KVAM is the largest registered owner, with 100.0%.

What is the revenue of RØYKEN OG OMEGN DYREKLINIKK AS?

RØYKEN OG OMEGN DYREKLINIKK AS had revenue of NOK 13.1m in 2025.

Who is the general manager of RØYKEN OG OMEGN DYREKLINIKK AS?

Christine Rønning Kvam is registered as general manager of RØYKEN OG OMEGN DYREKLINIKK AS.

Where is RØYKEN OG OMEGN DYREKLINIKK AS based?

RØYKEN OG OMEGN DYREKLINIKK AS has its business address in Røyken.

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.