BIZTRAC BETA
Rental and operating of own or leased real estate

FANNREM MEGARDSVEGEN 1 AS

Org. no. 923163867 Limited company (AS) Ålesund Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 1.9m
Operating profit NOK 464,000
Equity NOK 7.2m
Incorporated 2019
Share capital NOK 2.1m

Signals

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

FANNREM MEGARDSVEGEN 1 AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 923163867. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 2.1m, divided into 2109 shares. The company's stated purpose is: “Investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.9m in revenue and NOK 464,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.9m
Operating profit
NOK 464,000
Equity
NOK 7.2m
Est. value
NOK 6.4m

Financial health · 2025

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

Who owns FANNREM MEGARDSVEGEN 1 AS?

COM EIENDOM AS
FANNREM MEGARDSVEGEN 1 AS
NOK 1.9m rev. · NOK 464,000 profit

FANNREM MEGARDSVEGEN 1 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FANNREM MEGARDSVEGEN 1 AS

Who owns FANNREM MEGARDSVEGEN 1 AS?

COM EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of FANNREM MEGARDSVEGEN 1 AS?

FANNREM MEGARDSVEGEN 1 AS had revenue of NOK 1.9m in 2025.

Where is FANNREM MEGARDSVEGEN 1 AS based?

FANNREM MEGARDSVEGEN 1 AS has its business address in Ålesund.

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.