BIZTRAC BETA
Uoppgitt

INVEGSTAR AS

Org. no. 922947015 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK 0
Equity NOK 24,000
Incorporated 2019
Share capital NOK 30,000

INVEGSTAR AS is registered as a limited company in Oslo, Oslo with organisation number 922947015. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 24,000
Est. value
NOK 29,000

Financial health · 2024

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns INVEGSTAR AS?

VEGAR PAULSEN
INVEGSTAR AS
NOK 0 rev. · NOK 0 profit

INVEGSTAR AS has 1 registered shareholder:

All shareholders and roles →

Which companies does INVEGSTAR AS own?

INVEGSTAR AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about INVEGSTAR AS

Who owns INVEGSTAR AS?

VEGAR PAULSEN is the largest registered owner, with 100.0%.

What is the revenue of INVEGSTAR AS?

INVEGSTAR AS had revenue of NOK 0 in 2024.

Who is the general manager of INVEGSTAR AS?

Vegar Paulsen is registered as general manager of INVEGSTAR AS.

Where is INVEGSTAR AS based?

INVEGSTAR AS has its business address in Oslo.

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.