BIZTRAC BETA
Veterinary activities

DYREKLINIKKEN TERTNES AS

Org. no. 911957159 Limited company (AS) Bergen Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 13.5m
Operating profit NOK 2.2m
Equity NOK 92,000
Incorporated 2013
Employees 8
Share capital NOK 30,000

DYREKLINIKKEN TERTNES AS is registered as a limited company in Bergen, Vestland with organisation number 911957159. The business is classified under veterinary activities (NACE 75.000). The company was incorporated in 2013 and has 8 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Veterinærtjenester, kursvirksomhet samt salg av dyrefor og andre relaterte produkter.”. The most recent filed accounts, for the 2024 financial year, show NOK 13.5m in revenue and NOK 2.2m in operating profit.

Key figures · 2024

Revenue
NOK 13.5m
Operating profit
NOK 2.2m
Equity
NOK 92,000
Est. value
NOK 10.4m

Financial health · 2024

Liquidity
0.93
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 DYREKLINIKKEN TERTNES AS?

RKG HOLDING AS
DYREKLINIKKEN TERTNES AS
NOK 13.5m rev. · NOK 2.2m profit

DYREKLINIKKEN TERTNES AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DYREKLINIKKEN TERTNES AS

Who owns DYREKLINIKKEN TERTNES AS?

RKG HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of DYREKLINIKKEN TERTNES AS?

DYREKLINIKKEN TERTNES AS had revenue of NOK 13.5m in 2024.

Who is the general manager of DYREKLINIKKEN TERTNES AS?

Ulf Erlandsen is registered as general manager of DYREKLINIKKEN TERTNES AS.

Where is DYREKLINIKKEN TERTNES AS based?

DYREKLINIKKEN TERTNES AS has its business address in Nyborg.

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.