biztrac. BETA
COMPANY REGISTER PROFILE
987444908 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
General medical practice activities

VEITVETKLINIKKEN AS

Org. no. 987444908 Limited company (AS) Oslo Incorporated 2004 Active
Ownership graph ↗
Revenue 2025 NOK 3.7m
Operating profit NOK 203,000
Equity NOK 303,000
Incorporated 2004
Share capital NOK 100,000

VEITVETKLINIKKEN AS is registered as a limited company in Oslo, Oslo with organisation number 987444908. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2004. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Legesenter. Selskapet kan gjennom aksjetegning gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.7m in revenue and NOK 203,000 in operating profit.

Former names: LINDERUDKLINIKKEN AS

Key figures · 2025

Revenue
NOK 3.7m
▲ +13 %
Operating profit
NOK 203,000
▲ +349 %
Equity
NOK 303,000
▲ +122 %
Est. value
NOK 937,000

Financial health · 2025

Liquidity
1.94
Good
Current assets ÷ current liabilities
Profitability
32.5%
Very good
Return on total assets
Solidity
48.6%
Very good
Equity as a share of total capital

Who owns VEITVETKLINIKKEN AS?

VEITVETKLINIKKEN AS
NOK 3.7m rev. · NOK 203,000 profit

VEITVETKLINIKKEN AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about VEITVETKLINIKKEN AS

Who owns VEITVETKLINIKKEN AS?

Ambrin Mirza is the largest registered owner, with 34.0%.

What is the revenue of VEITVETKLINIKKEN AS?

VEITVETKLINIKKEN AS had revenue of NOK 3.7m in 2025.

Who is the general manager of VEITVETKLINIKKEN AS?

Nazia Batool is registered as general manager of VEITVETKLINIKKEN AS.

Where is VEITVETKLINIKKEN AS based?

VEITVETKLINIKKEN 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.