BIZTRAC BETA
General medical practice activities

CASMED AS

Org. no. 922155631 Limited company (AS) Skien Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 3.4m
Operating profit NOK 521,000
Equity NOK 204,000
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

CASMED AS is registered as a limited company in Skien, Telemark with organisation number 922155631. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Levere helsetjenester, eiendomsforvaltning samt relaterte virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.4m in revenue and NOK 521,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.4m
Operating profit
NOK 521,000
Equity
NOK 204,000
Est. value
NOK 2.2m

Financial health · 2024

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

Who owns CASMED AS?

CASPER HOLMBERG HOLDING AS
CASMED AS
NOK 3.4m rev. · NOK 521,000 profit

CASMED AS has 1 registered shareholder:

All shareholders and roles →

Which companies does CASMED AS own?

CASMED AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about CASMED AS

Who owns CASMED AS?

CASPER HOLMBERG HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of CASMED AS?

CASMED AS had revenue of NOK 3.4m in 2024.

Who is the general manager of CASMED AS?

Casper Holmberg is registered as general manager of CASMED AS.

Where is CASMED AS based?

CASMED AS has its business address in Skien.

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.