BIZTRAC BETA
Veterinary activities

STANGE DYREKLINIKK AS

Org. no. 923658548 Limited company (AS) Stange Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 11.9m
Operating profit NOK 195,000
Equity NOK 554,000
Incorporated 2019
Employees 15
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

STANGE DYREKLINIKK AS is registered as a limited company in Stange, Innlandet with organisation number 923658548. The business is classified under veterinary activities (NACE 75.000). The company was incorporated in 2019 and has 15 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Drive veterinærvirksomhet og annen virksomhet som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 11.9m in revenue and NOK 195,000 in operating profit.

Key figures · 2024

Revenue
NOK 11.9m
Operating profit
NOK 195,000
Equity
NOK 554,000
Est. value
NOK 1.2m

Financial health · 2024

Liquidity
1.19
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
25.0%
Good
Equity as a share of total capital

Who owns STANGE DYREKLINIKK AS?

EMPET AS
STANGE DYREKLINIKK AS
NOK 11.9m rev. · NOK 195,000 profit

STANGE DYREKLINIKK AS has 1 registered shareholder:

All shareholders and roles →

Group structure

STANGE DYREKLINIKK AS er morselskap for 23 datterselskaper:

Frequently asked questions about STANGE DYREKLINIKK AS

Who owns STANGE DYREKLINIKK AS?

EMPET AS is the largest registered owner, with 100.0%.

What is the revenue of STANGE DYREKLINIKK AS?

STANGE DYREKLINIKK AS had revenue of NOK 11.9m in 2024.

Where is STANGE DYREKLINIKK AS based?

STANGE DYREKLINIKK AS has its business address in Ottestad.

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.