BIZTRAC BETA
Construction of residential and non-residential buildings

RAM ENTREPRENØR AS

Org. no. 913787285 Limited company (AS) Ålesund Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 76.3m
Operating profit NOK 4.2m
Equity NOK 1.5m
Incorporated 2014
Employees 9
Share capital NOK 300,000

RAM ENTREPRENØR AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 913787285. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2014 and has 9 registered employees. Registered share capital is NOK 300,000, divided into 30 shares. The company's stated purpose is: “Entreprenørvirksomhet, prosjektutvikling og beslektet virksomhet. Herunder også deltagelse i andre selskap med lignende formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 76.3m in revenue and NOK 4.2m in operating profit.

Key figures · 2024

Revenue
NOK 76.3m
Operating profit
NOK 4.2m
Equity
NOK 1.5m
Est. value
NOK 14.6m

Financial health · 2024

Liquidity
1.09
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
7.2%
Weak
Equity as a share of total capital

Who owns RAM ENTREPRENØR AS?

BRRAD HOLDING AS
RAM ENTREPRENØR AS
NOK 76.3m rev. · NOK 4.2m profit

RAM ENTREPRENØR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RAM ENTREPRENØR AS

Who owns RAM ENTREPRENØR AS?

BRRAD HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of RAM ENTREPRENØR AS?

RAM ENTREPRENØR AS had revenue of NOK 76.3m in 2024.

Who is the general manager of RAM ENTREPRENØR AS?

Ramsy Bahjat Suleiman is registered as general manager of RAM ENTREPRENØR AS.

Where is RAM ENTREPRENØR AS based?

RAM ENTREPRENØR AS has its business address in Ålesund.

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.