BIZTRAC BETA
Rental and operating of own or leased real estate

VEITA INVEST AS

Org. no. 997316797 Limited company (AS) Inderøy Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 22,000
Operating profit NOK −28,000
Equity NOK 263,000
Incorporated 2011
Share capital NOK 100,000

Signals

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

VEITA INVEST AS is registered as a limited company in Inderøy, Trøndelag with organisation number 997316797. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg, drift og utvikling av fast eiendom samt konsulentvirksomhet for slik virksomhet. Eie aksjer samt kjøp og salg av aksjer. Deltakelse i andre selskap med lignende virksomhet. Virksomheten kan også gjelde investeringer i utlandet.”. The most recent filed accounts, for the 2024 financial year, show NOK 22,000 in revenue and NOK −28,000 in operating profit.

Key figures · 2024

Revenue
NOK 22,000
Operating profit
NOK −28,000
Equity
NOK 263,000
Est. value
NOK 212,000

Financial health · 2024

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

Who owns VEITA INVEST AS?

BJØRN EMIL RIKSVOLD
VEITA INVEST AS
NOK 22,000 rev. · NOK −28,000 profit

VEITA INVEST AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about VEITA INVEST AS

Who owns VEITA INVEST AS?

BJØRN EMIL RIKSVOLD is the largest registered owner, with 90.0%.

What is the revenue of VEITA INVEST AS?

VEITA INVEST AS had revenue of NOK 22,000 in 2024.

Where is VEITA INVEST AS based?

VEITA INVEST AS has its business address in Inderøy.

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.