BIZTRAC BETA
Masonry and bricklaying activities

RINDAL MUR OG BETONG AS

Org. no. 920801226 Limited company (AS) Rindal Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 10.1m
Operating profit NOK 789,000
Equity NOK 2.4m
Incorporated 2018
Employees 5
Share capital NOK 100,000

RINDAL MUR OG BETONG AS is registered as a limited company in Rindal, Trøndelag with organisation number 920801226. The business is classified under masonry and bricklaying activities (NACE 43.910). The company was incorporated in 2018 and has 5 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Mur- og betongarbeid, og andre produkter/tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 10.1m in revenue and NOK 789,000 in operating profit.

Key figures · 2024

Revenue
NOK 10.1m
Operating profit
NOK 789,000
Equity
NOK 2.4m
Est. value
NOK 4.0m

Financial health · 2025

Liquidity
1.45
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
55.0%
Very good
Equity as a share of total capital

Who owns RINDAL MUR OG BETONG AS?

VEGARD RAUSANDHAUG
RINDAL MUR OG BETONG AS
NOK 10.1m rev. · NOK 789,000 profit

RINDAL MUR OG BETONG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about RINDAL MUR OG BETONG AS

Who owns RINDAL MUR OG BETONG AS?

VEGARD RAUSANDHAUG is the largest registered owner, with 50.0%.

What is the revenue of RINDAL MUR OG BETONG AS?

RINDAL MUR OG BETONG AS had revenue of NOK 10.1m in 2024.

Who is the general manager of RINDAL MUR OG BETONG AS?

Truls Møkkelgård is registered as general manager of RINDAL MUR OG BETONG AS.

Where is RINDAL MUR OG BETONG AS based?

RINDAL MUR OG BETONG AS has its business address in Rindalsskogen.

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.