BIZTRAC BETA
Rental and operating of own or leased real estate

FORUS BYGGSENTER AS

Org. no. 997713273 Limited company (AS) Stavanger Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 4.7m
Operating profit NOK 1.5m
Equity NOK 14.7m
Incorporated 2011
Share capital NOK 365,000

FORUS BYGGSENTER AS is registered as a limited company in Stavanger, Rogaland with organisation number 997713273. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2011. Registered share capital is NOK 365,000, divided into 7294 shares. The company's stated purpose is: “Drive handel, import/eksport, agentur- og konsulentvirksomhet, kjøp, utleie og salg av fast eiendom samt alt hva hermed står i forbindelse, herunder å delta i andre selskap, også ved aksjeerverv.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.7m in revenue and NOK 1.5m in operating profit.

Key figures · 2024

Revenue
NOK 4.7m
Operating profit
NOK 1.5m
Equity
NOK 14.7m
Est. value
NOK 12.3m

Financial health · 2024

Liquidity
0.95
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
32.3%
Good
Equity as a share of total capital

Who owns FORUS BYGGSENTER AS?

HESKJE EIENDOM AS
FORUS BYGGSENTER AS
NOK 4.7m rev. · NOK 1.5m profit

FORUS BYGGSENTER AS has 20+ registered shareholders:

All shareholders and roles →

Which companies does FORUS BYGGSENTER AS own?

FORUS BYGGSENTER AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FORUS BYGGSENTER AS

Who owns FORUS BYGGSENTER AS?

HESKJE EIENDOM AS is the largest registered owner, with 34.2%.

What is the revenue of FORUS BYGGSENTER AS?

FORUS BYGGSENTER AS had revenue of NOK 4.7m in 2024.

Where is FORUS BYGGSENTER AS based?

FORUS BYGGSENTER 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.