BIZTRAC BETA
Veterinary activities

STORHAUG DYREKLINIKK AS

Org. no. 931949187 Limited company (AS) Stavanger Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 437,000
Operating profit NOK −17,000
Equity NOK 1,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

STORHAUG DYREKLINIKK AS is registered as a limited company in Stavanger, Rogaland with organisation number 931949187. The business is classified under veterinary activities (NACE 75.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Veterinærtjenester og dyreklinikk”. The most recent filed accounts, for the 2024 financial year, show NOK 437,000 in revenue and NOK −17,000 in operating profit.

Key figures · 2024

Revenue
NOK 437,000
Operating profit
NOK −17,000
Equity
NOK 1,000
Est. value
NOK 459,000

Financial health · 2024

Liquidity
0.79
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
1.8%
Weak
Equity as a share of total capital

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

Who owns STORHAUG DYREKLINIKK AS?

AVIV LIVNAT
STORHAUG DYREKLINIKK AS
NOK 437,000 rev. · NOK −17,000 profit

STORHAUG DYREKLINIKK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STORHAUG DYREKLINIKK AS

Who owns STORHAUG DYREKLINIKK AS?

AVIV LIVNAT is the largest registered owner, with 100.0%.

What is the revenue of STORHAUG DYREKLINIKK AS?

STORHAUG DYREKLINIKK AS had revenue of NOK 437,000 in 2024.

Who is the general manager of STORHAUG DYREKLINIKK AS?

Aviv Livnat is registered as general manager of STORHAUG DYREKLINIKK AS.

Where is STORHAUG DYREKLINIKK AS based?

STORHAUG DYREKLINIKK AS has its business address in Stavanger.

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.