biztrac. BETA
COMPANY REGISTER PROFILE
915461492 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Manufacture of plastic packing goods

BOCCO AS

Org. no. 915461492 Limited company (AS) Stavanger Incorporated 2015 Active
Revenue 2025 NOK 469,000
Operating profit NOK −1.7m
Equity NOK 1.9m
Incorporated 2015
Share capital NOK 1.5m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−1,7 mill kr).

BOCCO AS is registered as a limited company in Stavanger, Rogaland with organisation number 915461492. The business is classified under manufacture of plastic packing goods (NACE 22.220). The company was incorporated in 2015. Registered share capital is NOK 1.5m, divided into 1493842 shares. The company's stated purpose is: “Utvikling, investering i og kommersialisering av merkevarer, produkter og teknologi innenfor drikkevare- og konsumvaresegmentet, samt annen virksomhet som naturlig står i forbindelse med dette, herunder investering i og eierskap til andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 469,000 in revenue and NOK −1.7m in operating profit.

Former names: WIGGELYWOO AS, AQUAFIGURE AS

Key figures · 2025

Revenue
NOK 469,000
▲ +473 %
Operating profit
NOK −1.7m
▲ +39 %
Equity
NOK 1.9m
▼ −69 %
Est. value
NOK 1.1m

Financial health · 2025

Liquidity
0.09
Not satisfactory
Current assets ÷ current liabilities
Profitability
-4.2%
Not satisfactory
Return on total assets
Solidity
4.6%
Weak
Equity as a share of total capital

Who owns BOCCO AS?

BOCCO AS has 14 registered shareholders:

All shareholders and roles →

Frequently asked questions about BOCCO AS

Who owns BOCCO AS?

ØYHEIM AS is the largest registered owner, with 67.4%.

What is the revenue of BOCCO AS?

BOCCO AS had revenue of NOK 469,000 in 2025.

Where is BOCCO AS based?

BOCCO AS has its business address in Stavanger.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.