BIZTRAC BETA
Buying and selling of own real estate

ELO 1 AS

Org. no. 922121451 Limited company (AS) Åsnes Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 368,000
Operating profit NOK 226,000
Equity NOK −73,000
Incorporated 2019
Share capital NOK 30,000

Signals

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

ELO 1 AS is registered as a limited company in Åsnes, Innlandet with organisation number 922121451. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Finansielle investeringer, deltagelse i andre selskaper, kjøp/salg av eiendom, utleie av eiendom og produksjon, kjøp/salg av ved. Samt annen virksomhet som naturlig faller inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 368,000 in revenue and NOK 226,000 in operating profit.

Key figures · 2025

Revenue
NOK 368,000
Operating profit
NOK 226,000
Equity
NOK −73,000
Est. value
NOK 1.0m

Financial health · 2025

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

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

Who owns ELO 1 AS?

ESPEN ISAKSÆTRE
ELO 1 AS
NOK 368,000 rev. · NOK 226,000 profit

ELO 1 AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ELO 1 AS

Who owns ELO 1 AS?

ESPEN ISAKSÆTRE is the largest registered owner, with 50.0%.

What is the revenue of ELO 1 AS?

ELO 1 AS had revenue of NOK 368,000 in 2025.

Who is the general manager of ELO 1 AS?

Lars Ove Lie Isaksætre is registered as general manager of ELO 1 AS.

Where is ELO 1 AS based?

ELO 1 AS has its business address in Flisa.

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.