BIZTRAC BETA
Uoppgitt

MAGNE MORITSGÅRD HOLDING AS

Org. no. 925538205 Limited company (AS) Gloppen Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −15,000
Equity NOK 5.9m
Incorporated 2020
Share capital NOK 71,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−15k kr).

MAGNE MORITSGÅRD HOLDING AS is registered as a limited company in Gloppen, Vestland with organisation number 925538205. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 71,000, divided into 71100 shares. The company's stated purpose is: “Investere i andre selskaper, samt kjøp/salg og utleie av eiendom og kjøretøy.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −15,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −15,000
Equity
NOK 5.9m
Est. value
NOK 9.1m

Financial health · 2025

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

Who owns MAGNE MORITSGÅRD HOLDING AS?

MAGNE MORITSGÅRD
MAGNE MORITSGÅRD HOLDING AS
NOK 0 rev. · NOK −15,000 profit

MAGNE MORITSGÅRD HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MAGNE MORITSGÅRD HOLDING AS own?

MAGNE MORITSGÅRD HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MAGNE MORITSGÅRD HOLDING AS

Who owns MAGNE MORITSGÅRD HOLDING AS?

MAGNE MORITSGÅRD is the largest registered owner, with 100.0%.

What is the revenue of MAGNE MORITSGÅRD HOLDING AS?

MAGNE MORITSGÅRD HOLDING AS had revenue of NOK 0 in 2025.

Where is MAGNE MORITSGÅRD HOLDING AS based?

MAGNE MORITSGÅRD HOLDING AS has its business address in Sandane.

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.