BIZTRAC BETA
Rental and operating of own or leased real estate

EVO EIENDOM AS

Org. no. 919098546 Limited company (AS) Trondheim Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 1.9m
Operating profit NOK 717,000
Equity NOK 463,000
Incorporated 2017
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.

EVO EIENDOM AS is registered as a limited company in Trondheim, Trøndelag with organisation number 919098546. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg og utleie av eiendom, samt annen virksomhet som har tilknytning til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.9m in revenue and NOK 717,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.9m
Operating profit
NOK 717,000
Equity
NOK 463,000
Est. value
NOK 2.1m

Financial health · 2024

Liquidity
1.13
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
24.0%
Good
Equity as a share of total capital

Who owns EVO EIENDOM AS?

BORTEN MOE HOLDING AS
EVO EIENDOM AS
NOK 1.9m rev. · NOK 717,000 profit

EVO EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EVO EIENDOM AS

Who owns EVO EIENDOM AS?

BORTEN MOE HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of EVO EIENDOM AS?

EVO EIENDOM AS had revenue of NOK 1.9m in 2024.

Who is the general manager of EVO EIENDOM AS?

Ingvar Borten Moe is registered as general manager of EVO EIENDOM AS.

Where is EVO EIENDOM AS based?

EVO EIENDOM AS has its business address in Heimdal.

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.