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

SAMEIET BEHRENSGATE 8

Org. no. 985200718 Condominium flat owner (ESEK) Oslo Incorporated 1977 Active
Ownership graph ↗
Revenue 2025 NOK 3.1m
Operating profit NOK 2.2m
Equity NOK 277,000
Incorporated 1977

SAMEIET BEHRENSGATE 8 is registered as a condominium flat owner in Oslo, Oslo with organisation number 985200718. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 1977. The most recent filed accounts, for the 2025 financial year, show NOK 3.1m in revenue and NOK 2.2m in operating profit.

Key figures · 2025

Revenue
NOK 3.1m
Operating profit
NOK 2.2m
Equity
NOK 277,000
Est. value
NOK 6.3m

Financial health · 2025

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

Who owns SAMEIET BEHRENSGATE 8?

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

Frequently asked questions about SAMEIET BEHRENSGATE 8

What is the revenue of SAMEIET BEHRENSGATE 8?

SAMEIET BEHRENSGATE 8 had revenue of NOK 3.1m in 2025.

Where is SAMEIET BEHRENSGATE 8 based?

SAMEIET BEHRENSGATE 8 has its business address in Oslo.

Property

Business address Innspurten 11C, 0663 Oslo
Cadastral unit 301-130/245/0/0
Building Kontor- og administrasjonsbygning, rådhus · 1 unit

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