BIZTRAC BETA
Veterinary activities

OS DYREKLINIKK AS

Org. no. 986551700 Limited company (AS) Bjørnafjorden Incorporated 2004 Active
Ownership graph ↗
Revenue 2024 NOK 15.8m
Operating profit NOK −208,000
Equity NOK 2.5m
Incorporated 2004
Employees 16
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−208k kr).

OS DYREKLINIKK AS is registered as a limited company in Bjørnafjorden, Vestland with organisation number 986551700. The business is classified under veterinary activities (NACE 75.000). The company was incorporated in 2004 and has 16 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drive veterinærvirksomhet, smådyrklinikk samt annen virksomhet som faller naturlig inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 15.8m in revenue and NOK −208,000 in operating profit.

Key figures · 2024

Revenue
NOK 15.8m
Operating profit
NOK −208,000
Equity
NOK 2.5m
Est. value
NOK 17.7m

Financial health · 2024

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

Who owns OS DYREKLINIKK AS?

EVA KRISTIN LUNDE
OS DYREKLINIKK AS
NOK 15.8m rev. · NOK −208,000 profit

OS DYREKLINIKK AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about OS DYREKLINIKK AS

Who owns OS DYREKLINIKK AS?

EVA KRISTIN LUNDE is the largest registered owner, with 70.0%.

What is the revenue of OS DYREKLINIKK AS?

OS DYREKLINIKK AS had revenue of NOK 15.8m in 2024.

Who is the general manager of OS DYREKLINIKK AS?

Eva Kristin Lunde is registered as general manager of OS DYREKLINIKK AS.

Where is OS DYREKLINIKK AS based?

OS DYREKLINIKK AS has its business address in Os.

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.