BIZTRAC BETA
Veterinary activities

BERGEN KATTEKLINIKK AS

Org. no. 919323620 Limited company (AS) Bergen Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 6.2m
Operating profit NOK −650,000
Equity NOK 132,000
Incorporated 2017
Employees 8
Share capital NOK 100,000

Signals

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

BERGEN KATTEKLINIKK AS is registered as a limited company in Bergen, Vestland with organisation number 919323620. The business is classified under veterinary activities (NACE 75.000). The company was incorporated in 2017 and has 8 registered employees. Registered share capital is NOK 100,000, divided into 2000 shares. The company's stated purpose is: “Å drive veterinærvirksomhet og annen virksomhet som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.2m in revenue and NOK −650,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.2m
Operating profit
NOK −650,000
Equity
NOK 132,000
Est. value
NOK 6.6m

Financial health · 2025

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

Who owns BERGEN KATTEKLINIKK AS?

EMPET AS
BERGEN KATTEKLINIKK AS
NOK 6.2m rev. · NOK −650,000 profit

BERGEN KATTEKLINIKK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BERGEN KATTEKLINIKK AS

Who owns BERGEN KATTEKLINIKK AS?

EMPET AS is the largest registered owner, with 100.0%.

What is the revenue of BERGEN KATTEKLINIKK AS?

BERGEN KATTEKLINIKK AS had revenue of NOK 6.2m in 2025.

Who is the general manager of BERGEN KATTEKLINIKK AS?

Ida Schiander is registered as general manager of BERGEN KATTEKLINIKK AS.

Where is BERGEN KATTEKLINIKK AS based?

BERGEN KATTEKLINIKK AS has its business address in Bergen.

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.