BIZTRAC BETA
Wholesale of beverages

VINATURA AS

Org. no. 995764296 Limited company (AS) Oslo Incorporated 2010 Active
Ownership graph ↗
Revenue 2024 NOK 1.1m
Operating profit NOK −75,000
Equity NOK −510,000
Incorporated 2010
Share capital NOK 426,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−510k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−75k kr).

VINATURA AS is registered as a limited company in Oslo, Oslo with organisation number 995764296. The business is classified under wholesale of beverages (NACE 46.340). The company was incorporated in 2010. Registered share capital is NOK 426,000, divided into 1560 shares. The company's stated purpose is: “Import og salg av vin og brennevin og andre produkter som naturlig faller sammen med 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.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.1m in revenue and NOK −75,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.1m
Operating profit
NOK −75,000
Equity
NOK −510,000

Financial health · 2024

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

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

Who owns VINATURA AS?

COOL BEVERAGE COMPANY AS
VINATURA AS
NOK 1.1m rev. · NOK −75,000 profit

VINATURA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VINATURA AS

Who owns VINATURA AS?

COOL BEVERAGE COMPANY AS is the largest registered owner, with 100.0%.

What is the revenue of VINATURA AS?

VINATURA AS had revenue of NOK 1.1m in 2024.

Where is VINATURA AS based?

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