BIZTRAC BETA
Development of building projects

ØST IN VEST AS

Org. no. 991275819 Limited company (AS) Os Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −400
Equity NOK 3.8m
Incorporated 2007
Share capital NOK 150,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−400 kr).

ØST IN VEST AS is registered as a limited company in Os, Innlandet with organisation number 991275819. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2007. Registered share capital is NOK 150,000, divided into 150 shares. The company's stated purpose is: “Utvikling av eiendom, investering i aksjer, kjøp og salg av varer, samt naturlig tilhørende virksomhet og tjenester.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −400 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −400
Equity
NOK 3.8m
Est. value
NOK 4.9m

Financial health · 2024

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

Who owns ØST IN VEST AS?

HELGE KOKVOLL
ØST IN VEST AS
NOK 0 rev. · NOK −400 profit

ØST IN VEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ØST IN VEST AS own?

ØST IN VEST AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about ØST IN VEST AS

Who owns ØST IN VEST AS?

HELGE KOKVOLL is the largest registered owner, with 100.0%.

What is the revenue of ØST IN VEST AS?

ØST IN VEST AS had revenue of NOK 0 in 2024.

Who is the general manager of ØST IN VEST AS?

Helge Kokvoll is registered as general manager of ØST IN VEST AS.

Where is ØST IN VEST AS based?

ØST IN VEST AS has its business address in Os I Østerdalen.

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.