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

SAMEIET GAUSELBAKKEN PANORAMA III

Org. no. 985477957 Condominium flat owner (ESEK) Stavanger Incorporated 2001 Active
Ownership graph ↗
Revenue 2025 NOK 1.3m
Operating profit NOK −1.1m
Equity NOK −268,000
Incorporated 2001

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−268k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−1,1 mill kr).

SAMEIET GAUSELBAKKEN PANORAMA III is registered as a condominium flat owner in Stavanger, Rogaland with organisation number 985477957. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 2001. The company's stated purpose is: “Eierseksjonssameie.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.3m in revenue and NOK −1.1m in operating profit.

Key figures · 2025

Revenue
NOK 1.3m
▲ +20 %
Operating profit
NOK −1.1m
▼ −685 %
Equity
NOK −268,000
▼ −130 %

Financial health · 2025

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

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

Who owns SAMEIET GAUSELBAKKEN PANORAMA III?

No shareholders are registered for SAMEIET GAUSELBAKKEN PANORAMA III in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about SAMEIET GAUSELBAKKEN PANORAMA III

What is the revenue of SAMEIET GAUSELBAKKEN PANORAMA III?

SAMEIET GAUSELBAKKEN PANORAMA III had revenue of NOK 1.3m in 2025.

Where is SAMEIET GAUSELBAKKEN PANORAMA III based?

SAMEIET GAUSELBAKKEN PANORAMA III has its business address in Stavanger.

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.