BIZTRAC BETA
Uoppgitt

STORSKARVEN INVEST AS

Org. no. 926085069 Limited company (AS) Skaun Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −17,000
Equity NOK 979,000
Incorporated 2020
Share capital NOK 57,000

Signals

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

STORSKARVEN INVEST AS is registered as a limited company in Skaun, Trøndelag with organisation number 926085069. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 57,000, divided into 300 shares. The company's stated purpose is: “Investering aksjer og andeler i andre selskaper, investering i fast eiendom og annen næringsvirksomhet og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −17,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −17,000
Equity
NOK 979,000
Est. value
NOK 1.2m

Financial health · 2025

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

Who owns STORSKARVEN INVEST AS?

VIDAR KRISTIANSEN
STORSKARVEN INVEST AS
NOK 0 rev. · NOK −17,000 profit

STORSKARVEN INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does STORSKARVEN INVEST AS own?

STORSKARVEN INVEST AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about STORSKARVEN INVEST AS

Who owns STORSKARVEN INVEST AS?

VIDAR KRISTIANSEN is the largest registered owner, with 100.0%.

What is the revenue of STORSKARVEN INVEST AS?

STORSKARVEN INVEST AS had revenue of NOK 0 in 2025.

Where is STORSKARVEN INVEST AS based?

STORSKARVEN INVEST AS has its business address in Børsa.

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.