BIZTRAC BETA
Rental and operating of own or leased real estate

ELDØYANE EIENDOM AS

Org. no. 811865702 Limited company (AS) Lillestrøm Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 1.5m
Operating profit NOK 688,000
Equity NOK 3.6m
Incorporated 2013
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.

ELDØYANE EIENDOM AS is registered as a limited company in Lillestrøm, Akershus with organisation number 811865702. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2013. Registered share capital is NOK 2.1m, divided into 210000 shares. The company's stated purpose is: “Utleie av eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.5m in revenue and NOK 688,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.5m
Operating profit
NOK 688,000
Equity
NOK 3.6m
Est. value
NOK 3.4m

Financial health · 2025

Liquidity
0.31
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
31.1%
Good
Equity as a share of total capital

Who owns ELDØYANE EIENDOM AS?

MERCURIUS INVEST AS
ELDØYANE EIENDOM AS
NOK 1.5m rev. · NOK 688,000 profit

ELDØYANE EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ELDØYANE EIENDOM AS

Who owns ELDØYANE EIENDOM AS?

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

What is the revenue of ELDØYANE EIENDOM AS?

ELDØYANE EIENDOM AS had revenue of NOK 1.5m in 2025.

Who is the general manager of ELDØYANE EIENDOM AS?

Ove Einar Lunde is registered as general manager of ELDØYANE EIENDOM AS.

Where is ELDØYANE EIENDOM AS based?

ELDØYANE EIENDOM AS has its business address in Lillestrøm.

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.