BIZTRAC BETA
Other captive investment companies

SYAS INVEST AS

Org. no. 891683952 Limited company (AS) Oppdal Incorporated 2007 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −2,000
Equity NOK 1.1m
Incorporated 2007
Share capital NOK 100,000

Signals

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

SYAS INVEST AS is registered as a limited company in Oppdal, Trøndelag with organisation number 891683952. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Investeringsvirksomhet i aksjer og eiendom, konsulentvirksomhet og annet i denne forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −2,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −2,000
Equity
NOK 1.1m
Est. value
NOK 1.0m

Financial health · 2025

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

Who owns SYAS INVEST AS?

STEIN KJARTAN VIK
SYAS INVEST AS
NOK 0 rev. · NOK −2,000 profit

SYAS INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SYAS INVEST AS own?

SYAS INVEST AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about SYAS INVEST AS

Who owns SYAS INVEST AS?

STEIN KJARTAN VIK is the largest registered owner, with 100.0%.

What is the revenue of SYAS INVEST AS?

SYAS INVEST AS had revenue of NOK 0 in 2025.

Who is the general manager of SYAS INVEST AS?

Stein Kjartan Vik is registered as general manager of SYAS INVEST AS.

Where is SYAS INVEST AS based?

SYAS INVEST AS has its business address in Oppdal.

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.