BIZTRAC BETA
Wholesale of information and communication equipment

BEST BAY HOLDING AS

Org. no. 910433679 Limited company (AS) Oslo Incorporated 1941 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −16,000
Equity NOK 3.8m
Incorporated 1941
Share capital NOK 250,000

Signals

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

BEST BAY HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 910433679. The business is classified under wholesale of information and communication equipment (NACE 46.500). The company was incorporated in 1941. Registered share capital is NOK 250,000, divided into 100 shares. The company's stated purpose is: “Agentur, handel og import/eksport, samt hva dermed står i forbindelse, herunder å delta i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −16,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −16,000
Equity
NOK 3.8m
Est. value
NOK 1.9m

Financial health · 2024

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

Who owns BEST BAY HOLDING AS?

KRISTIAN BAY
BEST BAY HOLDING AS
NOK 0 rev. · NOK −16,000 profit

BEST BAY HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BEST BAY HOLDING AS own?

BEST BAY HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about BEST BAY HOLDING AS

Who owns BEST BAY HOLDING AS?

KRISTIAN BAY is the largest registered owner, with 100.0%.

What is the revenue of BEST BAY HOLDING AS?

BEST BAY HOLDING AS had revenue of NOK 0 in 2025.

Where is BEST BAY HOLDING AS based?

BEST BAY HOLDING 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.