BIZTRAC BETA
Rental and operating of own or leased real estate

FORUM EIENDOMSINVEST AS

Org. no. 988697869 Limited company (AS) Bærum Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 190,000
Operating profit NOK 109,000
Equity NOK 870,000
Incorporated 2005
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

FORUM EIENDOMSINVEST AS is registered as a limited company in Bærum, Akershus with organisation number 988697869. 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 100,000, divided into 1000 shares. The company's stated purpose is: “Erverv, utvikling og forvaltning av fast eiendom, samt deltakelse i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 190,000 in revenue and NOK 109,000 in operating profit.

Key figures · 2024

Revenue
NOK 190,000
Operating profit
NOK 109,000
Equity
NOK 870,000
Est. value
NOK 873,000

Financial health · 2025

Liquidity
1.87
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
58.5%
Very good
Equity as a share of total capital

Who owns FORUM EIENDOMSINVEST AS?

AGORA AS
FORUM EIENDOMSINVEST AS
NOK 190,000 rev. · NOK 109,000 profit

FORUM EIENDOMSINVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FORUM EIENDOMSINVEST AS

Who owns FORUM EIENDOMSINVEST AS?

AGORA AS is the largest registered owner, with 100.0%.

What is the revenue of FORUM EIENDOMSINVEST AS?

FORUM EIENDOMSINVEST AS had revenue of NOK 190,000 in 2024.

Where is FORUM EIENDOMSINVEST AS based?

FORUM EIENDOMSINVEST AS has its business address in Lysaker.

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.