BIZTRAC BETA
COMPANY REGISTER PROFILE
935850983 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Business and other management consultancy activities

VIMIX AS

Org. no. 935850983 Limited company (AS) Oslo Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 446,000
Operating profit NOK 130,000
Equity NOK 126,000
Incorporated 2025
Share capital NOK 30,000

VIMIX AS is registered as a limited company in Oslo, Oslo with organisation number 935850983. 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 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen bedriftsrådgivning - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 446,000 in revenue and NOK 130,000 in operating profit.

Key figures · 2025

Revenue
NOK 446,000
Operating profit
NOK 130,000
Equity
NOK 126,000
Est. value
NOK 501,000

Financial health · 2025

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

Who owns VIMIX AS?

MARTIN SMEDSRUD KRISTENSEN
VIMIX AS
NOK 446,000 rev. · NOK 130,000 profit

VIMIX AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VIMIX AS

Who owns VIMIX AS?

MARTIN SMEDSRUD KRISTENSEN is the largest registered owner, with 100.0%.

What is the revenue of VIMIX AS?

VIMIX AS had revenue of NOK 446,000 in 2025.

Who is the general manager of VIMIX AS?

Martin Smedsrud Kristensen is registered as general manager of VIMIX AS.

Where is VIMIX AS based?

VIMIX 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.