biztrac. BETA
COMPANY REGISTER PROFILE
984297785 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Activities of housing cooperatives

SAMEIET BRÅNÅSEN TERRASSE II

Org. no. 984297785 Condominium flat owner (ESEK) Oslo Incorporated 2001 Active
Ownership graph ↗
Revenue 2025 NOK 1.7m
Operating profit NOK 451,000
Equity NOK −212,000
Incorporated 2001

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−212k kr).

SAMEIET BRÅNÅSEN TERRASSE II is registered as a condominium flat owner in Oslo, Oslo with organisation number 984297785. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 2001. The company's stated purpose is: “Den enkelte enhet skal brukes til boligformål. Bruksenhetene kan ikke anvendes til næringsformål. Med næringsformål menes ethvert formål som ikke er boligformål.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.7m in revenue and NOK 451,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.7m
▲ +7 %
Operating profit
NOK 451,000
▲ +50 %
Equity
NOK −212,000
▲ +65 %
Est. value
NOK 1.7m

Financial health · 2025

Liquidity
22.84
Very good
Current assets ÷ current liabilities
Profitability
68.7%
Very good
Return on total assets
Solidity
-25.9%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns SAMEIET BRÅNÅSEN TERRASSE II?

No shareholders are registered for SAMEIET BRÅNÅSEN TERRASSE II in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about SAMEIET BRÅNÅSEN TERRASSE II

What is the revenue of SAMEIET BRÅNÅSEN TERRASSE II?

SAMEIET BRÅNÅSEN TERRASSE II had revenue of NOK 1.7m in 2025.

Where is SAMEIET BRÅNÅSEN TERRASSE II based?

SAMEIET BRÅNÅSEN TERRASSE II has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.