BIZTRAC BETA
Other real estate activities on a fee or contract basis

FINNESTADSVINGEN 36 AS

Org. no. 990633819 Limited company (AS) Stavanger Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 2.9m
Operating profit NOK 2.2m
Equity NOK 2.3m
Incorporated 2006
Share capital NOK 2.2m

FINNESTADSVINGEN 36 AS is registered as a limited company in Stavanger, Rogaland with organisation number 990633819. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2006. Registered share capital is NOK 2.2m, divided into 2200 shares. The company's stated purpose is: “Investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.9m in revenue and NOK 2.2m in operating profit.

Key figures · 2025

Revenue
NOK 2.9m
Operating profit
NOK 2.2m
Equity
NOK 2.3m
Est. value
NOK 5.8m

Financial health · 2024

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
15.7%
Satisfactory
Equity as a share of total capital

Who owns FINNESTADSVINGEN 36 AS?

FORUS AREAL HOLDING 2 AS
FINNESTADSVINGEN 36 AS
NOK 2.9m rev. · NOK 2.2m profit

FINNESTADSVINGEN 36 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FINNESTADSVINGEN 36 AS

Who owns FINNESTADSVINGEN 36 AS?

FORUS AREAL HOLDING 2 AS is the largest registered owner, with 100.0%.

What is the revenue of FINNESTADSVINGEN 36 AS?

FINNESTADSVINGEN 36 AS had revenue of NOK 2.9m in 2025.

Who is the general manager of FINNESTADSVINGEN 36 AS?

Kjetil Andre Haver is registered as general manager of FINNESTADSVINGEN 36 AS.

Where is FINNESTADSVINGEN 36 AS based?

FINNESTADSVINGEN 36 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.