BIZTRAC BETA
Rental and operating of own or leased real estate

ERCO EIENDOM BOLIG AS

Org. no. 913997662 Limited company (AS) Trondheim Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK 662,000
Equity NOK 605,000
Incorporated 2014
Share capital NOK 30,000

Signals

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

ERCO EIENDOM BOLIG AS is registered as a limited company in Trondheim, Trøndelag with organisation number 913997662. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Drift og utvikling av fast eiendom. Selskapet skal også kunne delta i tilsvarende virksomhet gjennom aksjetegning.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK 662,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
Operating profit
NOK 662,000
Equity
NOK 605,000
Est. value
NOK 1.8m

Financial health · 2025

Liquidity
0.16
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
16.7%
Satisfactory
Equity as a share of total capital

Who owns ERCO EIENDOM BOLIG AS?

ERCO INVEST AS
ERCO EIENDOM BOLIG AS
NOK 1.1m rev. · NOK 662,000 profit

ERCO EIENDOM BOLIG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ERCO EIENDOM BOLIG AS

Who owns ERCO EIENDOM BOLIG AS?

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

What is the revenue of ERCO EIENDOM BOLIG AS?

ERCO EIENDOM BOLIG AS had revenue of NOK 1.1m in 2025.

Where is ERCO EIENDOM BOLIG AS based?

ERCO EIENDOM BOLIG AS has its business address in Trondheim.

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.