BIZTRAC BETA
Other real estate activities on a fee or contract basis

VALESTRANDS BEITESFORENING AS

Org. no. 932081768 Limited company (AS) Sveio Incorporated 1982 Active
Ownership graph ↗
Revenue 2024 NOK 55,000
Operating profit NOK 41,000
Equity NOK 330,000
Incorporated 1982
Share capital NOK 100,000

VALESTRANDS BEITESFORENING AS is registered as a limited company in Sveio, Vestland with organisation number 932081768. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 1982. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Skaffe aksjeeierne godt og forsvarlig beite for deres kreaturer i de selskapet tilhørende eien- dommer gnr 98 gnr 1 og gnr 99 og bnr 3 i Etne kommune.”. The most recent filed accounts, for the 2024 financial year, show NOK 55,000 in revenue and NOK 41,000 in operating profit.

Key figures · 2024

Revenue
NOK 55,000
Operating profit
NOK 41,000
Equity
NOK 330,000
Est. value
NOK 331,000

Financial health · 2024

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 VALESTRANDS BEITESFORENING AS?

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

Frequently asked questions about VALESTRANDS BEITESFORENING AS

What is the revenue of VALESTRANDS BEITESFORENING AS?

VALESTRANDS BEITESFORENING AS had revenue of NOK 55,000 in 2024.

Who is the general manager of VALESTRANDS BEITESFORENING AS?

Jofrid Valen is registered as general manager of VALESTRANDS BEITESFORENING AS.

Where is VALESTRANDS BEITESFORENING AS based?

VALESTRANDS BEITESFORENING AS has its business address in Valevåg.

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.