BIZTRAC BETA
Camping grounds and recreational vehicle parks

KRAGERØFJORDEN CAMPING AS

Org. no. 929046374 Limited company (AS) Kragerø Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 1.9m
Operating profit NOK 180,000
Equity NOK 103,000
Incorporated 2022
Share capital NOK 30,000

Signals

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

KRAGERØFJORDEN CAMPING AS is registered as a limited company in Kragerø, Telemark with organisation number 929046374. The business is classified under camping grounds and recreational vehicle parks (NACE 55.300). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Å drifte campingplasser, samt alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.9m in revenue and NOK 180,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.9m
Operating profit
NOK 180,000
Equity
NOK 103,000
Est. value
NOK 725,000

Financial health · 2024

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

Who owns KRAGERØFJORDEN CAMPING AS?

FREDENSBORG HOSPITALITY AS
KRAGERØFJORDEN CAMPING AS
NOK 1.9m rev. · NOK 180,000 profit

KRAGERØFJORDEN CAMPING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KRAGERØFJORDEN CAMPING AS

Who owns KRAGERØFJORDEN CAMPING AS?

FREDENSBORG HOSPITALITY AS is the largest registered owner, with 100.0%.

What is the revenue of KRAGERØFJORDEN CAMPING AS?

KRAGERØFJORDEN CAMPING AS had revenue of NOK 1.9m in 2024.

Where is KRAGERØFJORDEN CAMPING AS based?

KRAGERØFJORDEN CAMPING AS has its business address in Stabbestad.

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.