BIZTRAC BETA
Holiday and other short-stay accommodation

BUODDEN RORBUCAMPING AS

Org. no. 819259542 Limited company (AS) Moskenes Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −54,000
Equity NOK 6.6m
Incorporated 2017
Share capital NOK 30,000

Signals

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

BUODDEN RORBUCAMPING AS is registered as a limited company in Moskenes, Nordland with organisation number 819259542. The business is classified under holiday and other short-stay accommodation (NACE 55.200). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Utleie og drift av rorbuanlegg for turisme og annen korttidsutleie”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −54,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −54,000
Equity
NOK 6.6m
Est. value
NOK 5.5m

Financial health · 2025

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

Who owns BUODDEN RORBUCAMPING AS?

KNUT OLAV KRANSVIK
BUODDEN RORBUCAMPING AS
NOK 0 rev. · NOK −54,000 profit

BUODDEN RORBUCAMPING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BUODDEN RORBUCAMPING AS

Who owns BUODDEN RORBUCAMPING AS?

KNUT OLAV KRANSVIK is the largest registered owner, with 100.0%.

What is the revenue of BUODDEN RORBUCAMPING AS?

BUODDEN RORBUCAMPING AS had revenue of NOK 0 in 2025.

Who is the general manager of BUODDEN RORBUCAMPING AS?

Knut Olav Kransvik is registered as general manager of BUODDEN RORBUCAMPING AS.

Where is BUODDEN RORBUCAMPING AS based?

BUODDEN RORBUCAMPING AS has its business address in Sørvågen.

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.