BIZTRAC BETA
Business and other management consultancy activities

ELDING AS

Org. no. 915555160 Limited company (AS) Trondheim Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 104,000
Operating profit NOK 67,000
Equity NOK 147,000
Incorporated 2015
Share capital NOK 30,000

ELDING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 915555160. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 10000 shares. The company's stated purpose is: “Tjenesteytelser som rådgivning og tilrettelegging for investering i aksjer, fondsandeler og andre verdipapirer samt det som naturlig står i forbindelse med dette, for eierselskapet Idjar AS med datterselskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 104,000 in revenue and NOK 67,000 in operating profit.

Key figures · 2024

Revenue
NOK 104,000
Operating profit
NOK 67,000
Equity
NOK 147,000
Est. value
NOK 314,000

Financial health · 2024

Liquidity
6.08
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
93.0%
Very good
Equity as a share of total capital

Who owns ELDING AS?

IDJAR AS
ELDING AS
NOK 104,000 rev. · NOK 67,000 profit

ELDING AS has 1 registered shareholder:

All shareholders and roles →

Group structure

ELDING AS er morselskap for 2 datterselskaper:

Frequently asked questions about ELDING AS

Who owns ELDING AS?

IDJAR AS is the largest registered owner, with 100.0%.

What is the revenue of ELDING AS?

ELDING AS had revenue of NOK 104,000 in 2024.

Who is the general manager of ELDING AS?

Einar Magnus Aasen is registered as general manager of ELDING AS.

Where is ELDING AS based?

ELDING AS has its business address in Charlottenlund.

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.