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

ØST INVEST AS

Org. no. 980674754 Limited company (AS) Sandefjord Incorporated 1998 Active
Ownership graph ↗
Operating profit NOK −14,000
Equity NOK 113,000
Incorporated 1998
Share capital NOK 300,000

Signals

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

ØST INVEST AS is registered as a limited company in Sandefjord, Vestfold with organisation number 980674754. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 1998. Registered share capital is NOK 300,000, divided into 150 shares. The company's stated purpose is: “Investeringer i andre selskaper samt handel og konsulentvirksomhet.”.

Key figures · 2025

Operating profit
NOK −14,000
▼ −1 %
Equity
NOK 113,000
▼ −10 %
Est. value
NOK 103,000

Financial health · 2025

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

Who owns ØST INVEST AS?

ØST INVEST AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about ØST INVEST AS

Who owns ØST INVEST AS?

TWIG AS is the largest registered owner, with 33.3%.

Where is ØST INVEST AS based?

ØST INVEST AS has its business address in Sandefjord.

Property

Business address Bjerggata 7, 3210 Sandefjord
Cadastral unit 3907-173/33/0/0
Building Annen forretningsbygning · 6 units

8 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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.