BIZTRAC BETA
Retail sale of pleasure boats and equipment

BÅT & FRITID AS

Org. no. 995340984 Limited company (AS) Fauske Incorporated 2010 Active
Ownership graph ↗
Revenue 2024 NOK 13.3m
Operating profit NOK −548,000
Equity NOK 2.0m
Incorporated 2010
Share capital NOK 2.3m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−548k kr).

BÅT & FRITID AS is registered as a limited company in Fauske, Nordland with organisation number 995340984. The business is classified under retail sale of pleasure boats and equipment (NACE 47.632). The company was incorporated in 2010. Registered share capital is NOK 2.3m, divided into 2316 shares. The company's stated purpose is: “Reparasjon og salg av varer og tjenester knyttet til fritidsbruk, samt andre aktiviteter som naturlig er knyttet til aktiv fritid.”. The most recent filed accounts, for the 2024 financial year, show NOK 13.3m in revenue and NOK −548,000 in operating profit.

Key figures · 2024

Revenue
NOK 13.3m
Operating profit
NOK −548,000
Equity
NOK 2.0m
Est. value
NOK 3.3m

Financial health · 2024

Liquidity
1.33
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
15.2%
Satisfactory
Equity as a share of total capital

Who owns BÅT & FRITID AS?

ACUSTUS HOLDING AS
BÅT & FRITID AS
NOK 13.3m rev. · NOK −548,000 profit

BÅT & FRITID AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BÅT & FRITID AS

Who owns BÅT & FRITID AS?

ACUSTUS HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of BÅT & FRITID AS?

BÅT & FRITID AS had revenue of NOK 13.3m in 2024.

Who is the general manager of BÅT & FRITID AS?

Kay Roger Pettersen is registered as general manager of BÅT & FRITID AS.

Where is BÅT & FRITID AS based?

BÅT & FRITID AS has its business address in Fauske.

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.