BIZTRAC BETA
Veterinary activities

VETERINÆR SVEIN H BAKKE AS

Org. no. 983145728 Limited company (AS) Indre Østfold Incorporated 2001 Active
Ownership graph ↗
Revenue 2025 NOK 2.0m
Operating profit NOK 607,000
Equity NOK 4.1m
Incorporated 2001
Share capital NOK 100,000

VETERINÆR SVEIN H BAKKE AS is registered as a limited company in Indre Østfold, Østfold with organisation number 983145728. The business is classified under veterinary activities (NACE 75.000). The company was incorporated in 2001. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Veterinærvirksomhet, konsulentvirksomhet og undervisning. Selskapet skal også kunne eie eller delta i andre bedrifter.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.0m in revenue and NOK 607,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.0m
Operating profit
NOK 607,000
Equity
NOK 4.1m
Est. value
NOK 4.8m

Financial health · 2025

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

Who owns VETERINÆR SVEIN H BAKKE AS?

SVEIN HALVARD BAKKE
VETERINÆR SVEIN H BAKKE AS
NOK 2.0m rev. · NOK 607,000 profit

VETERINÆR SVEIN H BAKKE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VETERINÆR SVEIN H BAKKE AS

Who owns VETERINÆR SVEIN H BAKKE AS?

SVEIN HALVARD BAKKE is the largest registered owner, with 100.0%.

What is the revenue of VETERINÆR SVEIN H BAKKE AS?

VETERINÆR SVEIN H BAKKE AS had revenue of NOK 2.0m in 2025.

Who is the general manager of VETERINÆR SVEIN H BAKKE AS?

Svein Halvard Bakke is registered as general manager of VETERINÆR SVEIN H BAKKE AS.

Where is VETERINÆR SVEIN H BAKKE AS based?

VETERINÆR SVEIN H BAKKE AS has its business address in Trøgstad.

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.