biztrac. BETA
COMPANY REGISTER PROFILE
989133365 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

GAMLE FORUSVEI 17-21 AS

Org. no. 989133365 Limited company (AS) Oslo Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 32.9m
Operating profit NOK 26.3m
Equity NOK 75.6m
Incorporated 2005
Share capital NOK 769,000

GAMLE FORUSVEI 17-21 AS is registered as a limited company in Oslo, Oslo with organisation number 989133365. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 769,000, divided into 769080 shares. The company's stated purpose is: “Eie, drifte og foredle Gamle Forusvei 17-21 i Stavanger kommune og alt som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 32.9m in revenue and NOK 26.3m in operating profit.

Former names: EINAR VON HIRSCH EIENDOM AS

Key figures · 2025

Revenue
NOK 32.9m
▼ −4 %
Operating profit
NOK 26.3m
▼ −9 %
Equity
NOK 75.6m
▲ +17 %
Est. value
NOK 105.0m

Financial health · 2025

Liquidity
0.39
Not satisfactory
Current assets ÷ current liabilities
Profitability
16.0%
Very good
Return on total assets
Solidity
41.3%
Very good
Equity as a share of total capital

Who owns GAMLE FORUSVEI 17-21 AS?

GAMLE FORUSVEI 17-21 AS
NOK 32.9m rev. · NOK 26.3m profit

GAMLE FORUSVEI 17-21 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GAMLE FORUSVEI 17-21 AS

Who owns GAMLE FORUSVEI 17-21 AS?

GAMLE FORUSVEI INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of GAMLE FORUSVEI 17-21 AS?

GAMLE FORUSVEI 17-21 AS had revenue of NOK 32.9m in 2025.

Where is GAMLE FORUSVEI 17-21 AS based?

GAMLE FORUSVEI 17-21 AS 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.