BIZTRAC BETA
Wholesale of beverages

VINIMA AS

Org. no. 998913543 Limited company (AS) Oslo Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 32.9m
Operating profit NOK 1.5m
Equity NOK −857,000
Incorporated 2012
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−857k kr).

VINIMA AS is registered as a limited company in Oslo, Oslo with organisation number 998913543. The business is classified under wholesale of beverages (NACE 46.340). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Handel-, investering- og eiendomsvirksomhet, samt å delta i andre selskaper med slik virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 32.9m in revenue and NOK 1.5m in operating profit.

Key figures · 2025

Revenue
NOK 32.9m
Operating profit
NOK 1.5m
Equity
NOK −857,000
Est. value
NOK 8.1m

Financial health · 2025

Liquidity
1.25
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-4.3%
Weak
Equity as a share of total capital

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

Who owns VINIMA AS?

NOVA BEVERAGE GROUP AS
VINIMA AS
NOK 32.9m rev. · NOK 1.5m profit

VINIMA AS has 4 registered shareholders:

All shareholders and roles →

Which companies does VINIMA AS own?

VINIMA AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about VINIMA AS

Who owns VINIMA AS?

NOVA BEVERAGE GROUP AS is the largest registered owner, with 40.0%.

What is the revenue of VINIMA AS?

VINIMA AS had revenue of NOK 32.9m in 2025.

Who is the general manager of VINIMA AS?

Ole Steinsholt is registered as general manager of VINIMA AS.

Where is VINIMA AS based?

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