BIZTRAC BETA
General hospital activities

SØRLANDET PRIVATSYKEHUS AS

Org. no. 919820489 Limited company (AS) Kristiansand Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 11.0m
Operating profit NOK 953,000
Equity NOK 763,000
Incorporated 2017
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.

SØRLANDET PRIVATSYKEHUS AS is registered as a limited company in Kristiansand, Agder with organisation number 919820489. The business is classified under general hospital activities (NACE 86.101). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Drift av sykehustjenester, legetjenester med dertil tilhørende virksomhet samt investering i øvrige selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 11.0m in revenue and NOK 953,000 in operating profit.

Key figures · 2024

Revenue
NOK 11.0m
Operating profit
NOK 953,000
Equity
NOK 763,000
Est. value
NOK 4.8m

Financial health · 2024

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

Who owns SØRLANDET PRIVATSYKEHUS AS?

APPENDIX HOLDING AS
SØRLANDET PRIVATSYKEHUS AS
NOK 11.0m rev. · NOK 953,000 profit

SØRLANDET PRIVATSYKEHUS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SØRLANDET PRIVATSYKEHUS AS

Who owns SØRLANDET PRIVATSYKEHUS AS?

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

What is the revenue of SØRLANDET PRIVATSYKEHUS AS?

SØRLANDET PRIVATSYKEHUS AS had revenue of NOK 11.0m in 2024.

Where is SØRLANDET PRIVATSYKEHUS AS based?

SØRLANDET PRIVATSYKEHUS AS has its business address in Kristiansand S.

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.