BIZTRAC BETA
Camping grounds and recreational vehicle parks

OFFERSØY CAMPING AS

Org. no. 986668438 Limited company (AS) Alstahaug Incorporated 2004 Active
Ownership graph ↗
Revenue 2025 NOK 126,000
Operating profit NOK −175,000
Equity NOK 4.2m
Incorporated 2004
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−175k kr).

OFFERSØY CAMPING AS is registered as a limited company in Alstahaug, Nordland with organisation number 986668438. The business is classified under camping grounds and recreational vehicle parks (NACE 55.300). The company was incorporated in 2004. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Selskapet skal drive campingplass og hva som naturlig hører under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 126,000 in revenue and NOK −175,000 in operating profit.

Key figures · 2025

Revenue
NOK 126,000
Operating profit
NOK −175,000
Equity
NOK 4.2m
Est. value
NOK 2.2m

Financial health · 2025

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

Who owns OFFERSØY CAMPING AS?

ODD BJØRNAR OLSEN
OFFERSØY CAMPING AS
NOK 126,000 rev. · NOK −175,000 profit

OFFERSØY CAMPING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OFFERSØY CAMPING AS

Who owns OFFERSØY CAMPING AS?

ODD BJØRNAR OLSEN is the largest registered owner, with 100.0%.

What is the revenue of OFFERSØY CAMPING AS?

OFFERSØY CAMPING AS had revenue of NOK 126,000 in 2025.

Who is the general manager of OFFERSØY CAMPING AS?

Odd Bjørnar Olsen is registered as general manager of OFFERSØY CAMPING AS.

Where is OFFERSØY CAMPING AS based?

OFFERSØY CAMPING AS has its business address in Tjøtta.

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.