BIZTRAC BETA
Veterinary activities

VETERINÆRVAKTA I ÅL OG HOL AS

Org. no. 990422559 Limited company (AS) Ål Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 11.4m
Operating profit NOK 115,000
Equity NOK 1.3m
Incorporated 2006
Employees 15
Share capital NOK 167,000

VETERINÆRVAKTA I ÅL OG HOL AS is registered as a limited company in Ål, Buskerud with organisation number 990422559. The business is classified under veterinary activities (NACE 75.000). The company was incorporated in 2006 and has 15 registered employees. Registered share capital is NOK 167,000, divided into 1670 shares. The company's stated purpose is: “Veterinærtjenester og andre produkter/tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 11.4m in revenue and NOK 115,000 in operating profit.

Key figures · 2024

Revenue
NOK 11.4m
Operating profit
NOK 115,000
Equity
NOK 1.3m
Est. value
NOK 978,000

Financial health · 2024

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

Who owns VETERINÆRVAKTA I ÅL OG HOL AS?

ÅDNE KVAMMEN
VETERINÆRVAKTA I ÅL OG HOL AS
NOK 11.4m rev. · NOK 115,000 profit

VETERINÆRVAKTA I ÅL OG HOL AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about VETERINÆRVAKTA I ÅL OG HOL AS

Who owns VETERINÆRVAKTA I ÅL OG HOL AS?

ÅDNE KVAMMEN is the largest registered owner, with 20.0%.

What is the revenue of VETERINÆRVAKTA I ÅL OG HOL AS?

VETERINÆRVAKTA I ÅL OG HOL AS had revenue of NOK 11.4m in 2024.

Who is the general manager of VETERINÆRVAKTA I ÅL OG HOL AS?

Hedvig Johanne Rud is registered as general manager of VETERINÆRVAKTA I ÅL OG HOL AS.

Where is VETERINÆRVAKTA I ÅL OG HOL AS based?

VETERINÆRVAKTA I ÅL OG HOL AS has its business address in Ål.

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.