biztrac. BETA
COMPANY REGISTER PROFILE
922956987 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Construction of residential and non-residential buildings

SALVATORI BYGG OG ENTREPRENØR AS

Org. no. 922956987 Limited company (AS) Lillestrøm Incorporated 2019 Active
Operating profit NOK 0
Equity NOK 170,000
Incorporated 2019
Share capital NOK 30,000

SALVATORI BYGG OG ENTREPRENØR AS is registered as a limited company in Lillestrøm, Akershus with organisation number 922956987. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Entreprenørvirksomhet, kjøp og salg, import og eksport, deltagelse i andre selskap, eiendomsbesittelse samt annen virksomhet som naturlig hører herunder.”.

Former names: OSBORNE HOLDING AS

Key figures · 2025

Operating profit
NOK 0
▲ +100 %
Equity
NOK 170,000
▲ +0 %
Est. value
NOK 174,000

Financial health · 2025

Liquidity
7.14
Very good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
88.1%
Very good
Equity as a share of total capital

Who owns SALVATORI BYGG OG ENTREPRENØR AS?

SALVATORI BYGG OG ENTREPRENØR AS
· NOK 0 profit

SALVATORI BYGG OG ENTREPRENØR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SALVATORI BYGG OG ENTREPRENØR AS

Who owns SALVATORI BYGG OG ENTREPRENØR AS?

Mutwakil Gamer Eldin Mohammed Ahmed is the largest registered owner, with 100.0%.

Who is the general manager of SALVATORI BYGG OG ENTREPRENØR AS?

Mutwakil Gamer Eldin Mohammed Ahmed is registered as general manager of SALVATORI BYGG OG ENTREPRENØR AS.

Where is SALVATORI BYGG OG ENTREPRENØR AS based?

SALVATORI BYGG OG ENTREPRENØR AS has its business address in Lillestrøm.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

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