biztrac. BETA
COMPANY REGISTER PROFILE
916454287 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Other captive investment companies

MURIEN AS

Org. no. 916454287 Limited company (AS) Bergen Incorporated 2015 Active
Revenue 2025 NOK 0
Operating profit NOK −16,000
Equity NOK −80,000
Incorporated 2015
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−80k kr).

MURIEN AS is registered as a limited company in Bergen, Vestland with organisation number 916454287. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Kjøpe og selge aksjer.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −16,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −16,000
▼ −30 %
Equity
NOK −80,000
▼ −24 %

Financial health · 2025

Liquidity
0.01
Not satisfactory
Current assets ÷ current liabilities
Profitability
-4.1%
Not satisfactory
Return on total assets
Solidity
-21.2%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns MURIEN AS?

MURIEN AS
NOK 0 rev. · NOK −16,000 profit

MURIEN AS has 2 registered shareholders:

All shareholders and roles →

Which companies does MURIEN AS own?

MURIEN AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about MURIEN AS

Who owns MURIEN AS?

Susann Helen Tarberg Muri is the largest registered owner, with 50.0%.

What is the revenue of MURIEN AS?

MURIEN AS had revenue of NOK 0 in 2025.

Who is the general manager of MURIEN AS?

Øystein Muri is registered as general manager of MURIEN AS.

Where is MURIEN AS based?

MURIEN AS has its business address in Morvik.

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.