BIZTRAC BETA
Rental and operating of own or leased real estate

HELVIG GARD AS

Org. no. 988088412 Limited company (AS) Eigersund Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 20,000
Operating profit NOK 12,000
Equity NOK 6.0m
Incorporated 2005
Share capital NOK 1.7m

HELVIG GARD AS is registered as a limited company in Eigersund, Rogaland with organisation number 988088412. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 1.7m, divided into 1 shares. The company's stated purpose is: “Investering i aksjer og eiendommer og der til hørende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 20,000 in revenue and NOK 12,000 in operating profit.

Key figures · 2025

Revenue
NOK 20,000
Operating profit
NOK 12,000
Equity
NOK 6.0m
Est. value
NOK 4.2m

Financial health · 2025

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

Who owns HELVIG GARD AS?

SVEIN HELVIG
HELVIG GARD AS
NOK 20,000 rev. · NOK 12,000 profit

HELVIG GARD AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HELVIG GARD AS own?

HELVIG GARD AS holds stakes in 2 companies:

See the full ownership structure →

Group structure

HELVIG GARD AS er morselskap for 2 datterselskaper:

Frequently asked questions about HELVIG GARD AS

Who owns HELVIG GARD AS?

SVEIN HELVIG is the largest registered owner, with 100.0%.

What is the revenue of HELVIG GARD AS?

HELVIG GARD AS had revenue of NOK 20,000 in 2025.

Who is the general manager of HELVIG GARD AS?

Svein Helvig is registered as general manager of HELVIG GARD AS.

Where is HELVIG GARD AS based?

HELVIG GARD AS has its business address in Hellvik.

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.