BIZTRAC BETA
Wholesale of other food

BLUEBERRY GROUP AS

Org. no. 987372222 Limited company (AS) Oslo Incorporated 2004 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −10,000
Equity NOK 196,000
Incorporated 2004
Share capital NOK 350,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−10k kr).

BLUEBERRY GROUP AS is registered as a limited company in Oslo, Oslo with organisation number 987372222. The business is classified under wholesale of other food (NACE 46.380). The company was incorporated in 2004. Registered share capital is NOK 350,000, divided into 3500 shares. The company's stated purpose is: “Engrossalg av forbrukerartikler og øvrige produkter gjennom import, produksjon, samt tjenester som naturlig hører til virksomheten. Konsulentvirksomhet og administrative salgs tjenester for andre selskaper, investering i andre selskaper og hva dermed står i forbindelse. Eiendomsforvaltning og utvikling av eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −10,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −10,000
Equity
NOK 196,000
Est. value
NOK 246,000

Financial health · 2025

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

Who owns BLUEBERRY GROUP AS?

TOFRE AS
BLUEBERRY GROUP AS
NOK 0 rev. · NOK −10,000 profit

BLUEBERRY GROUP AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BLUEBERRY GROUP AS

Who owns BLUEBERRY GROUP AS?

TOFRE AS is the largest registered owner, with 100.0%.

What is the revenue of BLUEBERRY GROUP AS?

BLUEBERRY GROUP AS had revenue of NOK 0 in 2025.

Where is BLUEBERRY GROUP AS based?

BLUEBERRY GROUP 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.