BIZTRAC BETA
Freight transport by road

ECOREN AS

Org. no. 822016812 Limited company (AS) Lillestrøm Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −18,000
Equity NOK −47,000
Incorporated 2018
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−47k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−18k kr).

ECOREN AS is registered as a limited company in Lillestrøm, Akershus with organisation number 822016812. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Å yte økologisk renhold tjenester til privat bolig eiere. Bygge og selge møbler på bestilling, herunder inkludert monterings-tjenester. Godstransport på vei.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −18,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −18,000
Equity
NOK −47,000

Financial health · 2025

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

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

Who owns ECOREN AS?

Tomas Repsys
ECOREN AS
NOK 0 rev. · NOK −18,000 profit

ECOREN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ECOREN AS

Who owns ECOREN AS?

Tomas Repsys is the largest registered owner, with 100.0%.

What is the revenue of ECOREN AS?

ECOREN AS had revenue of NOK 0 in 2025.

Who is the general manager of ECOREN AS?

Tomas Repsys is registered as general manager of ECOREN AS.

Where is ECOREN AS based?

ECOREN AS has its business address in Strømmen.

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.