BIZTRAC BETA
Rental and operating of own or leased real estate

E C DAHLS EIENDOM DRIFT AS

Org. no. 979359128 Limited company (AS) Trondheim Incorporated 1997 Active
Ownership graph ↗
Revenue 2025 NOK 166.6m
Operating profit NOK 5.7m
Equity NOK 5.7m
Incorporated 1997
Share capital NOK 5.0m

E C DAHLS EIENDOM DRIFT AS is registered as a limited company in Trondheim, Trøndelag with organisation number 979359128. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1997. Registered share capital is NOK 5.0m, divided into 5000 shares. The company's stated purpose is: “Omsetning av varer og tjenester i tilknytning til eiendommer med ett eller flere leieforhold.”. The most recent filed accounts, for the 2025 financial year, show NOK 166.6m in revenue and NOK 5.7m in operating profit.

Key figures · 2025

Revenue
NOK 166.6m
Operating profit
NOK 5.7m
Equity
NOK 5.7m
Est. value
NOK 19.0m

Financial health · 2025

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

Who owns E C DAHLS EIENDOM DRIFT AS?

E C DAHLS EIENDOM AS
E C DAHLS EIENDOM DRIFT AS
NOK 166.6m rev. · NOK 5.7m profit

E C DAHLS EIENDOM DRIFT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about E C DAHLS EIENDOM DRIFT AS

Who owns E C DAHLS EIENDOM DRIFT AS?

E C DAHLS EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of E C DAHLS EIENDOM DRIFT AS?

E C DAHLS EIENDOM DRIFT AS had revenue of NOK 166.6m in 2025.

Who is the general manager of E C DAHLS EIENDOM DRIFT AS?

Nils Magne Vikan is registered as general manager of E C DAHLS EIENDOM DRIFT AS.

Where is E C DAHLS EIENDOM DRIFT AS based?

E C DAHLS EIENDOM DRIFT 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.