BIZTRAC BETA
Repair and maintenance of civilian ships and boats

BØRSA BÅTLØFT AS

Org. no. 933377504 Limited company (AS) Skaun Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 582,000
Operating profit NOK −187,000
Equity NOK −476,000
Incorporated 2024
Share capital NOK 500,000

Signals

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

BØRSA BÅTLØFT AS is registered as a limited company in Skaun, Trøndelag with organisation number 933377504. The business is classified under repair and maintenance of civilian ships and boats (NACE 33.150). The company was incorporated in 2024. Registered share capital is NOK 500,000, divided into 1000 shares. The company's stated purpose is: “Selskapets virksomhet er tilbud av utvalgte tjenester innenfor det maritime markedet, herunder båtløft.”. The most recent filed accounts, for the 2025 financial year, show NOK 582,000 in revenue and NOK −187,000 in operating profit.

Key figures · 2025

Revenue
NOK 582,000
Operating profit
NOK −187,000
Equity
NOK −476,000

Financial health · 2025

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

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

Who owns BØRSA BÅTLØFT AS?

BØRSA BÅTKLUBB
BØRSA BÅTLØFT AS
NOK 582,000 rev. · NOK −187,000 profit

BØRSA BÅTLØFT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BØRSA BÅTLØFT AS

Who owns BØRSA BÅTLØFT AS?

BØRSA BÅTKLUBB is the largest registered owner, with 100.0%.

What is the revenue of BØRSA BÅTLØFT AS?

BØRSA BÅTLØFT AS had revenue of NOK 582,000 in 2025.

Where is BØRSA BÅTLØFT AS based?

BØRSA BÅTLØFT AS has its business address in Børsa.

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.