BIZTRAC BETA
Repair and maintenance of motor vehicles

VSGS AS

Org. no. 993186104 Limited company (AS) Trondheim Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 5.2m
Operating profit NOK 3.0m
Equity NOK 21.8m
Incorporated 2008
Share capital NOK 14.1m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

VSGS AS is registered as a limited company in Trondheim, Trøndelag with organisation number 993186104. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2008. Registered share capital is NOK 14.1m, divided into 14100000 shares. The company's stated purpose is: “Utleie av eiendom og utstyr, salg av mekaniker- og administrasjonstjenester.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.2m in revenue and NOK 3.0m in operating profit.

Key figures · 2024

Revenue
NOK 5.2m
Operating profit
NOK 3.0m
Equity
NOK 21.8m
Est. value
NOK 22.5m

Financial health · 2024

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

Who owns VSGS AS?

VINSNESBAKK EIENDOM AS
VSGS AS
NOK 5.2m rev. · NOK 3.0m profit

VSGS AS has 3 registered shareholders:

All shareholders and roles →

Which companies does VSGS AS own?

VSGS AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about VSGS AS

Who owns VSGS AS?

VINSNESBAKK EIENDOM AS is the largest registered owner, with 64.8%.

What is the revenue of VSGS AS?

VSGS AS had revenue of NOK 5.2m in 2024.

Who is the general manager of VSGS AS?

Harald Vinsnesbakk is registered as general manager of VSGS AS.

Where is VSGS AS based?

VSGS AS has its business address in Heimdal.

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.