BIZTRAC BETA
Rental and operating of own or leased real estate

SOLUM OG ALLOUCH EIENDOM AS

Org. no. 917489998 Limited company (AS) Eidsvoll Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 323,000
Operating profit NOK 204,000
Equity NOK 280,000
Incorporated 2016
Share capital NOK 30,000

SOLUM OG ALLOUCH EIENDOM AS is registered as a limited company in Eidsvoll, Akershus with organisation number 917489998. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Drift og utleie av næringseiendommer.”. The most recent filed accounts, for the 2024 financial year, show NOK 323,000 in revenue and NOK 204,000 in operating profit.

Key figures · 2024

Revenue
NOK 323,000
Operating profit
NOK 204,000
Equity
NOK 280,000
Est. value
NOK 523,000

Financial health · 2024

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

Who owns SOLUM OG ALLOUCH EIENDOM AS?

MOHAMED YACINE ALLOUCH
SOLUM OG ALLOUCH EIENDOM AS
NOK 323,000 rev. · NOK 204,000 profit

SOLUM OG ALLOUCH EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SOLUM OG ALLOUCH EIENDOM AS

Who owns SOLUM OG ALLOUCH EIENDOM AS?

MOHAMED YACINE ALLOUCH is the largest registered owner, with 50.0%.

What is the revenue of SOLUM OG ALLOUCH EIENDOM AS?

SOLUM OG ALLOUCH EIENDOM AS had revenue of NOK 323,000 in 2024.

Who is the general manager of SOLUM OG ALLOUCH EIENDOM AS?

Knut Solum is registered as general manager of SOLUM OG ALLOUCH EIENDOM AS.

Where is SOLUM OG ALLOUCH EIENDOM AS based?

SOLUM OG ALLOUCH EIENDOM AS has its business address in Råholt.

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.