BIZTRAC BETA
COMPANY REGISTER PROFILE
958056931 ORG. NO. 2024 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Activities of housing cooperatives

ADAMSTUEN BORETTSLAG

Org. no. 958056931 Housing cooperative (BRL) Oslo Incorporated 1990 Active
Ownership graph ↗
Revenue 2024 NOK 796,000
Operating profit NOK 22,000
Equity NOK 1.6m
Incorporated 1990

ADAMSTUEN BORETTSLAG is registered as a housing cooperative in Oslo, Oslo with organisation number 958056931. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 1990. The company's stated purpose is: “Borettslag.”. The most recent filed accounts, for the 2024 financial year, show NOK 796,000 in revenue and NOK 22,000 in operating profit.

Key figures · 2024

Revenue
NOK 796,000
Operating profit
NOK 22,000
Equity
NOK 1.6m
Est. value
NOK 883,000

Financial health · 2024

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

Who owns ADAMSTUEN BORETTSLAG?

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

Frequently asked questions about ADAMSTUEN BORETTSLAG

What is the revenue of ADAMSTUEN BORETTSLAG?

ADAMSTUEN BORETTSLAG had revenue of NOK 796,000 in 2024.

Where is ADAMSTUEN BORETTSLAG based?

ADAMSTUEN BORETTSLAG has its business address in Oslo.

Property

Business address v/Hallgren & Hallgren AS Brugata 11, 0186 Oslo
Cadastral unit 301-208/77/0/0

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