BIZTRAC BETA
Computing infrastructure, data processing, hosting and related activities

VASSHUS INVEST AS

Org. no. 920675360 Limited company (AS) Sandnes Incorporated 2018 Active
Ownership graph ↗
Operating profit NOK −27,000
Equity NOK 1.9m
Incorporated 2018
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−27k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

VASSHUS INVEST AS is registered as a limited company in Sandnes, Rogaland with organisation number 920675360. The business is classified under computing infrastructure, data processing, hosting and related activities (NACE 63.100). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Utvinning av digital valuta, kjøp og salg av tilknyttet utstyr som datamaskiner, servere m.m. Kjøp og salg av alle typer digital valuta, medvirke i andre selskaper innen samme virksomhet, samt alt som hører naturlig til dette.”.

Key figures · 2025

Operating profit
NOK −27,000
Equity
NOK 1.9m
Est. value
NOK 3.5m

Financial health · 2025

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

Who owns VASSHUS INVEST AS?

VASSHUS AS
VASSHUS INVEST AS
· NOK −27,000 profit

VASSHUS INVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VASSHUS INVEST AS

Who owns VASSHUS INVEST AS?

VASSHUS AS is the largest registered owner, with 100.0%.

Who is the general manager of VASSHUS INVEST AS?

Runar Sørbø is registered as general manager of VASSHUS INVEST AS.

Where is VASSHUS INVEST AS based?

VASSHUS INVEST AS has its business address in Sandnes.

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.