BIZTRAC BETA
Rental and operating of own or leased real estate

ESPELIEN EIENDOM AS

Org. no. 817180892 Limited company (AS) Trondheim Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 195,000
Operating profit NOK 104,000
Equity NOK −255,000
Incorporated 2016
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−255k kr).

ESPELIEN EIENDOM AS is registered as a limited company in Trondheim, Trøndelag with organisation number 817180892. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Kjøp, salg, utleie av fast eiendom og driftsmidler i tilknytning til aktivitet som foregår på eiendommen(e).”. The most recent filed accounts, for the 2024 financial year, show NOK 195,000 in revenue and NOK 104,000 in operating profit.

Key figures · 2024

Revenue
NOK 195,000
Operating profit
NOK 104,000
Equity
NOK −255,000
Est. value
NOK 710,000

Financial health · 2024

Liquidity
0.80
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-11.8%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns ESPELIEN EIENDOM AS?

INGVILD SVORKMO ESPELIEN
ESPELIEN EIENDOM AS
NOK 195,000 rev. · NOK 104,000 profit

ESPELIEN EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ESPELIEN EIENDOM AS

Who owns ESPELIEN EIENDOM AS?

INGVILD SVORKMO ESPELIEN is the largest registered owner, with 50.0%.

What is the revenue of ESPELIEN EIENDOM AS?

ESPELIEN EIENDOM AS had revenue of NOK 195,000 in 2024.

Where is ESPELIEN EIENDOM AS based?

ESPELIEN EIENDOM 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.