BIZTRAC BETA
Development of building projects

ØVRE HOLMEGATE 11 HOLDING AS

Org. no. 935757703 Limited company (AS) Stavanger Incorporated 2025 Active
Ownership graph ↗
Operating profit NOK −69,000
Equity NOK 1.8m
Incorporated 2025
Share capital NOK 30,000

Signals

3 flags
  • Driftsunderskudd Siste driftsresultat er negativt (−69k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Mangler regnskap Ingen årsregnskap er registrert for selskapet.

ØVRE HOLMEGATE 11 HOLDING AS is registered as a limited company in Stavanger, Rogaland with organisation number 935757703. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Utvikling av næringseiendom og det som står i forbindelse med dette, herunder investeringer i andre selskap.”.

Key figures

Operating profit
NOK −69,000
Equity
NOK 1.8m
Est. value
NOK 1.6m

Financial health · 2025

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

Who owns ØVRE HOLMEGATE 11 HOLDING AS?

AUGA EIENDOM AS
ØVRE HOLMEGATE 11 HOLDING AS
· NOK −69,000 profit

ØVRE HOLMEGATE 11 HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ØVRE HOLMEGATE 11 HOLDING AS own?

ØVRE HOLMEGATE 11 HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ØVRE HOLMEGATE 11 HOLDING AS

Who owns ØVRE HOLMEGATE 11 HOLDING AS?

AUGA EIENDOM AS is the largest registered owner, with 100.0%.

Where is ØVRE HOLMEGATE 11 HOLDING AS based?

ØVRE HOLMEGATE 11 HOLDING AS has its business address in Stavanger.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.