BIZTRAC BETA
Veterinary activities

DYREKLINIKKEN I SOGNDAL AS

Org. no. 913691032 Limited company (AS) Sogndal Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 4.9m
Operating profit NOK 818,000
Equity NOK 3.7m
Incorporated 2014
Employees 6
Share capital NOK 100,000

DYREKLINIKKEN I SOGNDAL AS is registered as a limited company in Sogndal, Vestland with organisation number 913691032. The business is classified under veterinary activities (NACE 75.000). The company was incorporated in 2014 and has 6 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Veterinærtenester og det som står i forbindelse med dette og utleige av maskiner.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.9m in revenue and NOK 818,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.9m
Operating profit
NOK 818,000
Equity
NOK 3.7m
Est. value
NOK 6.3m

Financial health · 2024

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

Who owns DYREKLINIKKEN I SOGNDAL AS?

GUNNAR HOFSLUNDSENGEN
DYREKLINIKKEN I SOGNDAL AS
NOK 4.9m rev. · NOK 818,000 profit

DYREKLINIKKEN I SOGNDAL AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about DYREKLINIKKEN I SOGNDAL AS

Who owns DYREKLINIKKEN I SOGNDAL AS?

GUNNAR HOFSLUNDSENGEN is the largest registered owner, with 80.0%.

What is the revenue of DYREKLINIKKEN I SOGNDAL AS?

DYREKLINIKKEN I SOGNDAL AS had revenue of NOK 4.9m in 2024.

Who is the general manager of DYREKLINIKKEN I SOGNDAL AS?

Gunnar Hofslundsengen is registered as general manager of DYREKLINIKKEN I SOGNDAL AS.

Where is DYREKLINIKKEN I SOGNDAL AS based?

DYREKLINIKKEN I SOGNDAL AS has its business address in Sogndal.

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.