BIZTRAC BETA
Rental and operating of own or leased real estate

FORUS KOMBINASJONSEIENDOM II AS

Org. no. 928848159 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −403,000
Equity NOK 35.3m
Incorporated 2022
Share capital NOK 2.2m

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−403k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

FORUS KOMBINASJONSEIENDOM II AS is registered as a limited company in Oslo, Oslo with organisation number 928848159. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 2.2m, divided into 450000 shares. The company's stated purpose is: “Å kjøpe, eie og selge fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”.

Key figures · 2025

Operating profit
NOK −403,000
Equity
NOK 35.3m
Est. value
NOK 30.0m

Financial health · 2025

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

Who owns FORUS KOMBINASJONSEIENDOM II AS?

ALCO HOLDING AS
FORUS KOMBINASJONSEIENDOM II AS
· NOK −403,000 profit

FORUS KOMBINASJONSEIENDOM II AS has 15 registered shareholders:

All shareholders and roles →

Which companies does FORUS KOMBINASJONSEIENDOM II AS own?

FORUS KOMBINASJONSEIENDOM II AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FORUS KOMBINASJONSEIENDOM II AS

Who owns FORUS KOMBINASJONSEIENDOM II AS?

ALCO HOLDING AS is the largest registered owner, with 25.0%.

Where is FORUS KOMBINASJONSEIENDOM II AS based?

FORUS KOMBINASJONSEIENDOM II 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 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.