biztrac. BETA
COMPANY REGISTER PROFILE
989225073 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

MURI HOLDING AS

Org. no. 989225073 Limited company (AS) Lillestrøm Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 584,000
Operating profit NOK 304,000
Equity NOK 23.1m
Incorporated 2005
Share capital NOK 100,000

MURI HOLDING AS is registered as a limited company in Lillestrøm, Akershus with organisation number 989225073. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Kjøp, salg og investeringer i andre selskaper og verdipapirer, samt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 584,000 in revenue and NOK 304,000 in operating profit.

Key figures · 2025

Revenue
NOK 584,000
▲ +8 %
Operating profit
NOK 304,000
▲ +45 %
Equity
NOK 23.1m
▲ +2 %
Est. value
NOK 16.8m

Financial health · 2025

Liquidity
42.46
Very good
Current assets ÷ current liabilities
Profitability
2.0%
Weak
Return on total assets
Solidity
99.1%
Very good
Equity as a share of total capital

Who owns MURI HOLDING AS?

MURI HOLDING AS
NOK 584,000 rev. · NOK 304,000 profit

MURI HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MURI HOLDING AS own?

MURI HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MURI HOLDING AS

Who owns MURI HOLDING AS?

Sigmund Endre Muri is the largest registered owner, with 100.0%.

What is the revenue of MURI HOLDING AS?

MURI HOLDING AS had revenue of NOK 584,000 in 2025.

Where is MURI HOLDING AS based?

MURI HOLDING AS has its business address in Kjeller.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.