BIZTRAC BETA
Rental and operating of own or leased real estate

MONUMENT EIENDOM AS

Org. no. 998451140 Limited company (AS) Trondheim Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 6.8m
Operating profit NOK 1.5m
Equity NOK 12.8m
Incorporated 2012
Share capital NOK 4.3m

MONUMENT EIENDOM AS is registered as a limited company in Trondheim, Trøndelag with organisation number 998451140. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2012. Registered share capital is NOK 4.3m, divided into 2897 shares. The company's stated purpose is: “Kjøp, salg og utleie av eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.8m in revenue and NOK 1.5m in operating profit.

Key figures · 2024

Revenue
NOK 6.8m
Operating profit
NOK 1.5m
Equity
NOK 12.8m
Est. value
NOK 11.6m

Financial health · 2024

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

Who owns MONUMENT EIENDOM AS?

JULIUSSEN INVEST AS
MONUMENT EIENDOM AS
NOK 6.8m rev. · NOK 1.5m profit

MONUMENT EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MONUMENT EIENDOM AS own?

MONUMENT EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MONUMENT EIENDOM AS

Who owns MONUMENT EIENDOM AS?

JULIUSSEN INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of MONUMENT EIENDOM AS?

MONUMENT EIENDOM AS had revenue of NOK 6.8m in 2024.

Who is the general manager of MONUMENT EIENDOM AS?

Marthe Jensen Juliussen is registered as general manager of MONUMENT EIENDOM AS.

Where is MONUMENT EIENDOM AS based?

MONUMENT 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.