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

SAUPSTAD TORG HUS D OG E BORETTSLAG

Org. no. 934220900 Housing cooperative (BRL) Trondheim Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −240
Equity NOK 597,000
Incorporated 2024

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−240 kr).

SAUPSTAD TORG HUS D OG E BORETTSLAG is registered as a housing cooperative in Trondheim, Trøndelag with organisation number 934220900. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 2024. The company's stated purpose is: “Borettslag.”.

Key figures · 2025

Operating profit
NOK −240
Equity
NOK 597,000
Est. value
NOK 330,000

Financial health · 2025

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

Who owns SAUPSTAD TORG HUS D OG E BORETTSLAG?

No shareholders are registered for SAUPSTAD TORG HUS D OG E BORETTSLAG in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about SAUPSTAD TORG HUS D OG E BORETTSLAG

Where is SAUPSTAD TORG HUS D OG E BORETTSLAG based?

SAUPSTAD TORG HUS D OG E BORETTSLAG has its business address in Trondheim.

Property

Business address c/o OBOS Eiendomsforvaltning AS Ranheimsvegen 9, 7044 Trondheim
Cadastral unit 5001-4/16/0/0
Building Annen kontorbygning · 1 unit

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