BIZTRAC BETA
Manufacture of bodies and coachwork for motor vehicles; manufacture of trailers and semi-trailers

VALSTADSVINGEN EIENDOM AS

Org. no. 997365542 Limited company (AS) Gjerdrum Incorporated 2011 Active
Ownership graph ↗
Operating profit NOK −56,000
Equity NOK 307,000
Incorporated 2011
Share capital NOK 486,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−56k kr).

VALSTADSVINGEN EIENDOM AS is registered as a limited company in Gjerdrum, Akershus with organisation number 997365542. The business is classified under manufacture of bodies and coachwork for motor vehicles; manufacture of trailers and semi-trailers (NACE 29.200). The company was incorporated in 2011. Registered share capital is NOK 486,000, divided into 500 shares. The company's stated purpose is: “Selskapets virksomhet er selv, gjennom hel- eller deleide selskaper eller ved samarbeid med andre virksomheter, å eie og drive fast eiendom, herunder kjøp og salg.”.

Key figures · 2024

Operating profit
NOK −56,000
Equity
NOK 307,000
Est. value
NOK 360,000

Financial health · 2024

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
26.9%
Good
Equity as a share of total capital

Who owns VALSTADSVINGEN EIENDOM AS?

JAN OLAV MARTINSEN HOLDING AS
VALSTADSVINGEN EIENDOM AS
· NOK −56,000 profit

VALSTADSVINGEN EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about VALSTADSVINGEN EIENDOM AS

Who owns VALSTADSVINGEN EIENDOM AS?

JAN OLAV MARTINSEN HOLDING AS is the largest registered owner, with 66.0%.

Who is the general manager of VALSTADSVINGEN EIENDOM AS?

Jan Olav Martinsen is registered as general manager of VALSTADSVINGEN EIENDOM AS.

Where is VALSTADSVINGEN EIENDOM AS based?

VALSTADSVINGEN EIENDOM AS has its business address in Gjerdrum.

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.