BIZTRAC BETA
Computer consultancy and computer facilities management activities

SAMSTØ AS

Org. no. 989253085 Limited company (AS) Stavanger Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 467,000
Operating profit NOK −246,000
Equity NOK 6.3m
Incorporated 2005
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−246k kr).

SAMSTØ AS is registered as a limited company in Stavanger, Rogaland with organisation number 989253085. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 10000 shares. The company's stated purpose is: “Konsulenttjenester innen prosjektutvikling.”. The most recent filed accounts, for the 2024 financial year, show NOK 467,000 in revenue and NOK −246,000 in operating profit.

Key figures · 2024

Revenue
NOK 467,000
Operating profit
NOK −246,000
Equity
NOK 6.3m
Est. value
NOK 3.7m

Financial health · 2024

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

Who owns SAMSTØ AS?

PÅL VIGMOSTAD
SAMSTØ AS
NOK 467,000 rev. · NOK −246,000 profit

SAMSTØ AS has 2 registered shareholders:

All shareholders and roles →

Which companies does SAMSTØ AS own?

SAMSTØ AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SAMSTØ AS

Who owns SAMSTØ AS?

PÅL VIGMOSTAD is the largest registered owner, with 70.0%.

What is the revenue of SAMSTØ AS?

SAMSTØ AS had revenue of NOK 467,000 in 2024.

Who is the general manager of SAMSTØ AS?

Pål Vigmostad is registered as general manager of SAMSTØ AS.

Where is SAMSTØ AS based?

SAMSTØ AS has its business address in Stavanger.

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.