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

SEKSJONSSAMEIET DRONNINGENS GATE 10-14

Org. no. 912485609 Condominium flat owner (ESEK) Oslo Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 2.6m
Operating profit NOK −899,000
Equity NOK −864,000
Incorporated 2013

Signals

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

SEKSJONSSAMEIET DRONNINGENS GATE 10-14 is registered as a condominium flat owner in Oslo, Oslo with organisation number 912485609. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 2013. The company's stated purpose is: “Eierseksjonssameie”. The most recent filed accounts, for the 2025 financial year, show NOK 2.6m in revenue and NOK −899,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.6m
▲ +2 %
Operating profit
NOK −899,000
▼ −28 %
Equity
NOK −864,000
▼ −1994 %

Financial health · 2025

Liquidity
0.41
Not satisfactory
Current assets ÷ current liabilities
Profitability
0.0%
Not satisfactory
Return on total assets
Solidity
-345.1%
Weak
Equity as a share of total capital

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

Who owns SEKSJONSSAMEIET DRONNINGENS GATE 10-14?

No shareholders are registered for SEKSJONSSAMEIET DRONNINGENS GATE 10-14 in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about SEKSJONSSAMEIET DRONNINGENS GATE 10-14

What is the revenue of SEKSJONSSAMEIET DRONNINGENS GATE 10-14?

SEKSJONSSAMEIET DRONNINGENS GATE 10-14 had revenue of NOK 2.6m in 2025.

Where is SEKSJONSSAMEIET DRONNINGENS GATE 10-14 based?

SEKSJONSSAMEIET DRONNINGENS GATE 10-14 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.