biztrac. BETA
COMPANY REGISTER PROFILE
912882675 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Other recreational activities

FANNEVATNET GRUNNEIGARLAG SA

Org. no. 912882675 Co-operation (SA) Haram Incorporated 1965 Active
Revenue 2025 NOK 17,000
Operating profit NOK 14,000
Equity NOK 275,000
Incorporated 1965

FANNEVATNET GRUNNEIGARLAG SA is registered as a co-operation in Haram, Møre og Romsdal with organisation number 912882675. The business is classified under other recreational activities (NACE 93.292). The company was incorporated in 1965. The company's stated purpose is: “Laget er ei samanslutning av grunneigarar med fiskerett i Fannevatnet og Vågsvatnet i Fannedalen i Haram. Laget skal arbeide for god forvaltning av Fannevatnet og Vågsvatnet som fiskevatn og rekreasjonsområde, legge tilhøva til rette for brukarar av vatna og ta vare på medlemmane sine interesser overfor offentlege styresmakter, organisasjonar og folk flest.”. The most recent filed accounts, for the 2025 financial year, show NOK 17,000 in revenue and NOK 14,000 in operating profit.

Key figures · 2025

Revenue
NOK 17,000
▼ −45 %
Operating profit
NOK 14,000
▼ −35 %
Equity
NOK 275,000
▲ +5 %
Est. value
NOK 180,000

Financial health · 2025

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

Who owns FANNEVATNET GRUNNEIGARLAG SA?

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

Frequently asked questions about FANNEVATNET GRUNNEIGARLAG SA

What is the revenue of FANNEVATNET GRUNNEIGARLAG SA?

FANNEVATNET GRUNNEIGARLAG SA had revenue of NOK 17,000 in 2025.

Where is FANNEVATNET GRUNNEIGARLAG SA based?

FANNEVATNET GRUNNEIGARLAG SA has its business address in Vatne.

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.