BIZTRAC BETA
Wholesale of beverages

365WINES AS

Org. no. 916550154 Limited company (AS) Bærum Incorporated 2015 Active
Ownership graph ↗
Operating profit NOK −2,000
Equity NOK 15,000
Incorporated 2015
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−2k kr).

365WINES AS is registered as a limited company in Bærum, Akershus with organisation number 916550154. The business is classified under wholesale of beverages (NACE 46.340). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Import, investeringer og engroshandel med vin og brennevin og andre produkter som naturlig faller sammen med dette. I tillegg er formålet å drive kjøp og salg av aksjer og verdipapirer samt eierskap i andre selskaper og andre tjenester og 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 samt kjøp, salg og utleie av fast eiendom.”.

Key figures · 2024

Operating profit
NOK −2,000
Equity
NOK 15,000
Est. value
NOK 19,000

Financial health · 2024

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

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

Who owns 365WINES AS?

HELGE SVENDSEN
365WINES AS
· NOK −2,000 profit

365WINES AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about 365WINES AS

Who owns 365WINES AS?

HELGE SVENDSEN is the largest registered owner, with 100.0%.

Who is the general manager of 365WINES AS?

Helge Svendsen is registered as general manager of 365WINES AS.

Where is 365WINES AS based?

365WINES AS has its business address in Jar.

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.