BIZTRAC BETA
Veterinary activities

SNÅSA DYREKLINIKK AS

Org. no. 913577515 Limited company (AS) Snåsa Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 1.8m
Operating profit NOK 368,000
Equity NOK −317,000
Incorporated 2014
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−317k kr).

SNÅSA DYREKLINIKK AS is registered as a limited company in Snåsa, Trøndelag with organisation number 913577515. The business is classified under veterinary activities (NACE 75.000). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Drive veterinærvirksomhet samt det som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.8m in revenue and NOK 368,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.8m
Operating profit
NOK 368,000
Equity
NOK −317,000
Est. value
NOK 2.7m

Financial health · 2024

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

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

Who owns SNÅSA DYREKLINIKK AS?

THOR JOHAN SKAGET
SNÅSA DYREKLINIKK AS
NOK 1.8m rev. · NOK 368,000 profit

SNÅSA DYREKLINIKK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SNÅSA DYREKLINIKK AS

Who owns SNÅSA DYREKLINIKK AS?

THOR JOHAN SKAGET is the largest registered owner, with 100.0%.

What is the revenue of SNÅSA DYREKLINIKK AS?

SNÅSA DYREKLINIKK AS had revenue of NOK 1.8m in 2024.

Who is the general manager of SNÅSA DYREKLINIKK AS?

Thor Johan Skaget is registered as general manager of SNÅSA DYREKLINIKK AS.

Where is SNÅSA DYREKLINIKK AS based?

SNÅSA DYREKLINIKK AS has its business address in Snåsa.

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.