biztrac. BETA
COMPANY REGISTER PROFILE
828664662 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

VISJON INVEST AS

Org. no. 828664662 Limited company (AS) Tvedestrand Incorporated 2021 Active
Ownership graph ↗
Operating profit NOK −80,000
Equity NOK 92,000
Incorporated 2021
Share capital NOK 30,000

Signals

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

VISJON INVEST AS is registered as a limited company in Tvedestrand, Agder with organisation number 828664662. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Eie og forvalte aksjer i andre selskaper, drive forretningsmessig tjenesteyting samt 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 foretagender.”.

Key figures · 2025

Operating profit
NOK −80,000
▼ −7873 %
Equity
NOK 92,000
▲ +133 %
Est. value
NOK 592,000

Financial health · 2025

Liquidity
0.46
Not satisfactory
Current assets ÷ current liabilities
Profitability
113.2%
Very good
Return on total assets
Solidity
94.7%
Weak
Equity as a share of total capital

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

Who owns VISJON INVEST AS?

VISJON INVEST AS
· NOK −80,000 profit

VISJON INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VISJON INVEST AS own?

VISJON INVEST AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about VISJON INVEST AS

Who owns VISJON INVEST AS?

Marcus Bjerkeseth Marcussen is the largest registered owner, with 100.0%.

Where is VISJON INVEST AS based?

VISJON INVEST AS has its business address in Tvedestrand.

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

Report a problem

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