BIZTRAC BETA
Rental and operating of own or leased real estate

SYVERSTAD GÅRD SELSKAP AS

Org. no. 922390134 Limited company (AS) Asker Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 6.3m
Operating profit NOK 312,000
Equity NOK 197,000
Incorporated 2019
Employees 25
Share capital NOK 30,000

SYVERSTAD GÅRD SELSKAP AS is registered as a limited company in Asker, Akershus with organisation number 922390134. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019 and has 25 registered employees. Registered share capital is NOK 30,000, divided into 2000 shares. The company's stated purpose is: “Utleie av selskapslokale og det som naturlig hører til.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.3m in revenue and NOK 312,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.3m
Operating profit
NOK 312,000
Equity
NOK 197,000
Est. value
NOK 956,000

Financial health · 2025

Liquidity
1.01
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
17.5%
Satisfactory
Equity as a share of total capital

Who owns SYVERSTAD GÅRD SELSKAP AS?

SIMEN FOSSUM
SYVERSTAD GÅRD SELSKAP AS
NOK 6.3m rev. · NOK 312,000 profit

SYVERSTAD GÅRD SELSKAP AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SYVERSTAD GÅRD SELSKAP AS

Who owns SYVERSTAD GÅRD SELSKAP AS?

SIMEN FOSSUM is the largest registered owner, with 50.0%.

What is the revenue of SYVERSTAD GÅRD SELSKAP AS?

SYVERSTAD GÅRD SELSKAP AS had revenue of NOK 6.3m in 2025.

Who is the general manager of SYVERSTAD GÅRD SELSKAP AS?

Simen Fossum is registered as general manager of SYVERSTAD GÅRD SELSKAP AS.

Where is SYVERSTAD GÅRD SELSKAP AS based?

SYVERSTAD GÅRD SELSKAP AS has its business address in Nesbru.

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.