BIZTRAC BETA
COMPANY REGISTER PROFILE
995856409 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Development of building projects

SOPRANOS 2 DA

Org. no. 995856409 General partnership with shared liability (DA) Oslo Incorporated 2010 Active
Ownership graph ↗
Operating profit NOK −13,000
Equity NOK −116,000
Incorporated 2010

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−116k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−13k kr).

SOPRANOS 2 DA is registered as a general partnership with shared liability in Oslo, Oslo with organisation number 995856409. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2010. The company's stated purpose is: “Kjøp, utvikling og forvaltning av fast eiendom.”.

Key figures · 2025

Operating profit
NOK −13,000
Equity
NOK −116,000

Financial health · 2025

Liquidity
Not available
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-924.5%
Weak
Equity as a share of total capital

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

Who owns SOPRANOS 2 DA?

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

Frequently asked questions about SOPRANOS 2 DA

Where is SOPRANOS 2 DA based?

SOPRANOS 2 DA has its business address in Oslo.

Property

Business address c/o Synne Irene Gulseth Ombergveien 2C, 0283 Oslo
Cadastral unit 301-10/882/0/0
Building Enebolig · 2 units

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