BIZTRAC BETA
Warehousing and storage

VAGLE RETURLAGER AS

Org. no. 920272231 Limited company (AS) Sandnes Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 5.6m
Operating profit NOK 741,000
Equity NOK 135,000
Incorporated 2018
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

VAGLE RETURLAGER AS is registered as a limited company in Sandnes, Rogaland with organisation number 920272231. The business is classified under warehousing and storage (NACE 52.100). The company was incorporated in 2018. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Selskapets formål er mottak, sortering, lagring og transport av returemballasje samt hva hertil står i forbindelse, herunder deltakelse i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.6m in revenue and NOK 741,000 in operating profit.

Key figures · 2024

Revenue
NOK 5.6m
Operating profit
NOK 741,000
Equity
NOK 135,000
Est. value
NOK 2.4m

Financial health · 2024

Liquidity
1.10
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
11.2%
Satisfactory
Equity as a share of total capital

Who owns VAGLE RETURLAGER AS?

NORTEMP DISTRIBUSJON AS
VAGLE RETURLAGER AS
NOK 5.6m rev. · NOK 741,000 profit

VAGLE RETURLAGER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VAGLE RETURLAGER AS

Who owns VAGLE RETURLAGER AS?

NORTEMP DISTRIBUSJON AS is the largest registered owner, with 100.0%.

What is the revenue of VAGLE RETURLAGER AS?

VAGLE RETURLAGER AS had revenue of NOK 5.6m in 2024.

Where is VAGLE RETURLAGER AS based?

VAGLE RETURLAGER AS has its business address in Sandnes.

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.