BIZTRAC BETA
Masonry and bricklaying activities

MURPARTNER EIENDOM AS

Org. no. 912490769 Limited company (AS) Kristiansand Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 204,000
Operating profit NOK 127,000
Equity NOK 606,000
Incorporated 2013
Share capital NOK 30,000

MURPARTNER EIENDOM AS is registered as a limited company in Kristiansand, Agder with organisation number 912490769. The business is classified under masonry and bricklaying activities (NACE 43.910). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Eie, drifte og handle fast eiendom samt alt hva herved står i forbindelse. Selskapet skal også kunne delta i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 204,000 in revenue and NOK 127,000 in operating profit.

Key figures · 2025

Revenue
NOK 204,000
Operating profit
NOK 127,000
Equity
NOK 606,000
Est. value
NOK 684,000

Financial health · 2025

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

Who owns MURPARTNER EIENDOM AS?

LINDEBØ INVEST AS
MURPARTNER EIENDOM AS
NOK 204,000 rev. · NOK 127,000 profit

MURPARTNER EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MURPARTNER EIENDOM AS

Who owns MURPARTNER EIENDOM AS?

LINDEBØ INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of MURPARTNER EIENDOM AS?

MURPARTNER EIENDOM AS had revenue of NOK 204,000 in 2025.

Who is the general manager of MURPARTNER EIENDOM AS?

Gardian Hansson is registered as general manager of MURPARTNER EIENDOM AS.

Where is MURPARTNER EIENDOM AS based?

MURPARTNER EIENDOM AS has its business address in Flekkerøy.

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.