BIZTRAC BETA
Warehousing and storage

BÅTSERVICE TROMSØ AS

Org. no. 928754596 Limited company (AS) Tromsø Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 1.2m
Operating profit NOK 8,000
Equity NOK −181,000
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−181k kr).

BÅTSERVICE TROMSØ AS is registered as a limited company in Tromsø, Troms with organisation number 928754596. The business is classified under warehousing and storage (NACE 52.100). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 10 shares. The company's stated purpose is: “Oppsetting og lagring av båter. Maritimt verksted. Salg av drivstoff og rekvisita.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK 8,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.2m
Operating profit
NOK 8,000
Equity
NOK −181,000
Est. value
NOK 55,000

Financial health · 2025

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

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

Who owns BÅTSERVICE TROMSØ AS?

JONAS FENES
BÅTSERVICE TROMSØ AS
NOK 1.2m rev. · NOK 8,000 profit

BÅTSERVICE TROMSØ AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BÅTSERVICE TROMSØ AS

Who owns BÅTSERVICE TROMSØ AS?

JONAS FENES is the largest registered owner, with 90.0%.

What is the revenue of BÅTSERVICE TROMSØ AS?

BÅTSERVICE TROMSØ AS had revenue of NOK 1.2m in 2025.

Who is the general manager of BÅTSERVICE TROMSØ AS?

Jonas Fenes is registered as general manager of BÅTSERVICE TROMSØ AS.

Where is BÅTSERVICE TROMSØ AS based?

BÅTSERVICE TROMSØ AS has its business address in Tromsdalen.

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.