BIZTRAC BETA
Rental and operating of own or leased real estate

ØVRE HOLMEGATE 22 AS

Org. no. 919916265 Limited company (AS) Stavanger Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 288,000
Operating profit NOK −483,000
Equity NOK 764,000
Incorporated 2017
Share capital NOK 1.1m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−483k kr).

ØVRE HOLMEGATE 22 AS is registered as a limited company in Stavanger, Rogaland with organisation number 919916265. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2017. Registered share capital is NOK 1.1m, divided into 1100 shares. The company's stated purpose is: “Eie og utleie av fast eiendom og hva som naturlig medfølger dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 288,000 in revenue and NOK −483,000 in operating profit.

Key figures · 2025

Revenue
NOK 288,000
Operating profit
NOK −483,000
Equity
NOK 764,000
Est. value
NOK 697,000

Financial health · 2025

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

Who owns ØVRE HOLMEGATE 22 AS?

BÆREBJELKEN AS
ØVRE HOLMEGATE 22 AS
NOK 288,000 rev. · NOK −483,000 profit

ØVRE HOLMEGATE 22 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ØVRE HOLMEGATE 22 AS

Who owns ØVRE HOLMEGATE 22 AS?

BÆREBJELKEN AS is the largest registered owner, with 100.0%.

What is the revenue of ØVRE HOLMEGATE 22 AS?

ØVRE HOLMEGATE 22 AS had revenue of NOK 288,000 in 2025.

Who is the general manager of ØVRE HOLMEGATE 22 AS?

Stein Øivind Ekeland is registered as general manager of ØVRE HOLMEGATE 22 AS.

Where is ØVRE HOLMEGATE 22 AS based?

ØVRE HOLMEGATE 22 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.