BIZTRAC BETA
Wholesale of beverages

PERFECT WINES AS

Org. no. 833452762 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 214,000
Operating profit NOK −355,000
Equity NOK −157,000
Incorporated 2024
Share capital NOK 200,000

Signals

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

PERFECT WINES AS is registered as a limited company in Oslo, Oslo with organisation number 833452762. The business is classified under wholesale of beverages (NACE 46.340). The company was incorporated in 2024. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Import, salg og distribusjon av vin. Rådgivning, kurs og konsulent virksomhet. Tilrettelegging av opplevelser og reiser, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 214,000 in revenue and NOK −355,000 in operating profit.

Key figures · 2024

Revenue
NOK 214,000
Operating profit
NOK −355,000
Equity
NOK −157,000

Financial health · 2024

Liquidity
8.06
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-18.1%
Weak
Equity as a share of total capital

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

Who owns PERFECT WINES AS?

BERGSTRØM AS
PERFECT WINES AS
NOK 214,000 rev. · NOK −355,000 profit

PERFECT WINES AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PERFECT WINES AS

Who owns PERFECT WINES AS?

BERGSTRØM AS is the largest registered owner, with 100.0%.

What is the revenue of PERFECT WINES AS?

PERFECT WINES AS had revenue of NOK 214,000 in 2024.

Where is PERFECT WINES AS based?

PERFECT WINES 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.