BIZTRAC BETA
General medical practice activities

SOLSIKKEN LEGEPRAKSIS AS

Org. no. 922133204 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 147,000
Operating profit NOK −1.7m
Equity NOK 5.7m
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,7 mill kr).

SOLSIKKEN LEGEPRAKSIS AS is registered as a limited company in Oslo, Oslo with organisation number 922133204. 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 30000 shares. The company's stated purpose is: “Allmennpraksis.”. The most recent filed accounts, for the 2024 financial year, show NOK 147,000 in revenue and NOK −1.7m in operating profit.

Key figures · 2024

Revenue
NOK 147,000
Operating profit
NOK −1.7m
Equity
NOK 5.7m
Est. value
NOK 3.6m

Financial health · 2024

Liquidity
0.40
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
56.3%
Very good
Equity as a share of total capital

Who owns SOLSIKKEN LEGEPRAKSIS AS?

PERAPAKARAN ARULANANDAM
SOLSIKKEN LEGEPRAKSIS AS
NOK 147,000 rev. · NOK −1.7m profit

SOLSIKKEN LEGEPRAKSIS AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SOLSIKKEN LEGEPRAKSIS AS own?

SOLSIKKEN LEGEPRAKSIS AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SOLSIKKEN LEGEPRAKSIS AS

Who owns SOLSIKKEN LEGEPRAKSIS AS?

PERAPAKARAN ARULANANDAM is the largest registered owner, with 100.0%.

What is the revenue of SOLSIKKEN LEGEPRAKSIS AS?

SOLSIKKEN LEGEPRAKSIS AS had revenue of NOK 147,000 in 2024.

Where is SOLSIKKEN LEGEPRAKSIS AS based?

SOLSIKKEN LEGEPRAKSIS 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 15.06.2026.

Report a problem

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