BIZTRAC BETA
Retail sale of information and communication equipment

SANDVIKA DATA AS

Org. no. 819625832 Limited company (AS) Asker Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −18,000
Equity NOK −5,000
Incorporated 2017
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−5k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−18k kr).

SANDVIKA DATA AS is registered as a limited company in Asker, Akershus with organisation number 819625832. The business is classified under retail sale of information and communication equipment (NACE 47.400). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Konsulenttjenester og salg av datautstyr.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −18,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −18,000
Equity
NOK −5,000

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns SANDVIKA DATA AS?

SVEND OWE JAMTH
SANDVIKA DATA AS
NOK 0 rev. · NOK −18,000 profit

SANDVIKA DATA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SANDVIKA DATA AS

Who owns SANDVIKA DATA AS?

SVEND OWE JAMTH is the largest registered owner, with 100.0%.

What is the revenue of SANDVIKA DATA AS?

SANDVIKA DATA AS had revenue of NOK 0 in 2025.

Who is the general manager of SANDVIKA DATA AS?

Svend Owe Jamth is registered as general manager of SANDVIKA DATA AS.

Where is SANDVIKA DATA AS based?

SANDVIKA DATA AS has its business address in Hvalstad.

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.