BIZTRAC BETA
Activities of specialist physicians, other than psychiatrists

BRINIK MEDICAL AS

Org. no. 832539732 Limited company (AS) Stord Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK 8,000
Incorporated 2023
Share capital NOK 30,000

BRINIK MEDICAL AS is registered as a limited company in Stord, Vestland with organisation number 832539732. The business is classified under activities of specialist physicians, other than psychiatrists (NACE 86.221). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Tilby spesialiserte medisinske tjenester innen (spesifikk medisinsk spesialitet), inkludert, men ikke begrenset til, diagnose, behandling, oppfølging og rådgivning til pasienter.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 8,000
Est. value
NOK 13,000

Financial health · 2025

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

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

Who owns BRINIK MEDICAL AS?

WALEED SHAIE BRISAM
BRINIK MEDICAL AS
NOK 0 rev. · NOK 0 profit

BRINIK MEDICAL AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BRINIK MEDICAL AS

Who owns BRINIK MEDICAL AS?

WALEED SHAIE BRISAM is the largest registered owner, with 60.0%.

What is the revenue of BRINIK MEDICAL AS?

BRINIK MEDICAL AS had revenue of NOK 0 in 2025.

Who is the general manager of BRINIK MEDICAL AS?

Maja Nikolic is registered as general manager of BRINIK MEDICAL AS.

Where is BRINIK MEDICAL AS based?

BRINIK MEDICAL AS has its business address in Stord.

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.