BIZTRAC BETA
Camping grounds and recreational vehicle parks

BJØRGEBU CAMPING AS

Org. no. 929979141 Limited company (AS) Nord-Fron Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 1.6m
Operating profit NOK 114,000
Equity NOK −36,000
Incorporated 2022
Share capital NOK 1.0m

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−36k kr).

BJØRGEBU CAMPING AS is registered as a limited company in Nord-Fron, Innlandet with organisation number 929979141. 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 1.0m, divided into 400 shares. The company's stated purpose is: “Camping og hytteutleie.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.6m in revenue and NOK 114,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.6m
Operating profit
NOK 114,000
Equity
NOK −36,000
Est. value
NOK 688,000

Financial health · 2025

Liquidity
0.68
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-0.7%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns BJØRGEBU CAMPING AS?

PER ARNE SJØMÆLING
BJØRGEBU CAMPING AS
NOK 1.6m rev. · NOK 114,000 profit

BJØRGEBU CAMPING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BJØRGEBU CAMPING AS

Who owns BJØRGEBU CAMPING AS?

PER ARNE SJØMÆLING is the largest registered owner, with 100.0%.

What is the revenue of BJØRGEBU CAMPING AS?

BJØRGEBU CAMPING AS had revenue of NOK 1.6m in 2025.

Who is the general manager of BJØRGEBU CAMPING AS?

Per Arne Sjømæling is registered as general manager of BJØRGEBU CAMPING AS.

Where is BJØRGEBU CAMPING AS based?

BJØRGEBU CAMPING AS has its business address in Kvam.

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.