BIZTRAC BETA
Veterinary activities

LILLEHAMMER DYREKLINIKK AS

Org. no. 993974161 Limited company (AS) Lillehammer Incorporated 2009 Active
Ownership graph ↗
Revenue 2025 NOK 14.6m
Operating profit NOK 650,000
Equity NOK 2.6m
Incorporated 2009
Employees 20
Share capital NOK 200,000

LILLEHAMMER DYREKLINIKK AS is registered as a limited company in Lillehammer, Innlandet with organisation number 993974161. The business is classified under veterinary activities (NACE 75.000). The company was incorporated in 2009 and has 20 registered employees. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Dyrlegetjenester, salg av handelsvarer og deltakelse i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 14.6m in revenue and NOK 650,000 in operating profit.

Key figures · 2025

Revenue
NOK 14.6m
Operating profit
NOK 650,000
Equity
NOK 2.6m
Est. value
NOK 4.5m

Financial health · 2025

Liquidity
2.17
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
48.8%
Very good
Equity as a share of total capital

Who owns LILLEHAMMER DYREKLINIKK AS?

GISLE ERITSVÆR
LILLEHAMMER DYREKLINIKK AS
NOK 14.6m rev. · NOK 650,000 profit

LILLEHAMMER DYREKLINIKK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LILLEHAMMER DYREKLINIKK AS

Who owns LILLEHAMMER DYREKLINIKK AS?

GISLE ERITSVÆR is the largest registered owner, with 100.0%.

What is the revenue of LILLEHAMMER DYREKLINIKK AS?

LILLEHAMMER DYREKLINIKK AS had revenue of NOK 14.6m in 2025.

Who is the general manager of LILLEHAMMER DYREKLINIKK AS?

Gisle Eritsvær is registered as general manager of LILLEHAMMER DYREKLINIKK AS.

Where is LILLEHAMMER DYREKLINIKK AS based?

LILLEHAMMER DYREKLINIKK AS has its business address in Lillehammer.

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.