BIZTRAC BETA
COMPANY REGISTER PROFILE
936774210 ORG. NO. 7 SECTIONS
Active UPDATED 02.09.2026
Non-specialised retail sale of predominately food, beverages or tobacco

RULLE BORTOVER AS

Org. no. 936774210 Limited company (AS) Beiarn Incorporated 2025 Active
Ownership graph ↗
Incorporated 2025
Employees 8
Share capital NOK 30,000

Signals

3 flags
  • Mangler regnskap Ingen årsregnskap er registrert for selskapet.
  • Nystiftet selskap Selskapet ble stiftet 2025-10-30.
  • Nylig endring 2026-03-19 Adresseendring registrert 2026-03-19.

RULLE BORTOVER AS is registered as a limited company in Beiarn, Nordland with organisation number 936774210. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2025 and has 8 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Butikk innen dagligvarehandel, samt hva som naturlig står i forbindelse med til dette.”.

Who owns RULLE BORTOVER AS?

RULLE BORTOVER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RULLE BORTOVER AS

Who owns RULLE BORTOVER AS?

IRAMGHAN ALLAHI MALIK is the largest registered owner, with 100.0%.

Who is the general manager of RULLE BORTOVER AS?

Iramghan Allahi Malik is registered as general manager of RULLE BORTOVER AS.

Where is RULLE BORTOVER AS based?

RULLE BORTOVER AS has its business address in Moldjord.

Property

Business address Nedre Beiarveien 912, 8110 Moldjord
Cadastral unit 1839-10/118/0/0
Building Butikkbygning · 1 unit

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.