BIZTRAC BETA
COMPANY REGISTER PROFILE
914582687 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Rental and operating of own or leased real estate

VELDE GAARD AS

Org. no. 914582687 Limited company (AS) Hjelmeland Incorporated 2014 Active
Ownership graph ↗
Operating profit NOK 0
Incorporated 2014
Share capital NOK 600,000

VELDE GAARD AS is registered as a limited company in Hjelmeland, Rogaland with organisation number 914582687. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2014. Registered share capital is NOK 600,000, divided into 600 shares. The company's stated purpose is: “Bortforpakting av landbruksjord, drift av gården og utleie av gårdsutstyr og verktøy.”.

Key figures · 2025

Operating profit
NOK 0
▲ +100 %

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
–
Not available
Equity as a share of total capital

Who owns VELDE GAARD AS?

VELDE GAARD AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about VELDE GAARD AS

Who owns VELDE GAARD AS?

TORBJØRN VELDE is the largest registered owner, with 25.0%.

Who is the general manager of VELDE GAARD AS?

Ann Mari Velde is registered as general manager of VELDE GAARD AS.

Where is VELDE GAARD AS based?

VELDE GAARD AS has its business address in Hjelmeland.

Property

Business address Randøy Ring 121, 4130 Hjelmeland
Cadastral unit 1133-1/43/0/0
Building Våningshus · 1 unit

2 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.