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

SAMEIE SKOGMOTOPPEN

Org. no. 989261959 Condominium flat owner (ESEK) Oslo Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 1.4m
Operating profit NOK 241,000
Equity NOK 776,000
Incorporated 2005

SAMEIE SKOGMOTOPPEN is registered as a condominium flat owner in Oslo, Oslo with organisation number 989261959. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 2005. The most recent filed accounts, for the 2025 financial year, show NOK 1.4m in revenue and NOK 241,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.4m
Operating profit
NOK 241,000
Equity
NOK 776,000
Est. value
NOK 1.3m

Financial health · 2025

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

Who owns SAMEIE SKOGMOTOPPEN?

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

Frequently asked questions about SAMEIE SKOGMOTOPPEN

What is the revenue of SAMEIE SKOGMOTOPPEN?

SAMEIE SKOGMOTOPPEN had revenue of NOK 1.4m in 2025.

Where is SAMEIE SKOGMOTOPPEN based?

SAMEIE SKOGMOTOPPEN has its business address in Oslo.

Property

Business address Dronning Eufemias gate 16, 0191 Oslo
Cadastral unit 301-234/83/0/0
Building Kontor- og administrasjonsbygning, rådhus · 3 units

891 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.