BIZTRAC BETA
Hotels and similar accommodation

RISØYHAMN KAFE AS

Org. no. 933537374 Limited company (AS) Andøy Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 925,000
Operating profit NOK 59,000
Equity NOK 85,000
Incorporated 2024
Share capital NOK 60,000

RISØYHAMN KAFE AS is registered as a limited company in Andøy, Nordland with organisation number 933537374. The business is classified under hotels and similar accommodation (NACE 55.100). The company was incorporated in 2024. Registered share capital is NOK 60,000, divided into 60 shares. The company's stated purpose is: “Utleie av egen eiendom, drift av kafe med overnatting og annet som naturlig faller sammen med dette. Produsere ferdigretter, Kjøp og salg av fisk og fiskeprodukter.”. The most recent filed accounts, for the 2025 financial year, show NOK 925,000 in revenue and NOK 59,000 in operating profit.

Key figures · 2025

Revenue
NOK 925,000
Operating profit
NOK 59,000
Equity
NOK 85,000
Est. value
NOK 209,000

Financial health · 2025

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

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

Who owns RISØYHAMN KAFE AS?

JUTHAPORN LOEDLAM
RISØYHAMN KAFE AS
NOK 925,000 rev. · NOK 59,000 profit

RISØYHAMN KAFE AS has 2 registered shareholders:

All shareholders and roles →

Which companies does RISØYHAMN KAFE AS own?

RISØYHAMN KAFE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about RISØYHAMN KAFE AS

Who owns RISØYHAMN KAFE AS?

JUTHAPORN LOEDLAM is the largest registered owner, with 50.0%.

What is the revenue of RISØYHAMN KAFE AS?

RISØYHAMN KAFE AS had revenue of NOK 925,000 in 2025.

Where is RISØYHAMN KAFE AS based?

RISØYHAMN KAFE AS has its business address in Risøyhamn.

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.