biztrac. BETA
COMPANY REGISTER PROFILE
985725160 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Other real estate activities on a fee or contract basis

MGJ EIENDOM AS

Org. no. 985725160 Limited company (AS) Ørsta Incorporated 2003 Active
Revenue 2025 NOK 1.4m
Operating profit NOK −1.5m
Equity NOK 2.8m
Incorporated 2003
Share capital NOK 293,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−1,5 mill kr).

MGJ EIENDOM AS is registered as a limited company in Ørsta, Møre og Romsdal with organisation number 985725160. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2003. Registered share capital is NOK 293,000, divided into 375 shares. The company's stated purpose is: “Å eie og forvalte fast eiendom samt alt som står i forbindelse med dette, herunder deltakelse i selskap med lignende virksomhet og annen økonomisk virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.4m in revenue and NOK −1.5m in operating profit.

Former names: MØRE PERSONAL SERVICE AS, MØRE PERSONAL EIGEDOM AS

Key figures · 2025

Revenue
NOK 1.4m
▼ −8 %
Operating profit
NOK −1.5m
▼ −1102 %
Equity
NOK 2.8m
▼ −41 %
Est. value
NOK 2.8m

Financial health · 2025

Liquidity
0.20
Not satisfactory
Current assets ÷ current liabilities
Profitability
-14.8%
Not satisfactory
Return on total assets
Solidity
28.1%
Good
Equity as a share of total capital

Who owns MGJ EIENDOM AS?

MGJ EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about MGJ EIENDOM AS

Who owns MGJ EIENDOM AS?

Jan Arve Mork is the largest registered owner, with 33.3%.

What is the revenue of MGJ EIENDOM AS?

MGJ EIENDOM AS had revenue of NOK 1.4m in 2025.

Where is MGJ EIENDOM AS based?

MGJ EIENDOM AS has its business address in Ørsta.

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.