BIZTRAC BETA
Repair and maintenance of civilian ships and boats

JARLSØ MARINA AS

Org. no. 976065034 Limited company (AS) Tønsberg Incorporated 1996 Active
Ownership graph ↗
Revenue 2025 NOK 31.8m
Operating profit NOK 692,000
Equity NOK 788,000
Incorporated 1996
Employees 12
Share capital NOK 100,000

JARLSØ MARINA AS is registered as a limited company in Tønsberg, Vestfold with organisation number 976065034. The business is classified under repair and maintenance of civilian ships and boats (NACE 33.150). The company was incorporated in 1996 and has 12 registered employees. Registered share capital is NOK 100,000. The company's stated purpose is: “Salg, service og reparasjon av båtmotorer, samt det som naturlig hører sammen med dette, herunder også alle typer kjøp og salg samt deltagelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 31.8m in revenue and NOK 692,000 in operating profit.

Key figures · 2025

Revenue
NOK 31.8m
Operating profit
NOK 692,000
Equity
NOK 788,000
Est. value
NOK 2.9m

Financial health · 2025

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

Who owns JARLSØ MARINA AS?

CHRISTO HOLDING AS
JARLSØ MARINA AS
NOK 31.8m rev. · NOK 692,000 profit

JARLSØ MARINA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JARLSØ MARINA AS

Who owns JARLSØ MARINA AS?

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

What is the revenue of JARLSØ MARINA AS?

JARLSØ MARINA AS had revenue of NOK 31.8m in 2025.

Who is the general manager of JARLSØ MARINA AS?

Christian Jensen is registered as general manager of JARLSØ MARINA AS.

Where is JARLSØ MARINA AS based?

JARLSØ MARINA AS has its business address in Tønsberg.

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.