BIZTRAC BETA
Masonry and bricklaying activities

TRE, MUR OG BETONG AS

Org. no. 998734991 Limited company (AS) Lindesnes Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 4.5m
Operating profit NOK 196,000
Equity NOK 3.4m
Incorporated 2012
Employees 5
Share capital NOK 30,000

TRE, MUR OG BETONG AS is registered as a limited company in Lindesnes, Agder with organisation number 998734991. The business is classified under masonry and bricklaying activities (NACE 43.910). The company was incorporated in 2012 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Mur og betongarbeid, snekkertjenester og annet som naturlig kan knyttes til dette. Investeringer i fast eiendom og deltaker i andre selskap og foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.5m in revenue and NOK 196,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.5m
Operating profit
NOK 196,000
Equity
NOK 3.4m
Est. value
NOK 2.3m

Financial health · 2024

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

Who owns TRE, MUR OG BETONG AS?

HARALD RØYLAND
TRE, MUR OG BETONG AS
NOK 4.5m rev. · NOK 196,000 profit

TRE, MUR OG BETONG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TRE, MUR OG BETONG AS

Who owns TRE, MUR OG BETONG AS?

HARALD RØYLAND is the largest registered owner, with 100.0%.

What is the revenue of TRE, MUR OG BETONG AS?

TRE, MUR OG BETONG AS had revenue of NOK 4.5m in 2024.

Who is the general manager of TRE, MUR OG BETONG AS?

Harald Røyland is registered as general manager of TRE, MUR OG BETONG AS.

Where is TRE, MUR OG BETONG AS based?

TRE, MUR OG BETONG AS has its business address in Holum.

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.