BIZTRAC BETA
Wholesale of beverages

GIO VIN AS

Org. no. 821259762 Limited company (AS) Bergen Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 1.5m
Operating profit NOK 524,000
Equity NOK 1.9m
Incorporated 2018
Share capital NOK 30,000

GIO VIN AS is registered as a limited company in Bergen, Vestland with organisation number 821259762. The business is classified under wholesale of beverages (NACE 46.340). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Import og salg av alkoholholdige drikker og andre relaterte produkter, samt annen virksomhet i forbindelse med dette. Import og salg av olivenolje. Arrangere kurs innen mat- og drikkefag, foredrag, planlegge mat- og vinrelaterte turer i Italia. Vinkonsulent. Selskapet kan også investere i næringsvirksomhet og i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.5m in revenue and NOK 524,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.5m
Operating profit
NOK 524,000
Equity
NOK 1.9m
Est. value
NOK 2.9m

Financial health · 2025

Liquidity
8.04
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
87.6%
Very good
Equity as a share of total capital

Who owns GIO VIN AS?

GIOVANNI SCORRANO
GIO VIN AS
NOK 1.5m rev. · NOK 524,000 profit

GIO VIN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GIO VIN AS

Who owns GIO VIN AS?

GIOVANNI SCORRANO is the largest registered owner, with 100.0%.

What is the revenue of GIO VIN AS?

GIO VIN AS had revenue of NOK 1.5m in 2025.

Who is the general manager of GIO VIN AS?

Giovanni Scorrano is registered as general manager of GIO VIN AS.

Where is GIO VIN AS based?

GIO VIN AS has its business address in Bergen.

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.