BIZTRAC BETA
Veterinary activities

ULVENVETERINÆR AS

Org. no. 935677645 Limited company (AS) Selbu Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 552,000
Operating profit NOK 136,000
Equity NOK 136,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-05-13 Adresseendring registrert 2026-05-13.

ULVENVETERINÆR AS is registered as a limited company in Selbu, Trøndelag with organisation number 935677645. 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: “Selge varer og tjenester innen veterinærmedisin, og annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 552,000 in revenue and NOK 136,000 in operating profit.

Key figures · 2025

Revenue
NOK 552,000
Operating profit
NOK 136,000
Equity
NOK 136,000
Est. value
NOK 533,000

Financial health · 2025

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

Who owns ULVENVETERINÆR AS?

OLE ULVEN
ULVENVETERINÆR AS
NOK 552,000 rev. · NOK 136,000 profit

ULVENVETERINÆR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ULVENVETERINÆR AS

Who owns ULVENVETERINÆR AS?

OLE ULVEN is the largest registered owner, with 100.0%.

What is the revenue of ULVENVETERINÆR AS?

ULVENVETERINÆR AS had revenue of NOK 552,000 in 2025.

Who is the general manager of ULVENVETERINÆR AS?

Ole Ulven is registered as general manager of ULVENVETERINÆR AS.

Where is ULVENVETERINÆR AS based?

ULVENVETERINÆR AS has its business address in Selbu.

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.