BIZTRAC BETA
Business and other management consultancy activities

VITALE SOLUTIONS AS

Org. no. 836372522 Limited company (AS) Nesodden Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 205,000
Operating profit NOK 10,000
Equity NOK 200,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Nystiftet selskap Selskapet ble stiftet 2025-10-06.

VITALE SOLUTIONS AS is registered as a limited company in Nesodden, Akershus with organisation number 836372522. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 300000 shares. The company's stated purpose is: “Tilby administrativ bedriftsrådgivning og konsulenttjenester, inkludert, men ikke begrenset til, forretningsplanlegging, strategi, organisasjonsutvikling, personalledelse og effektivisering av arbeidsprosesser.”. The most recent filed accounts, for the 2025 financial year, show NOK 205,000 in revenue and NOK 10,000 in operating profit.

Key figures · 2025

Revenue
NOK 205,000
Operating profit
NOK 10,000
Equity
NOK 200,000
Est. value
NOK 155,000

Financial health · 2025

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

Who owns VITALE SOLUTIONS AS?

VITALE PRODUKTER AS
VITALE SOLUTIONS AS
NOK 205,000 rev. · NOK 10,000 profit

VITALE SOLUTIONS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VITALE SOLUTIONS AS

Who owns VITALE SOLUTIONS AS?

VITALE PRODUKTER AS is the largest registered owner, with 100.0%.

What is the revenue of VITALE SOLUTIONS AS?

VITALE SOLUTIONS AS had revenue of NOK 205,000 in 2025.

Where is VITALE SOLUTIONS AS based?

VITALE SOLUTIONS AS has its business address in Fagerstrand.

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.