biztrac. BETA
COMPANY REGISTER PROFILE
997259785 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Veterinary activities

TVEIT DYREKLINIKK AS

Org. no. 997259785 Limited company (AS) Kristiansand Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 4.7m
Operating profit NOK 885,000
Equity NOK 1.2m
Incorporated 2011
Employees 5
Share capital NOK 100,000

TVEIT DYREKLINIKK AS is registered as a limited company in Kristiansand, Agder with organisation number 997259785. The business is classified under veterinary activities (NACE 75.000). The company was incorporated in 2011 and has 5 registered employees. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Veterinærtjenester og salg av relaterte produkter som dyrlege.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.7m in revenue and NOK 885,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.7m
▼ −8 %
Operating profit
NOK 885,000
▼ −31 %
Equity
NOK 1.2m
▼ −12 %
Est. value
NOK 4.9m

Financial health · 2025

Liquidity
1.62
Good
Current assets ÷ current liabilities
Profitability
46.1%
Very good
Return on total assets
Solidity
63.5%
Very good
Equity as a share of total capital

Who owns TVEIT DYREKLINIKK AS?

TVEIT DYREKLINIKK AS
NOK 4.7m rev. · NOK 885,000 profit

TVEIT DYREKLINIKK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TVEIT DYREKLINIKK AS

Who owns TVEIT DYREKLINIKK AS?

Julia Ryen-Westvik is the largest registered owner, with 100.0%.

What is the revenue of TVEIT DYREKLINIKK AS?

TVEIT DYREKLINIKK AS had revenue of NOK 4.7m in 2025.

Who is the general manager of TVEIT DYREKLINIKK AS?

Julia Ryen-Westvik is registered as general manager of TVEIT DYREKLINIKK AS.

Where is TVEIT DYREKLINIKK AS based?

TVEIT DYREKLINIKK AS has its business address in Tveit.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.