BIZTRAC BETA
Rental and operating of own or leased real estate

ELG EIENDOM AS

Org. no. 997480740 Limited company (AS) Trysil Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −23,000
Equity NOK 249,000
Incorporated 2011
Share capital NOK 240,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−23k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

ELG EIENDOM AS is registered as a limited company in Trysil, Innlandet with organisation number 997480740. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2011. Registered share capital is NOK 240,000, divided into 240 shares. The company's stated purpose is: “Å eie, drifte, kjøpe og selge eiendommer.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −23,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −23,000
Equity
NOK 249,000
Est. value
NOK 227,000

Financial health · 2025

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

Who owns ELG EIENDOM AS?

BAKKES HOLDING AS
ELG EIENDOM AS
NOK 0 rev. · NOK −23,000 profit

ELG EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ELG EIENDOM AS

Who owns ELG EIENDOM AS?

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

What is the revenue of ELG EIENDOM AS?

ELG EIENDOM AS had revenue of NOK 0 in 2025.

Who is the general manager of ELG EIENDOM AS?

Kent Bakke is registered as general manager of ELG EIENDOM AS.

Where is ELG EIENDOM AS based?

ELG EIENDOM AS has its business address in Trysil.

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.