BIZTRAC BETA
Rental and operating of own or leased real estate

MINNESUND EIENDOM AS

Org. no. 820633792 Limited company (AS) Lørenskog Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 887,000
Operating profit NOK 630,000
Equity NOK 6.7m
Incorporated 2018
Share capital NOK 900,000

Signals

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

MINNESUND EIENDOM AS is registered as a limited company in Lørenskog, Akershus with organisation number 820633792. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 900,000, divided into 3000000 shares. The company's stated purpose is: “Å eie og drifte fast eiendom, og det som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 887,000 in revenue and NOK 630,000 in operating profit.

Key figures · 2025

Revenue
NOK 887,000
Operating profit
NOK 630,000
Equity
NOK 6.7m
Est. value
NOK 6.1m

Financial health · 2025

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

Who owns MINNESUND EIENDOM AS?

F.M INVEST AS
MINNESUND EIENDOM AS
NOK 887,000 rev. · NOK 630,000 profit

MINNESUND EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Group structure

MINNESUND EIENDOM AS er morselskap for 1 datterselskap:

Frequently asked questions about MINNESUND EIENDOM AS

Who owns MINNESUND EIENDOM AS?

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

What is the revenue of MINNESUND EIENDOM AS?

MINNESUND EIENDOM AS had revenue of NOK 887,000 in 2025.

Where is MINNESUND EIENDOM AS based?

MINNESUND EIENDOM AS has its business address in Rasta.

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.