BIZTRAC BETA
Accounting and bookkeeping

VIEGO REGNSKAP AS

Org. no. 988394920 Limited company (AS) Kristiansand Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 11.3m
Operating profit NOK 1.7m
Equity NOK 794,000
Incorporated 2005
Employees 13
Share capital NOK 100,000

VIEGO REGNSKAP AS is registered as a limited company in Kristiansand, Agder with organisation number 988394920. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2005 and has 13 registered employees. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Selskapets virksomhet er regnskapsførsel med tilhørende beslektede tjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 11.3m in revenue and NOK 1.7m in operating profit.

Key figures · 2025

Revenue
NOK 11.3m
Operating profit
NOK 1.7m
Equity
NOK 794,000
Est. value
NOK 8.8m

Financial health · 2025

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

Who owns VIEGO REGNSKAP AS?

HELGE STORNES
VIEGO REGNSKAP AS
NOK 11.3m rev. · NOK 1.7m profit

VIEGO REGNSKAP AS has 5 registered shareholders:

All shareholders and roles →

Which companies does VIEGO REGNSKAP AS own?

VIEGO REGNSKAP AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about VIEGO REGNSKAP AS

Who owns VIEGO REGNSKAP AS?

HELGE STORNES is the largest registered owner, with 50.0%.

What is the revenue of VIEGO REGNSKAP AS?

VIEGO REGNSKAP AS had revenue of NOK 11.3m in 2025.

Who is the general manager of VIEGO REGNSKAP AS?

Helge Stornes is registered as general manager of VIEGO REGNSKAP AS.

Where is VIEGO REGNSKAP AS based?

VIEGO REGNSKAP 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.