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

SAMEIET BENTSEBRUGATA 21

Org. no. 979405642 Condominium flat owner (ESEK) Oslo Incorporated 1997 Active
Ownership graph ↗
Revenue 2025 NOK 1.5m
Operating profit NOK 278,000
Equity NOK 472,000
Incorporated 1997

SAMEIET BENTSEBRUGATA 21 is registered as a condominium flat owner in Oslo, Oslo with organisation number 979405642. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 1997. The most recent filed accounts, for the 2025 financial year, show NOK 1.5m in revenue and NOK 278,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.5m
Operating profit
NOK 278,000
Equity
NOK 472,000
Est. value
NOK 1.2m

Financial health · 2025

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

Who owns SAMEIET BENTSEBRUGATA 21?

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

Frequently asked questions about SAMEIET BENTSEBRUGATA 21

What is the revenue of SAMEIET BENTSEBRUGATA 21?

SAMEIET BENTSEBRUGATA 21 had revenue of NOK 1.5m in 2025.

Where is SAMEIET BENTSEBRUGATA 21 based?

SAMEIET BENTSEBRUGATA 21 has its business address in Oslo.

Property

Business address v/ Alle Tall AS Karoline Kristiansens vei 1, 0661 Oslo
Cadastral unit 301-130/2/0/0

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