BIZTRAC BETA
Masonry and bricklaying activities

MURMESTER LINDGREN AS

Org. no. 975930025 Limited company (AS) Kristiansand Incorporated 1995 Active
Ownership graph ↗
Revenue 2024 NOK 46.9m
Operating profit NOK 6.8m
Equity NOK 3.3m
Incorporated 1995
Employees 32
Share capital NOK 1.4m

MURMESTER LINDGREN AS is registered as a limited company in Kristiansand, Agder with organisation number 975930025. The business is classified under masonry and bricklaying activities (NACE 43.910). The company was incorporated in 1995 and has 32 registered employees. Registered share capital is NOK 1.4m, divided into 4400 shares. The company's stated purpose is: “Entreprenørvirksomhet innen overflatebehandling, herunder murertjenester, samt relaterte tjenester.”. The most recent filed accounts, for the 2024 financial year, show NOK 46.9m in revenue and NOK 6.8m in operating profit.

Key figures · 2024

Revenue
NOK 46.9m
Operating profit
NOK 6.8m
Equity
NOK 3.3m
Est. value
NOK 19.6m

Financial health · 2024

Liquidity
1.12
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
13.9%
Satisfactory
Equity as a share of total capital

Who owns MURMESTER LINDGREN AS?

HG HÅNDVERKSGRUPPEN NORGE AS
MURMESTER LINDGREN AS
NOK 46.9m rev. · NOK 6.8m profit

MURMESTER LINDGREN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MURMESTER LINDGREN AS

Who owns MURMESTER LINDGREN AS?

HG HÅNDVERKSGRUPPEN NORGE AS is the largest registered owner, with 100.0%.

What is the revenue of MURMESTER LINDGREN AS?

MURMESTER LINDGREN AS had revenue of NOK 46.9m in 2024.

Who is the general manager of MURMESTER LINDGREN AS?

Lise Schie is registered as general manager of MURMESTER LINDGREN AS.

Where is MURMESTER LINDGREN AS based?

MURMESTER LINDGREN AS has its business address in Kristiansand S.

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.