biztrac. BETA
COMPANY REGISTER PROFILE
933582108 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Hunting, trapping and related service activities

SOLAVÅG GRUNNEIGARLAG SA

Org. no. 933582108 Co-operation (SA) Sula Incorporated 2024 Active
Revenue 2024 NOK 7,000
Operating profit NOK −5,000
Equity NOK 0
Incorporated 2024

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−5k kr).

SOLAVÅG GRUNNEIGARLAG SA is registered as a co-operation in Sula, Møre og Romsdal with organisation number 933582108. The business is classified under hunting, trapping and related service activities (NACE 01.700). The company was incorporated in 2024. The company's stated purpose is: “Samvirkeforetaket består av grunneierne som har jaktretter i den delen av Solavågsfjellet som tilhører gårdsnummer 64. Hovedformålet er å forvalte viltet og inntektene fra dette på en best mulig måte, både med tanke på naturresursene og grunneierne.”. The most recent filed accounts, for the 2024 financial year, show NOK 7,000 in revenue and NOK −5,000 in operating profit.

Key figures · 2024

Revenue
NOK 7,000
Operating profit
NOK −5,000
Equity
NOK 0

Financial health · 2024

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

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

Who owns SOLAVÅG GRUNNEIGARLAG SA?

No shareholders are registered for SOLAVÅG GRUNNEIGARLAG SA in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about SOLAVÅG GRUNNEIGARLAG SA

What is the revenue of SOLAVÅG GRUNNEIGARLAG SA?

SOLAVÅG GRUNNEIGARLAG SA had revenue of NOK 7,000 in 2024.

Where is SOLAVÅG GRUNNEIGARLAG SA based?

SOLAVÅG GRUNNEIGARLAG SA has its business address in Eidsnes.

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.