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

SAMEIET OSLOVEIEN 241

Org. no. 991570918 Condominium flat owner (ESEK) Moss Incorporated 2002 Active
Ownership graph ↗
Revenue 2025 NOK 530,000
Operating profit NOK 78,000
Equity NOK 819,000
Incorporated 2002

SAMEIET OSLOVEIEN 241 is registered as a condominium flat owner in Moss, Østfold with organisation number 991570918. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 2002. The most recent filed accounts, for the 2025 financial year, show NOK 530,000 in revenue and NOK 78,000 in operating profit.

Key figures · 2025

Revenue
NOK 530,000
Operating profit
NOK 78,000
Equity
NOK 819,000
Est. value
NOK 774,000

Financial health · 2025

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

Who owns SAMEIET OSLOVEIEN 241?

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

Frequently asked questions about SAMEIET OSLOVEIEN 241

What is the revenue of SAMEIET OSLOVEIEN 241?

SAMEIET OSLOVEIEN 241 had revenue of NOK 530,000 in 2025.

Where is SAMEIET OSLOVEIEN 241 based?

SAMEIET OSLOVEIEN 241 has its business address in Moss.

Property

Business address Varnaveien 34, 1523 Moss
Cadastral unit 3103-2/2228/0/0
Building Butikkbygning · 5 units

255 companies are registered at this address.

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.