BIZTRAC BETA
Service activities incidental to water transportation

ONSØY BÅTHAVN AS

Org. no. 968659405 Limited company (AS) Fredrikstad Incorporated 1994 Active
Ownership graph ↗
Revenue 2025 NOK 2.6m
Operating profit NOK 1.1m
Equity NOK 2.6m
Incorporated 1994
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

ONSØY BÅTHAVN AS is registered as a limited company in Fredrikstad, Østfold with organisation number 968659405. The business is classified under service activities incidental to water transportation (NACE 52.220). The company was incorporated in 1994. Registered share capital is NOK 100,000. The company's stated purpose is: “Handel og servicevirksomhet, herunder virksomhet i forbindelse med drift av båthavner med tilknyttet virksomhet samt detagelse i andre selskaper og virksomheter med tilsvarende formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.6m in revenue and NOK 1.1m in operating profit.

Key figures · 2025

Revenue
NOK 2.6m
Operating profit
NOK 1.1m
Equity
NOK 2.6m
Est. value
NOK 4.9m

Financial health · 2025

Liquidity
1.13
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
64.9%
Very good
Equity as a share of total capital

Who owns ONSØY BÅTHAVN AS?

GRESSVIK PROPERTIES AS
ONSØY BÅTHAVN AS
NOK 2.6m rev. · NOK 1.1m profit

ONSØY BÅTHAVN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ONSØY BÅTHAVN AS

Who owns ONSØY BÅTHAVN AS?

GRESSVIK PROPERTIES AS is the largest registered owner, with 100.0%.

What is the revenue of ONSØY BÅTHAVN AS?

ONSØY BÅTHAVN AS had revenue of NOK 2.6m in 2025.

Where is ONSØY BÅTHAVN AS based?

ONSØY BÅTHAVN AS has its business address in Fredrikstad.

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.