BIZTRAC BETA
COMPANY REGISTER PROFILE
989169173 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Other captive investment companies

TORINVEST AS

Org. no. 989169173 Limited company (AS) Gloppen Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −9,000
Equity NOK 3.2m
Incorporated 2005
Share capital NOK 99,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−9k kr).

TORINVEST AS is registered as a limited company in Gloppen, Vestland with organisation number 989169173. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2005. Registered share capital is NOK 99,000, divided into 16520 shares. The company's stated purpose is: “Investering i aksjer og obligasjoner samt deltagelse i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −9,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −9,000
▼ −8 %
Equity
NOK 3.2m
▲ +9 %
Est. value
NOK 2.8m

Financial health · 2025

Liquidity
12.61
Very good
Current assets ÷ current liabilities
Profitability
13.8%
Good
Return on total assets
Solidity
98.7%
Very good
Equity as a share of total capital

Who owns TORINVEST AS?

TORINVEST AS has 5 registered shareholders:

All shareholders and roles →

Which companies does TORINVEST AS own?

TORINVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TORINVEST AS

Who owns TORINVEST AS?

TOR ØYVIND AA is the largest registered owner, with 30.0%.

What is the revenue of TORINVEST AS?

TORINVEST AS had revenue of NOK 0 in 2025.

Who is the general manager of TORINVEST AS?

Tor Øyvind Aa is registered as general manager of TORINVEST AS.

Where is TORINVEST AS based?

TORINVEST AS has its business address in Hyen.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.