BIZTRAC BETA
Rental and operating of own or leased real estate

QUATRO INVEST AS

Org. no. 984857233 Limited company (AS) Vestby Incorporated 2002 Active
Ownership graph ↗
Revenue 2025 NOK 11.7m
Operating profit NOK 5.3m
Equity NOK 4.0m
Incorporated 2002
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.

QUATRO INVEST AS is registered as a limited company in Vestby, Akershus with organisation number 984857233. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2002. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Investerings- og handelsvirksomhet, kjøp og salg av eiendom, utleie av fast eiendom, samt aksjeerverv, eller på annen måte gjøre seg interessert i andre foretagender av samme eller lignende art.”. The most recent filed accounts, for the 2025 financial year, show NOK 11.7m in revenue and NOK 5.3m in operating profit.

Key figures · 2025

Revenue
NOK 11.7m
Operating profit
NOK 5.3m
Equity
NOK 4.0m
Est. value
NOK 16.5m

Financial health · 2025

Liquidity
0.36
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
3.0%
Not satisfactory
Equity as a share of total capital

Who owns QUATRO INVEST AS?

WESSEL EIENDOM AS
QUATRO INVEST AS
NOK 11.7m rev. · NOK 5.3m profit

QUATRO INVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about QUATRO INVEST AS

Who owns QUATRO INVEST AS?

WESSEL EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of QUATRO INVEST AS?

QUATRO INVEST AS had revenue of NOK 11.7m in 2025.

Where is QUATRO INVEST AS based?

QUATRO INVEST AS has its business address in Vestby.

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.