BIZTRAC BETA
COMPANY REGISTER PROFILE
994875345 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Activities of housing cooperatives

SAMEIET STØLSTUNET

Org. no. 994875345 Condominium flat owner (ESEK) Øystre Slidre Incorporated 2009 Active
Ownership graph ↗
Revenue 2025 NOK 5.5m
Operating profit NOK 64,000
Equity NOK 306,000
Incorporated 2009

SAMEIET STØLSTUNET is registered as a condominium flat owner in Øystre Slidre, Innlandet with organisation number 994875345. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 2009. The company's stated purpose is: “Eierseksjonssameie.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.5m in revenue and NOK 64,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.5m
Operating profit
NOK 64,000
Equity
NOK 306,000
Est. value
NOK 343,000

Financial health · 2025

Liquidity
1.46
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
31.7%
Good
Equity as a share of total capital

Who owns SAMEIET STØLSTUNET?

No shareholders are registered for SAMEIET STØLSTUNET in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about SAMEIET STØLSTUNET

What is the revenue of SAMEIET STØLSTUNET?

SAMEIET STØLSTUNET had revenue of NOK 5.5m in 2025.

Where is SAMEIET STØLSTUNET based?

SAMEIET STØLSTUNET has its business address in Beitostølen.

Property

Business address Bygdinvegen 3764, 2953 Beitostølen
Cadastral unit 3453-9002/5/15/0
Building Appartement · 85 units

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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

Report a problem

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