BIZTRAC BETA
General medical practice activities

SVACHRIS AS

Org. no. 998415225 Limited company (AS) Lillehammer Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −85,000
Equity NOK 20.3m
Incorporated 2012
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−85k kr).

SVACHRIS AS is registered as a limited company in Lillehammer, Innlandet with organisation number 998415225. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 3 shares. The company's stated purpose is: “Legevirksomhet, investering i verdipapirer og eiendom og det som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −85,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −85,000
Equity
NOK 20.3m
Est. value
NOK 43.4m

Financial health · 2025

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

Who owns SVACHRIS AS?

SVEIN-ARVE SCHJØLSETH
SVACHRIS AS
NOK 0 rev. · NOK −85,000 profit

SVACHRIS AS has 3 registered shareholders:

All shareholders and roles →

Which companies does SVACHRIS AS own?

SVACHRIS AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about SVACHRIS AS

Who owns SVACHRIS AS?

SVEIN-ARVE SCHJØLSETH is the largest registered owner, with 33.3%.

What is the revenue of SVACHRIS AS?

SVACHRIS AS had revenue of NOK 0 in 2025.

Who is the general manager of SVACHRIS AS?

Svein Arve Schjølseth is registered as general manager of SVACHRIS AS.

Where is SVACHRIS AS based?

SVACHRIS AS has its business address in Lillehammer.

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.