BIZTRAC BETA
Industrial product and fashion design activities

GO BLUE AS

Org. no. 932069008 Limited company (AS) Asker Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 2.2m
Operating profit NOK −69,000
Equity NOK −29,000
Incorporated 2023
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−29k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−69k kr).

GO BLUE AS is registered as a limited company in Asker, Akershus with organisation number 932069008. The business is classified under industrial product and fashion design activities (NACE 74.110). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 10000 shares. The company's stated purpose is: “Produktutvikling, kjøp/salg og konsulenttjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.2m in revenue and NOK −69,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.2m
Operating profit
NOK −69,000
Equity
NOK −29,000

Financial health · 2025

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

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

Who owns GO BLUE AS?

BRAATHENS AS
GO BLUE AS
NOK 2.2m rev. · NOK −69,000 profit

GO BLUE AS has 1 registered shareholder:

All shareholders and roles →

Group structure

GO BLUE AS er morselskap for 1 datterselskap:

Frequently asked questions about GO BLUE AS

Who owns GO BLUE AS?

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

What is the revenue of GO BLUE AS?

GO BLUE AS had revenue of NOK 2.2m in 2025.

Who is the general manager of GO BLUE AS?

William Braathen is registered as general manager of GO BLUE AS.

Where is GO BLUE AS based?

GO BLUE AS has its business address in Vollen.

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.