biztrac. BETA
COMPANY REGISTER PROFILE
988321877 ORG. NO. 2021 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Activities of housing cooperatives

EIERSEKSJONSSAMEIE GABELS GATE 8

Org. no. 988321877 Condominium flat owner (ESEK) Oslo Incorporated 1974 Active
Ownership graph ↗
Revenue 2021 NOK 698.4m
Operating profit NOK −152.9m
Equity NOK −331.4m
Incorporated 1974

Signals

3 flags
  • Negativ egenkapital 2021 Bokført egenkapital er negativ (−331,4 mill kr).
  • Driftsunderskudd 2021 Siste driftsresultat er negativt (−152,9 mill kr).
  • Nylig endring 2026-09-23 Adresseendring registrert 2026-09-23.

EIERSEKSJONSSAMEIE GABELS GATE 8 is registered as a condominium flat owner in Oslo, Oslo with organisation number 988321877. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 1974. The most recent filed accounts, for the 2021 financial year, show NOK 698.4m in revenue and NOK −152.9m in operating profit.

Former names: EIERSEKSJONSSAMEIE GABRIELS GATE 8

Key figures · 2021

Revenue
NOK 698.4m
Operating profit
NOK −152.9m
Equity
NOK −331.4m

Financial health · 2021

Liquidity
4.99
Very good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
-284.6%
Weak
Equity as a share of total capital

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

Who owns EIERSEKSJONSSAMEIE GABELS GATE 8?

No shareholders are registered for EIERSEKSJONSSAMEIE GABELS GATE 8 in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about EIERSEKSJONSSAMEIE GABELS GATE 8

What is the revenue of EIERSEKSJONSSAMEIE GABELS GATE 8?

EIERSEKSJONSSAMEIE GABELS GATE 8 had revenue of NOK 698.4m in 2021.

Where is EIERSEKSJONSSAMEIE GABELS GATE 8 based?

EIERSEKSJONSSAMEIE GABELS GATE 8 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.