BIZTRAC BETA
COMPANY REGISTER PROFILE
936665519 ORG. NO. 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

BETONG RØROS HOLDING AS

Org. no. 936665519 Limited company (AS) Røros Incorporated 2025 Active
Ownership graph ↗
Incorporated 2025
Share capital NOK 80,000

Signals

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

BETONG RØROS HOLDING AS is registered as a limited company in Røros, Trøndelag with organisation number 936665519. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 80,000, divided into 80 shares. The company's stated purpose is: “Holdingselskap for aksjonærer i datterselskap i Røros som skal produsere ferdigbetong gjennom eget eierskap eller leieavtaler med andre selskaper samt deltagelse eller investeringer i andre foretak.”.

Who owns BETONG RØROS HOLDING AS?

BETONG RØROS HOLDING AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about BETONG RØROS HOLDING AS

Who owns BETONG RØROS HOLDING AS?

OLE JØRGEN KJELLMARK is the largest registered owner, with 43.8%.

Who is the general manager of BETONG RØROS HOLDING AS?

Ole Jørgen Kjellmark is registered as general manager of BETONG RØROS HOLDING AS.

Where is BETONG RØROS HOLDING AS based?

BETONG RØROS HOLDING AS has its business address in Røros.

Property

Business address Sundveien 100, 7374 Røros
Cadastral unit 5025-133/451/0/0
Building Kontor- og administrasjonsbygning, rådhus · 2 units

8 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.