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

VETBYGG HOLDING AS

Org. no. 935813921 Limited company (AS) Volda Incorporated 2025 Active
Operating profit NOK −4,000
Equity NOK 922,000
Incorporated 2025
Share capital NOK 30,000

Signals

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

VETBYGG HOLDING AS is registered as a limited company in Volda, Møre og Romsdal with organisation number 935813921. The business is classified under veterinary activities (NACE 75.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”.

Key figures · 2025

Operating profit
NOK −4,000
Equity
NOK 922,000
Est. value
NOK 9.4m

Financial health · 2025

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

Who owns VETBYGG HOLDING AS?

VETBYGG HOLDING AS
· NOK −4,000 profit

VETBYGG HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VETBYGG HOLDING AS own?

VETBYGG HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about VETBYGG HOLDING AS

Who owns VETBYGG HOLDING AS?

Linn-Anett Hillestad is the largest registered owner, with 100.0%.

Who is the general manager of VETBYGG HOLDING AS?

Linn-Anett Hillestad is registered as general manager of VETBYGG HOLDING AS.

Where is VETBYGG HOLDING AS based?

VETBYGG HOLDING AS has its business address in Volda.

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.