biztrac. BETA
COMPANY REGISTER PROFILE
918316663 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Public relations and communication activities

BIG BLUE AS

Org. no. 918316663 Limited company (AS) Oslo Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 3.0m
Operating profit NOK 3.0m
Equity NOK 11.4m
Incorporated 2016
Share capital NOK 30,000

BIG BLUE AS is registered as a limited company in Oslo, Oslo with organisation number 918316663. The business is classified under public relations and communication activities (NACE 73.300). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Salg av konsulenttjenester knyttet til salg og markedsføring.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.0m in revenue and NOK 3.0m in operating profit.

Key figures · 2025

Revenue
NOK 3.0m
▲ +10 %
Operating profit
NOK 3.0m
▲ +22 %
Equity
NOK 11.4m
▲ +17 %
Est. value
NOK 16.5m

Financial health · 2025

Liquidity
0.04
Not satisfactory
Current assets ÷ current liabilities
Profitability
22.9%
Very good
Return on total assets
Solidity
82.4%
Very good
Equity as a share of total capital

Who owns BIG BLUE AS?

BIG BLUE AS
NOK 3.0m rev. · NOK 3.0m profit

BIG BLUE AS has 1 registered shareholder:

The company is not in the Tax Administration's shareholder register for 2025. The list shows the owners at the end of 2024.

All shareholders and roles →

Frequently asked questions about BIG BLUE AS

Who owns BIG BLUE AS?

BIG BLUE HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of BIG BLUE AS?

BIG BLUE AS had revenue of NOK 3.0m in 2025.

Who is the general manager of BIG BLUE AS?

Alf Bendik Bendixen is registered as general manager of BIG BLUE AS.

Where is BIG BLUE AS based?

BIG BLUE 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 03.10.2026.

Report a problem

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