BIZTRAC BETA
Materials recovery

GJENVINNING SØR-VEST AS

Org. no. 980197492 Limited company (AS) Lyngdal Incorporated 1998 Active
Ownership graph ↗
Revenue 2024 NOK 14.7m
Operating profit NOK 397,000
Equity NOK 6.7m
Incorporated 1998
Employees 6
Share capital NOK 2.5m

GJENVINNING SØR-VEST AS is registered as a limited company in Lyngdal, Agder with organisation number 980197492. The business is classified under materials recovery (NACE 38.210). The company was incorporated in 1998 and has 6 registered employees. Registered share capital is NOK 2.5m, divided into 2500 shares. The company's stated purpose is: “Mottak, behandling, mellomlagring og videreformidling av avfall for gjenvinning, aktuelle tjenester i den forbindelse, handel med slik varer m.v.”. The most recent filed accounts, for the 2024 financial year, show NOK 14.7m in revenue and NOK 397,000 in operating profit.

Key figures · 2024

Revenue
NOK 14.7m
Operating profit
NOK 397,000
Equity
NOK 6.7m
Est. value
NOK 5.2m

Financial health · 2024

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

Who owns GJENVINNING SØR-VEST AS?

AGDER VEITRANSPORT AS
GJENVINNING SØR-VEST AS
NOK 14.7m rev. · NOK 397,000 profit

GJENVINNING SØR-VEST AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about GJENVINNING SØR-VEST AS

Who owns GJENVINNING SØR-VEST AS?

AGDER VEITRANSPORT AS is the largest registered owner, with 25.0%.

What is the revenue of GJENVINNING SØR-VEST AS?

GJENVINNING SØR-VEST AS had revenue of NOK 14.7m in 2024.

Who is the general manager of GJENVINNING SØR-VEST AS?

Tor Ove Sagstad is registered as general manager of GJENVINNING SØR-VEST AS.

Where is GJENVINNING SØR-VEST AS based?

GJENVINNING SØR-VEST AS has its business address in Lyngdal.

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.