BIZTRAC BETA
Site preparation

ELJ ANLEGG AS

Org. no. 919028440 Limited company (AS) Enebakk Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 982,000
Operating profit NOK −162,000
Equity NOK −461,000
Incorporated 2017
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−461k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−162k kr).

ELJ ANLEGG AS is registered as a limited company in Enebakk, Akershus with organisation number 919028440. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Alle typer entreprenørvirksomhet herunder bygg, utvikling, salg, utleie, forvaltning og drift av eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 982,000 in revenue and NOK −162,000 in operating profit.

Key figures · 2024

Revenue
NOK 982,000
Operating profit
NOK −162,000
Equity
NOK −461,000

Financial health · 2024

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

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

Who owns ELJ ANLEGG AS?

Leif Jørstad
ELJ ANLEGG AS
NOK 982,000 rev. · NOK −162,000 profit

ELJ ANLEGG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ELJ ANLEGG AS

Who owns ELJ ANLEGG AS?

Leif Jørstad is the largest registered owner, with 80.0%.

What is the revenue of ELJ ANLEGG AS?

ELJ ANLEGG AS had revenue of NOK 982,000 in 2024.

Who is the general manager of ELJ ANLEGG AS?

Espen Lorentz Jørstad is registered as general manager of ELJ ANLEGG AS.

Where is ELJ ANLEGG AS based?

ELJ ANLEGG AS has its business address in Enebakk.

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.