BIZTRAC BETA
Collection of hazardous waste

BATTERIRETUR EV AS

Org. no. 913997905 Limited company (AS) Fredrikstad Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 4.0m
Operating profit NOK −789,000
Equity NOK 10.6m
Incorporated 2014
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−789k kr).

BATTERIRETUR EV AS is registered as a limited company in Fredrikstad, Østfold with organisation number 913997905. The business is classified under collection of hazardous waste (NACE 38.120). The company was incorporated in 2014. Registered share capital is NOK 100,000, divided into 10000 shares. The company's stated purpose is: “Forestå landsdekkende innsamling, depot, gjenvinning og handel med brukte industribatterier og annet som naturlig hører sammen med dette, alt i samsvar med de til enhver tid gjeldende norske forskrifter om dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.0m in revenue and NOK −789,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.0m
Operating profit
NOK −789,000
Equity
NOK 10.6m
Est. value
NOK 9.1m

Financial health · 2024

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

Who owns BATTERIRETUR EV AS?

No shareholders are registered for BATTERIRETUR EV AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about BATTERIRETUR EV AS

What is the revenue of BATTERIRETUR EV AS?

BATTERIRETUR EV AS had revenue of NOK 4.0m in 2024.

Who is the general manager of BATTERIRETUR EV AS?

Tor Henrik Svendsen is registered as general manager of BATTERIRETUR EV AS.

Where is BATTERIRETUR EV AS based?

BATTERIRETUR EV AS has its business address in Gamle Fredrikstad.

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.