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

SLETTEVOLL FORSAMLINGSHUS SA

Org. no. 935021618 Co-operation (SA) Lund Incorporated 1961 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −720
Equity NOK 43,000
Incorporated 1961

Signals

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

SLETTEVOLL FORSAMLINGSHUS SA is registered as a co-operation in Lund, Rogaland with organisation number 935021618. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1961. The company's stated purpose is: “Drift og utleie av forsamlingshuset i tråd med opprinnelige vedtekter.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −720 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −720
Equity
NOK 43,000
Est. value
NOK 39,000

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
–
Not available
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 SLETTEVOLL FORSAMLINGSHUS SA?

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

Frequently asked questions about SLETTEVOLL FORSAMLINGSHUS SA

What is the revenue of SLETTEVOLL FORSAMLINGSHUS SA?

SLETTEVOLL FORSAMLINGSHUS SA had revenue of NOK 0 in 2025.

Who is the general manager of SLETTEVOLL FORSAMLINGSHUS SA?

Per Ove Røiland is registered as general manager of SLETTEVOLL FORSAMLINGSHUS SA.

Where is SLETTEVOLL FORSAMLINGSHUS SA based?

SLETTEVOLL FORSAMLINGSHUS SA has its business address in Moi.

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.