biztrac. BETA
COMPANY REGISTER PROFILE
932148986 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

SOLSET GÅRD AS

Org. no. 932148986 Limited company (AS) Gausdal Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 244,000
Operating profit NOK −25,000
Equity NOK 94,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−25k kr).

SOLSET GÅRD AS is registered as a limited company in Gausdal, Innlandet with organisation number 932148986. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Gårdsdrift, jord- og skogbruk. Utleie og egenproduksjon.”. The most recent filed accounts, for the 2025 financial year, show NOK 244,000 in revenue and NOK −25,000 in operating profit.

Key figures · 2025

Revenue
NOK 244,000
▼ −51 %
Operating profit
NOK −25,000
▼ −108 %
Equity
NOK 94,000
▼ −34 %
Est. value
NOK 180,000

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
-18.4%
Not satisfactory
Return on total assets
Solidity
100.0%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns SOLSET GÅRD AS?

SOLSET GÅRD AS
NOK 244,000 rev. · NOK −25,000 profit

SOLSET GÅRD AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SOLSET GÅRD AS

Who owns SOLSET GÅRD AS?

Tarald Fiskaa Kverneland is the largest registered owner, with 50.0%.

What is the revenue of SOLSET GÅRD AS?

SOLSET GÅRD AS had revenue of NOK 244,000 in 2025.

Where is SOLSET GÅRD AS based?

SOLSET GÅRD AS has its business address in Vestre Gausdal.

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

Report a problem

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