BIZTRAC BETA
Other real estate activities on a fee or contract basis

OSLO MONUMENT EIENDOM AS

Org. no. 933688356 Limited company (AS) Ås Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 2.1m
Operating profit NOK 469,000
Equity NOK 8.4m
Incorporated 2024
Share capital NOK 49,000

OSLO MONUMENT EIENDOM AS is registered as a limited company in Ås, Akershus with organisation number 933688356. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2024. Registered share capital is NOK 49,000, divided into 600 shares. The company's stated purpose is: “Å eie og forvalte fast eiendom samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.1m in revenue and NOK 469,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.1m
Operating profit
NOK 469,000
Equity
NOK 8.4m
Est. value
NOK 6.8m

Financial health · 2024

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

Who owns OSLO MONUMENT EIENDOM AS?

INGER ANN ORNELL GUSTAVSON
OSLO MONUMENT EIENDOM AS
NOK 2.1m rev. · NOK 469,000 profit

OSLO MONUMENT EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about OSLO MONUMENT EIENDOM AS

Who owns OSLO MONUMENT EIENDOM AS?

INGER ANN ORNELL GUSTAVSON is the largest registered owner, with 99.0%.

What is the revenue of OSLO MONUMENT EIENDOM AS?

OSLO MONUMENT EIENDOM AS had revenue of NOK 2.1m in 2024.

Who is the general manager of OSLO MONUMENT EIENDOM AS?

Inger Ann Ornell Gustavson is registered as general manager of OSLO MONUMENT EIENDOM AS.

Where is OSLO MONUMENT EIENDOM AS based?

OSLO MONUMENT EIENDOM AS has its business address in Ski.

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.