BIZTRAC BETA
Rental and operating of own or leased real estate

INTVEST AS

Org. no. 987945583 Limited company (AS) Bærum Incorporated 2004 Active
Ownership graph ↗
Revenue 2024 NOK 10,000
Operating profit NOK −163,000
Equity NOK 34.5m
Incorporated 2004
Share capital NOK 2.9m

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−163k kr).
  • Nylig endring 2026-05-04 Adresseendring registrert 2026-05-04.

INTVEST AS is registered as a limited company in Bærum, Akershus with organisation number 987945583. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2004. Registered share capital is NOK 2.9m, divided into 29000 shares. The company's stated purpose is: “Å eie aksjer i andre selskaper, samt eventuelle eiendomsinvesteringer og/eller finansinvesteringer og hva dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 10,000 in revenue and NOK −163,000 in operating profit.

Key figures · 2024

Revenue
NOK 10,000
Operating profit
NOK −163,000
Equity
NOK 34.5m
Est. value
NOK 23.6m

Financial health · 2024

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

Who owns INTVEST AS?

TOR VEGARD VALE
INTVEST AS
NOK 10,000 rev. · NOK −163,000 profit

INTVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does INTVEST AS own?

INTVEST AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about INTVEST AS

Who owns INTVEST AS?

TOR VEGARD VALE is the largest registered owner, with 100.0%.

What is the revenue of INTVEST AS?

INTVEST AS had revenue of NOK 10,000 in 2024.

Where is INTVEST AS based?

INTVEST AS has its business address in Sandvika.

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.