BIZTRAC BETA
Rental and operating of own or leased real estate

SYGARD GUNSTAD EIENDOM AS

Org. no. 891422342 Limited company (AS) Ringebu Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 770,000
Operating profit NOK 298,000
Equity NOK 3.6m
Incorporated 2007
Share capital NOK 200,000

SYGARD GUNSTAD EIENDOM AS is registered as a limited company in Ringebu, Innlandet with organisation number 891422342. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2007. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Oppføre driftsbygning på gnr. 42 bnr. 41 i Ringbu kommune som leies ut til landbruksformål.”. The most recent filed accounts, for the 2024 financial year, show NOK 770,000 in revenue and NOK 298,000 in operating profit.

Key figures · 2024

Revenue
NOK 770,000
Operating profit
NOK 298,000
Equity
NOK 3.6m
Est. value
NOK 3.1m

Financial health · 2024

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

Who owns SYGARD GUNSTAD EIENDOM AS?

JON VALDEMAR DAHL
SYGARD GUNSTAD EIENDOM AS
NOK 770,000 rev. · NOK 298,000 profit

SYGARD GUNSTAD EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SYGARD GUNSTAD EIENDOM AS

Who owns SYGARD GUNSTAD EIENDOM AS?

JON VALDEMAR DAHL is the largest registered owner, with 65.0%.

What is the revenue of SYGARD GUNSTAD EIENDOM AS?

SYGARD GUNSTAD EIENDOM AS had revenue of NOK 770,000 in 2024.

Who is the general manager of SYGARD GUNSTAD EIENDOM AS?

Jon Valdemar Dahl is registered as general manager of SYGARD GUNSTAD EIENDOM AS.

Where is SYGARD GUNSTAD EIENDOM AS based?

SYGARD GUNSTAD EIENDOM AS has its business address in Ringebu.

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.