BIZTRAC BETA
Landscape service activities

VETRON AS

Org. no. 913600967 Limited company (AS) Jevnaker Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 173,000
Operating profit NOK −173,000
Equity NOK −93,000
Incorporated 2014
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−93k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−173k kr).

VETRON AS is registered as a limited company in Jevnaker, Akershus with organisation number 913600967. The business is classified under landscape service activities (NACE 81.300). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Anleggs- og gartnervirksomhet, snørydding og landbrukstjenester og vedproduksjon.”. The most recent filed accounts, for the 2025 financial year, show NOK 173,000 in revenue and NOK −173,000 in operating profit.

Key figures · 2025

Revenue
NOK 173,000
Operating profit
NOK −173,000
Equity
NOK −93,000

Financial health · 2025

Liquidity
0.01
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-96.4%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns VETRON AS?

TROND VIGGO VESTBY
VETRON AS
NOK 173,000 rev. · NOK −173,000 profit

VETRON AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about VETRON AS

Who owns VETRON AS?

TROND VIGGO VESTBY is the largest registered owner, with 51.0%.

What is the revenue of VETRON AS?

VETRON AS had revenue of NOK 173,000 in 2025.

Who is the general manager of VETRON AS?

Trond Viggo Vestby is registered as general manager of VETRON AS.

Where is VETRON AS based?

VETRON AS has its business address in Jevnaker.

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.