biztrac. BETA
COMPANY REGISTER PROFILE
929465512 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

BORSHAVN BIG FISH COMPANY AS

Org. no. 929465512 Limited company (AS) Farsund Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −19,000
Equity NOK −331,000
Incorporated 2022
Share capital NOK 500,000

Signals

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

BORSHAVN BIG FISH COMPANY AS is registered as a limited company in Farsund, Agder with organisation number 929465512. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 500,000, divided into 1000000 shares. The company's stated purpose is: “Investering i diverse hav-relaterte objekt, investeringer i andre selskap, drift, tjenester og utleie, konsulentbistand og annet som vil være naturlig i denne sammenheng.”.

Key figures · 2025

Operating profit
NOK −19,000
▲ +90 %
Equity
NOK −331,000
▼ −36 %

Financial health · 2025

Liquidity
0.14
Not satisfactory
Current assets ÷ current liabilities
Profitability
-1.2%
Not satisfactory
Return on total assets
Solidity
-19.9%
Weak
Equity as a share of total capital

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

Who owns BORSHAVN BIG FISH COMPANY AS?

BORSHAVN BIG FISH COMPANY AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about BORSHAVN BIG FISH COMPANY AS

Who owns BORSHAVN BIG FISH COMPANY AS?

GUBO AS is the largest registered owner, with 20.0%.

Who is the general manager of BORSHAVN BIG FISH COMPANY AS?

Arnt Gaute Ubostad is registered as general manager of BORSHAVN BIG FISH COMPANY AS.

Where is BORSHAVN BIG FISH COMPANY AS based?

BORSHAVN BIG FISH COMPANY AS has its business address in Borhaug.

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.