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

SELE DYREKLINIKK DA

Org. no. 888797432 General partnership with shared liability (DA) Klepp Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 16.1m
Operating profit NOK −12,000
Equity NOK 64,000
Incorporated 2005
Employees 10

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−12k kr).

SELE DYREKLINIKK DA is registered as a general partnership with shared liability in Klepp, Rogaland with organisation number 888797432. The business is classified under veterinary activities (NACE 75.000). The company was incorporated in 2005 and has 10 registered employees. The company's stated purpose is: “Dyreklinikk og ambulatorisk praksis for alle slags dyr.”. The most recent filed accounts, for the 2025 financial year, show NOK 16.1m in revenue and NOK −12,000 in operating profit.

Key figures · 2025

Revenue
NOK 16.1m
▲ +18 %
Operating profit
NOK −12,000
▼ −64 %
Equity
NOK 64,000
▲ +0 %
Est. value
NOK 16.7m

Financial health · 2025

Liquidity
1.23
Satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
2.9%
Weak
Equity as a share of total capital

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

Who owns SELE DYREKLINIKK DA?

No shareholders are registered for SELE DYREKLINIKK DA in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about SELE DYREKLINIKK DA

What is the revenue of SELE DYREKLINIKK DA?

SELE DYREKLINIKK DA had revenue of NOK 16.1m in 2025.

Who is the general manager of SELE DYREKLINIKK DA?

Alfred Hove is registered as general manager of SELE DYREKLINIKK DA.

Where is SELE DYREKLINIKK DA based?

SELE DYREKLINIKK DA has its business address in Kleppe.

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.