BIZTRAC BETA
Activities of specialist physicians, other than psychiatrists

SANDVIKA REUMATOLOGI DRIFT AS

Org. no. 929522907 Limited company (AS) Bærum Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 1.3m
Operating profit NOK 528,000
Equity NOK 32,000
Incorporated 2022
Share capital NOK 30,000

SANDVIKA REUMATOLOGI DRIFT AS is registered as a limited company in Bærum, Akershus with organisation number 929522907. The business is classified under activities of specialist physicians, other than psychiatrists (NACE 86.221). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Forestå drift og administrasjon av reumatologivirksomhet og annet som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.3m in revenue and NOK 528,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.3m
Operating profit
NOK 528,000
Equity
NOK 32,000
Est. value
NOK 1.7m

Financial health · 2024

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

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

Who owns SANDVIKA REUMATOLOGI DRIFT AS?

SANDVIKA REUMATOLOGIPRAKSIS AS
SANDVIKA REUMATOLOGI DRIFT AS
NOK 1.3m rev. · NOK 528,000 profit

SANDVIKA REUMATOLOGI DRIFT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SANDVIKA REUMATOLOGI DRIFT AS

Who owns SANDVIKA REUMATOLOGI DRIFT AS?

SANDVIKA REUMATOLOGIPRAKSIS AS is the largest registered owner, with 100.0%.

What is the revenue of SANDVIKA REUMATOLOGI DRIFT AS?

SANDVIKA REUMATOLOGI DRIFT AS had revenue of NOK 1.3m in 2024.

Where is SANDVIKA REUMATOLOGI DRIFT AS based?

SANDVIKA REUMATOLOGI DRIFT AS has its business address in Sandvika.

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.