BIZTRAC BETA
Rental and operating of own or leased real estate

MØLLESTUA EIENDOM AS

Org. no. 931331698 Limited company (AS) Lillehammer Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 611,000
Operating profit NOK 137,000
Equity NOK 139,000
Incorporated 2023
Share capital NOK 661,000

Signals

2 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-06-13 Adresseendring registrert 2026-06-13.

MØLLESTUA EIENDOM AS is registered as a limited company in Lillehammer, Innlandet with organisation number 931331698. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 661,000, divided into 661 shares. The company's stated purpose is: “Kjøp, salg og forvaltning av fast eiendom og alt som naturlig hører under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 611,000 in revenue and NOK 137,000 in operating profit.

Key figures · 2025

Revenue
NOK 611,000
Operating profit
NOK 137,000
Equity
NOK 139,000
Est. value
NOK 358,000

Financial health · 2025

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

Who owns MØLLESTUA EIENDOM AS?

NERWO AS
MØLLESTUA EIENDOM AS
NOK 611,000 rev. · NOK 137,000 profit

MØLLESTUA EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MØLLESTUA EIENDOM AS

Who owns MØLLESTUA EIENDOM AS?

NERWO AS is the largest registered owner, with 100.0%.

What is the revenue of MØLLESTUA EIENDOM AS?

MØLLESTUA EIENDOM AS had revenue of NOK 611,000 in 2025.

Where is MØLLESTUA EIENDOM AS based?

MØLLESTUA EIENDOM AS has its business address in Lillehammer.

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.