BIZTRAC BETA
Service activities incidental to water transportation

BÅTOPPLAG SØR AS

Org. no. 929990501 Limited company (AS) Kristiansand Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 32,000
Operating profit NOK −3,000
Equity NOK 115,000
Incorporated 2022
Share capital NOK 30,000

Signals

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

BÅTOPPLAG SØR AS is registered as a limited company in Kristiansand, Agder with organisation number 929990501. The business is classified under service activities incidental to water transportation (NACE 52.220). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Båtopplag, service, vedlikehold, kjøp og salg av båter, og utstyr til båt.”. The most recent filed accounts, for the 2024 financial year, show NOK 32,000 in revenue and NOK −3,000 in operating profit.

Key figures · 2024

Revenue
NOK 32,000
Operating profit
NOK −3,000
Equity
NOK 115,000
Est. value
NOK 74,000

Financial health · 2024

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

Who owns BÅTOPPLAG SØR AS?

LUIS ALBERTO CHRISTENSEN
BÅTOPPLAG SØR AS
NOK 32,000 rev. · NOK −3,000 profit

BÅTOPPLAG SØR AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BÅTOPPLAG SØR AS own?

BÅTOPPLAG SØR AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about BÅTOPPLAG SØR AS

Who owns BÅTOPPLAG SØR AS?

LUIS ALBERTO CHRISTENSEN is the largest registered owner, with 100.0%.

What is the revenue of BÅTOPPLAG SØR AS?

BÅTOPPLAG SØR AS had revenue of NOK 32,000 in 2024.

Where is BÅTOPPLAG SØR AS based?

BÅTOPPLAG SØR 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.