BIZTRAC BETA
Research and experimental development on natural sciences and engineering

CINCH MEDICAL AS

Org. no. 932125072 Limited company (AS) Bergen Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 1.6m
Operating profit NOK 867,000
Equity NOK 1.4m
Incorporated 2023
Share capital NOK 94,000

Signals

1 flags
  • Nylig endring 2026-04-15 Aksjekapital registrert 2026-04-15.

CINCH MEDICAL AS is registered as a limited company in Bergen, Vestland with organisation number 932125072. The business is classified under research and experimental development on natural sciences and engineering (NACE 72.100). The company was incorporated in 2023. Registered share capital is NOK 94,000, divided into 94141 shares. The company's stated purpose is: “Utvikling av medisinsk teknologi samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.6m in revenue and NOK 867,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.6m
Operating profit
NOK 867,000
Equity
NOK 1.4m
Est. value
NOK 3.4m

Financial health · 2024

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

Who owns CINCH MEDICAL AS?

VT KARDIO HOLDING AS
CINCH MEDICAL AS
NOK 1.6m rev. · NOK 867,000 profit

CINCH MEDICAL AS has 20+ registered shareholders:

All shareholders and roles →

Frequently asked questions about CINCH MEDICAL AS

Who owns CINCH MEDICAL AS?

VT KARDIO HOLDING AS is the largest registered owner, with 23.0%.

What is the revenue of CINCH MEDICAL AS?

CINCH MEDICAL AS had revenue of NOK 1.6m in 2024.

Who is the general manager of CINCH MEDICAL AS?

Vegard Tuseth is registered as general manager of CINCH MEDICAL AS.

Where is CINCH MEDICAL AS based?

CINCH MEDICAL 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.