BIZTRAC BETA
Retail sale of watches and jewellery

MORKEN EIENDOM AS

Org. no. 986960856 Limited company (AS) Trondheim Incorporated 2004 Active
Ownership graph ↗
Revenue 2024 NOK 1.8m
Operating profit NOK 463,000
Equity NOK 3.8m
Incorporated 2004
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

MORKEN EIENDOM AS is registered as a limited company in Trondheim, Trøndelag with organisation number 986960856. The business is classified under retail sale of watches and jewellery (NACE 47.770). The company was incorporated in 2004. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Investering, utvikling og drift av fast eiendom, samt deltagelse i andre virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.8m in revenue and NOK 463,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.8m
Operating profit
NOK 463,000
Equity
NOK 3.8m
Est. value
NOK 3.3m

Financial health · 2024

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

Who owns MORKEN EIENDOM AS?

MORKEN HOLDING AS
MORKEN EIENDOM AS
NOK 1.8m rev. · NOK 463,000 profit

MORKEN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MORKEN EIENDOM AS

Who owns MORKEN EIENDOM AS?

MORKEN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of MORKEN EIENDOM AS?

MORKEN EIENDOM AS had revenue of NOK 1.8m in 2024.

Who is the general manager of MORKEN EIENDOM AS?

Ragnfrid Oline Morken is registered as general manager of MORKEN EIENDOM AS.

Where is MORKEN EIENDOM AS based?

MORKEN EIENDOM AS has its business address in Trondheim.

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.