BIZTRAC BETA
Rental and operating of own or leased real estate

RETS AS

Org. no. 923325468 Limited company (AS) Asker Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −13.2m
Equity NOK 2.8m
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−13,2 mill kr).

RETS AS is registered as a limited company in Asker, Akershus with organisation number 923325468. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Konsulentbistand innen markedsføring og etablering og drift av andre selskaper og andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap, kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −13.2m in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −13.2m
Equity
NOK 2.8m
Est. value
NOK 2.6m

Financial health · 2024

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

Who owns RETS AS?

ELIN TUV SANDVIK
RETS AS
NOK 0 rev. · NOK −13.2m profit

RETS AS has 6 registered shareholders:

All shareholders and roles →

Which companies does RETS AS own?

RETS AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about RETS AS

Who owns RETS AS?

ELIN TUV SANDVIK is the largest registered owner, with 35.0%.

What is the revenue of RETS AS?

RETS AS had revenue of NOK 0 in 2024.

Where is RETS AS based?

RETS AS has its business address in Billingstad.

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.