BIZTRAC BETA
Buying and selling of own real estate

VETO GJØVIK AS

Org. no. 998938139 Limited company (AS) Gjøvik Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 1.5m
Operating profit NOK −283,000
Equity NOK 3.3m
Incorporated 2012
Share capital NOK 30,000

Signals

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

VETO GJØVIK AS is registered as a limited company in Gjøvik, Innlandet with organisation number 998938139. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investering i andre virksomheter og eiendom. Samt salg av konsulenttjenester. Selskapet skal også kunne drive import, kjøp og salg av motorkjøretøyer.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.5m in revenue and NOK −283,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.5m
Operating profit
NOK −283,000
Equity
NOK 3.3m
Est. value
NOK 4.5m

Financial health · 2025

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

Who owns VETO GJØVIK AS?

VEGARD TORKEHAGEN
VETO GJØVIK AS
NOK 1.5m rev. · NOK −283,000 profit

VETO GJØVIK AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VETO GJØVIK AS own?

VETO GJØVIK AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about VETO GJØVIK AS

Who owns VETO GJØVIK AS?

VEGARD TORKEHAGEN is the largest registered owner, with 100.0%.

What is the revenue of VETO GJØVIK AS?

VETO GJØVIK AS had revenue of NOK 1.5m in 2025.

Where is VETO GJØVIK AS based?

VETO GJØVIK AS has its business address in Gjøvik.

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.