BIZTRAC BETA
Veterinary activities

VETERINÆR KRISTIN LUND-HOTVEDT AS

Org. no. 918709142 Limited company (AS) Oslo Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 1.7m
Operating profit NOK −53,000
Equity NOK 7,000
Incorporated 2017
Share capital NOK 30,000

Signals

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

VETERINÆR KRISTIN LUND-HOTVEDT AS is registered as a limited company in Oslo, Oslo with organisation number 918709142. The business is classified under veterinary activities (NACE 75.000). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Ambulerende veterinærpraksis for hest, og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.7m in revenue and NOK −53,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.7m
Operating profit
NOK −53,000
Equity
NOK 7,000
Est. value
NOK 1.7m

Financial health · 2025

Liquidity
0.52
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
0.6%
Weak
Equity as a share of total capital

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

Who owns VETERINÆR KRISTIN LUND-HOTVEDT AS?

KRISTIN LUND-HOTVEDT
VETERINÆR KRISTIN LUND-HOTVEDT AS
NOK 1.7m rev. · NOK −53,000 profit

VETERINÆR KRISTIN LUND-HOTVEDT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VETERINÆR KRISTIN LUND-HOTVEDT AS

Who owns VETERINÆR KRISTIN LUND-HOTVEDT AS?

KRISTIN LUND-HOTVEDT is the largest registered owner, with 100.0%.

What is the revenue of VETERINÆR KRISTIN LUND-HOTVEDT AS?

VETERINÆR KRISTIN LUND-HOTVEDT AS had revenue of NOK 1.7m in 2025.

Where is VETERINÆR KRISTIN LUND-HOTVEDT AS based?

VETERINÆR KRISTIN LUND-HOTVEDT AS has its business address in Oslo.

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.