BIZTRAC BETA
Veterinary activities

JÆREN DYREHELSE AS

Org. no. 916321724 Limited company (AS) Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 4.2m
Operating profit NOK −377,000
Equity NOK −604,000
Incorporated 2015
Employees 5
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−604k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−377k kr).

JÆREN DYREHELSE AS is registered as a limited company in Hå, Rogaland with organisation number 916321724. The business is classified under veterinary activities (NACE 75.000). The company was incorporated in 2015 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Å drive veterinær- og andre helserelaterte tjenester på dyr i ulik størrelse samt hva som hermed måtte stå i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.2m in revenue and NOK −377,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.2m
Operating profit
NOK −377,000
Equity
NOK −604,000

Financial health · 2025

Liquidity
0.28
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-255.4%
Weak
Equity as a share of total capital

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

Who owns JÆREN DYREHELSE AS?

MARIUS USVALTAS
JÆREN DYREHELSE AS
NOK 4.2m rev. · NOK −377,000 profit

JÆREN DYREHELSE AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about JÆREN DYREHELSE AS

Who owns JÆREN DYREHELSE AS?

MARIUS USVALTAS is the largest registered owner, with 55.0%.

What is the revenue of JÆREN DYREHELSE AS?

JÆREN DYREHELSE AS had revenue of NOK 4.2m in 2025.

Where is JÆREN DYREHELSE AS based?

JÆREN DYREHELSE AS has its business address in Varhaug.

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.