BIZTRAC BETA
COMPANY REGISTER PROFILE
834081652 ORG. NO. 2024 ACCOUNTS 8 SECTIONS
Active UPDATED 15.06.2026
Business and other management consultancy activities

VIDDA SOLUTIONS AS

Org. no. 834081652 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 1.5m
Operating profit NOK 342,000
Equity NOK 204,000
Incorporated 2024
Share capital NOK 30,000

VIDDA SOLUTIONS AS is registered as a limited company in Oslo, Oslo with organisation number 834081652. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Drive konsulenttjenester innen bank og finans og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.5m in revenue and NOK 342,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.5m
Operating profit
NOK 342,000
Equity
NOK 204,000
Est. value
NOK 1.4m

Financial health · 2024

Liquidity
1.40
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
28.7%
Good
Equity as a share of total capital

Who owns VIDDA SOLUTIONS AS?

VIDDA GROUP AS
VIDDA SOLUTIONS AS
NOK 1.5m rev. · NOK 342,000 profit

VIDDA SOLUTIONS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VIDDA SOLUTIONS AS

Who owns VIDDA SOLUTIONS AS?

VIDDA GROUP AS is the largest registered owner, with 100.0%.

What is the revenue of VIDDA SOLUTIONS AS?

VIDDA SOLUTIONS AS had revenue of NOK 1.5m in 2024.

Who is the general manager of VIDDA SOLUTIONS AS?

Jonas Anton Kullgren is registered as general manager of VIDDA SOLUTIONS AS.

Where is VIDDA SOLUTIONS AS based?

VIDDA SOLUTIONS 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.