biztrac. BETA
COMPANY REGISTER PROFILE
898435652 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

VICASA AS

Org. no. 898435652 Limited company (AS) Sunnfjord Incorporated 2012 Active
Ownership graph ↗
Operating profit NOK −3,000
Equity NOK −90,000
Incorporated 2012
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−90k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−3k kr).

VICASA AS is registered as a limited company in Sunnfjord, Vestland with organisation number 898435652. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Kjøp, salg, drift og utleie av eiendom i Spania og andre virksomheter som faller naturlig inn under 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 −3,000
▼ −34 %
Equity
NOK −90,000
▼ −3 %

Financial health · 2025

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

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

Who owns VICASA AS?

VITOOLS DA NO
VICASA AS
· NOK −3,000 profit

VICASA AS has 1 registered shareholder:

  • VITOOLS DA 100.0%
All shareholders and roles →

Group structure

VICASA AS er morselskap for 1 datterselskap:

Frequently asked questions about VICASA AS

Who owns VICASA AS?

VITOOLS DA is the largest registered owner, with 100.0%.

Where is VICASA AS based?

VICASA AS has its business address in Sande I Sunnfjord.

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.