BIZTRAC BETA
Computer consultancy and computer facilities management activities

VIEGO DATA AS

Org. no. 894022582 Limited company (AS) Kristiansand Incorporated 2009 Active
Ownership graph ↗
Revenue 2025 NOK 3.3m
Operating profit NOK −183,000
Equity NOK 188,000
Incorporated 2009
Share capital NOK 100,000

Signals

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

VIEGO DATA AS is registered as a limited company in Kristiansand, Agder with organisation number 894022582. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2009. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Selge programvare og maskinvare for PC knyttet til økonomi/regnskap, samt tilhørende konsulenttjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.3m in revenue and NOK −183,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.3m
Operating profit
NOK −183,000
Equity
NOK 188,000
Est. value
NOK 5.7m

Financial health · 2025

Liquidity
1.19
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
19.6%
Good
Equity as a share of total capital

Who owns VIEGO DATA AS?

STIG DRANGSHOLT
VIEGO DATA AS
NOK 3.3m rev. · NOK −183,000 profit

VIEGO DATA AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about VIEGO DATA AS

Who owns VIEGO DATA AS?

STIG DRANGSHOLT is the largest registered owner, with 50.0%.

What is the revenue of VIEGO DATA AS?

VIEGO DATA AS had revenue of NOK 3.3m in 2025.

Who is the general manager of VIEGO DATA AS?

Henrik Drangsholt is registered as general manager of VIEGO DATA AS.

Where is VIEGO DATA AS based?

VIEGO DATA AS has its business address in Kristiansand S.

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.