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

BOLIGSAMEIET STANG TERRASSE

Org. no. 975801055 Condominium flat owner (ESEK) Oslo Incorporated 1984 Active
Ownership graph ↗
Revenue 2025 NOK 10.9m
Operating profit NOK 4.5m
Equity NOK 1.2m
Incorporated 1984

BOLIGSAMEIET STANG TERRASSE is registered as a condominium flat owner in Oslo, Oslo with organisation number 975801055. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 1984. The company's stated purpose is: “1. Ivareta driften av sameiet. 2. Administrere bruk og vedlikehold av fellesanlegg og fellesareal. 3. Ivareta alle andre saker av felles interesse.”. The most recent filed accounts, for the 2025 financial year, show NOK 10.9m in revenue and NOK 4.5m in operating profit.

Former names: STANG TERASSE BOLIGSAMEIE

Key figures · 2025

Revenue
NOK 10.9m
▲ +4 %
Operating profit
NOK 4.5m
▲ +97 %
Equity
NOK 1.2m
▲ +141 %
Est. value
NOK 8.9m

Financial health · 2025

Liquidity
13.06
Very good
Current assets ÷ current liabilities
Profitability
114.5%
Very good
Return on total assets
Solidity
30.9%
Good
Equity as a share of total capital

Who owns BOLIGSAMEIET STANG TERRASSE?

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

Which companies does BOLIGSAMEIET STANG TERRASSE own?

BOLIGSAMEIET STANG TERRASSE holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BOLIGSAMEIET STANG TERRASSE

What is the revenue of BOLIGSAMEIET STANG TERRASSE?

BOLIGSAMEIET STANG TERRASSE had revenue of NOK 10.9m in 2025.

Where is BOLIGSAMEIET STANG TERRASSE based?

BOLIGSAMEIET STANG TERRASSE 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.