BIZTRAC BETA
Rental and operating of own or leased real estate

ELVELUNDEN AS

Org. no. 913270878 Limited company (AS) Stjørdal Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 118,000
Operating profit NOK 74,000
Equity NOK −312,000
Incorporated 2014
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−312k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

ELVELUNDEN AS is registered as a limited company in Stjørdal, Trøndelag with organisation number 913270878. 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 100 shares. The company's stated purpose is: “Drift og utvikling av eiendom samt deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 118,000 in revenue and NOK 74,000 in operating profit.

Key figures · 2024

Revenue
NOK 118,000
Operating profit
NOK 74,000
Equity
NOK −312,000
Est. value
NOK 506,000

Financial health · 2024

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

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

Who owns ELVELUNDEN AS?

LIGAARD HOLDING AS
ELVELUNDEN AS
NOK 118,000 rev. · NOK 74,000 profit

ELVELUNDEN AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about ELVELUNDEN AS

Who owns ELVELUNDEN AS?

LIGAARD HOLDING AS is the largest registered owner, with 52.0%.

What is the revenue of ELVELUNDEN AS?

ELVELUNDEN AS had revenue of NOK 118,000 in 2024.

Where is ELVELUNDEN AS based?

ELVELUNDEN AS has its business address in Stjørdal.

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.