BIZTRAC BETA
COMPANY REGISTER PROFILE
936527825 ORG. NO. 7 SECTIONS
Active UPDATED 02.09.2026
Rental and operating of own or leased real estate

M. SHERIF EIENDOM AS

Org. no. 936527825 Limited company (AS) Hammerfest Incorporated 2025 Active
Ownership graph ↗
Incorporated 2025
Share capital NOK 30,000

Signals

2 flags
  • Mangler regnskap Ingen årsregnskap er registrert for selskapet.
  • Nystiftet selskap Selskapet ble stiftet 2025-10-01.

M. SHERIF EIENDOM AS is registered as a limited company in Hammerfest, Finnmark with organisation number 936527825. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investeringer innen fast eiendom og det som naturlig tilhører den virksomheten, herunder drift av eiendom og investeringer i eiendomsselskap.”.

Who owns M. SHERIF EIENDOM AS?

M. SHERIF EIENDOM AS

M. SHERIF EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about M. SHERIF EIENDOM AS

Who owns M. SHERIF EIENDOM AS?

MOHAMMED SHERIF is the largest registered owner, with 100.0%.

Who is the general manager of M. SHERIF EIENDOM AS?

Mohammed Sherif is registered as general manager of M. SHERIF EIENDOM AS.

Where is M. SHERIF EIENDOM AS based?

M. SHERIF EIENDOM AS has its business address in Hammerfest.

Property

Business address Forsølveien 23, 9601 Hammerfest
Cadastral unit 5603-22/393/0/0
Building Andre småhus med 3 boliger eller flere · 4 units

6 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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

Report a problem

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