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

MONSTAD EIENDOM AS

Org. no. 814393542 Limited company (AS) Bergen Incorporated 1971 Active
Ownership graph ↗
Revenue 2025 NOK 276,000
Operating profit NOK 208,000
Equity NOK 2.2m
Incorporated 1971
Share capital NOK 250,000

MONSTAD EIENDOM AS is registered as a limited company in Bergen, Vestland with organisation number 814393542. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 1971. Registered share capital is NOK 250,000, divided into 2000 shares. The company's stated purpose is: “Utøve eiendomsforvaltning og for øvrig virksomhet som står i forbindelse med dette, herunder kjøp av aksjer eller andel i firma innen samme bransje.”. The most recent filed accounts, for the 2025 financial year, show NOK 276,000 in revenue and NOK 208,000 in operating profit.

Key figures · 2025

Revenue
NOK 276,000
Operating profit
NOK 208,000
Equity
NOK 2.2m
Est. value
NOK 2.1m

Financial health · 2025

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

Who owns MONSTAD EIENDOM AS?

MONA RINGSTAD MJELDE
MONSTAD EIENDOM AS
NOK 276,000 rev. · NOK 208,000 profit

MONSTAD EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MONSTAD EIENDOM AS

Who owns MONSTAD EIENDOM AS?

MONA RINGSTAD MJELDE is the largest registered owner, with 100.0%.

What is the revenue of MONSTAD EIENDOM AS?

MONSTAD EIENDOM AS had revenue of NOK 276,000 in 2025.

Who is the general manager of MONSTAD EIENDOM AS?

Oddvar Mjelde is registered as general manager of MONSTAD EIENDOM AS.

Where is MONSTAD EIENDOM AS based?

MONSTAD EIENDOM AS has its business address in Fyllingsdalen.

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.