BIZTRAC BETA
Accounting and bookkeeping

VS REGNSKAP AS

Org. no. 950308508 Limited company (AS) Haugesund Incorporated 1988 Active
Ownership graph ↗
Revenue 2025 NOK 4.6m
Operating profit NOK 148,000
Equity NOK 543,000
Incorporated 1988
Employees 5
Share capital NOK 30,000

VS REGNSKAP AS is registered as a limited company in Haugesund, Rogaland with organisation number 950308508. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 1988 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Drift av regnskapskontor og andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.6m in revenue and NOK 148,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.6m
Operating profit
NOK 148,000
Equity
NOK 543,000
Est. value
NOK 1.0m

Financial health · 2025

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

Who owns VS REGNSKAP AS?

KRISTIN SALTVEIT
VS REGNSKAP AS
NOK 4.6m rev. · NOK 148,000 profit

VS REGNSKAP AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about VS REGNSKAP AS

Who owns VS REGNSKAP AS?

KRISTIN SALTVEIT is the largest registered owner, with 60.0%.

What is the revenue of VS REGNSKAP AS?

VS REGNSKAP AS had revenue of NOK 4.6m in 2025.

Who is the general manager of VS REGNSKAP AS?

Kristin Saltveit is registered as general manager of VS REGNSKAP AS.

Where is VS REGNSKAP AS based?

VS REGNSKAP AS has its business address in Haugesund.

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.