BIZTRAC BETA
Marine fishing

BÅLY KONTORFELLESSKAP AS

Org. no. 990627673 Limited company (AS) Kristiansand Incorporated 2006 Active
Ownership graph ↗
Operating profit NOK −31,000
Equity NOK −2.4m
Incorporated 2006
Share capital NOK 200,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−2,4 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−31k kr).

BÅLY KONTORFELLESSKAP AS is registered as a limited company in Kristiansand, Agder with organisation number 990627673. The business is classified under marine fishing (NACE 03.110). The company was incorporated in 2006. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Fiskerivirksomhet, handel, eiendomsutvikling, anskaffelse og drift av eiendommer, investering i aksjer, andeler og andre finans- og realobjekter, deltagelse i andre virksomheter samt alt hva som står i forbindelse med ovennevnte.”.

Key figures · 2025

Operating profit
NOK −31,000
Equity
NOK −2.4m

Financial health · 2025

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

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

Who owns BÅLY KONTORFELLESSKAP AS?

REMEFJORD AS
BÅLY KONTORFELLESSKAP AS
· NOK −31,000 profit

BÅLY KONTORFELLESSKAP AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BÅLY KONTORFELLESSKAP AS

Who owns BÅLY KONTORFELLESSKAP AS?

REMEFJORD AS is the largest registered owner, with 80.0%.

Who is the general manager of BÅLY KONTORFELLESSKAP AS?

Ole Kristoffer Torsvik is registered as general manager of BÅLY KONTORFELLESSKAP AS.

Where is BÅLY KONTORFELLESSKAP AS based?

BÅLY KONTORFELLESSKAP AS has its business address in Kristiansand S.

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.