BIZTRAC BETA
Veterinary activities

LIER DYREKLINIKK AS

Org. no. 999279457 Limited company (AS) Lier Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 5.0m
Operating profit NOK −25,000
Equity NOK −162,000
Incorporated 2012
Employees 5
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−162k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−25k kr).

LIER DYREKLINIKK AS is registered as a limited company in Lier, Buskerud with organisation number 999279457. The business is classified under veterinary activities (NACE 75.000). The company was incorporated in 2012 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Veterinærtjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.0m in revenue and NOK −25,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.0m
Operating profit
NOK −25,000
Equity
NOK −162,000

Financial health · 2025

Liquidity
1.53
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-19.7%
Weak
Equity as a share of total capital

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

Who owns LIER DYREKLINIKK AS?

GRO HEGG
LIER DYREKLINIKK AS
NOK 5.0m rev. · NOK −25,000 profit

LIER DYREKLINIKK AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LIER DYREKLINIKK AS

Who owns LIER DYREKLINIKK AS?

GRO HEGG is the largest registered owner, with 70.0%.

What is the revenue of LIER DYREKLINIKK AS?

LIER DYREKLINIKK AS had revenue of NOK 5.0m in 2025.

Who is the general manager of LIER DYREKLINIKK AS?

Gro Hegg is registered as general manager of LIER DYREKLINIKK AS.

Where is LIER DYREKLINIKK AS based?

LIER DYREKLINIKK AS has its business address in Lier.

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.