BIZTRAC BETA
Hotels and similar accommodation

RØST BRYGGEHOTELL AS

Org. no. 981482859 Limited company (AS) Røst Incorporated 2000 Active
Ownership graph ↗
Revenue 2025 NOK 6.3m
Operating profit NOK −244,000
Equity NOK 1.3m
Incorporated 2000
Employees 15
Share capital NOK 1.3m

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−244k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

RØST BRYGGEHOTELL AS is registered as a limited company in Røst, Nordland with organisation number 981482859. The business is classified under hotels and similar accommodation (NACE 55.100). The company was incorporated in 2000 and has 15 registered employees. Registered share capital is NOK 1.3m, divided into 6177 shares. The company's stated purpose is: “Hotell og restaurantvirksomhet, samt hva som herved står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.3m in revenue and NOK −244,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.3m
Operating profit
NOK −244,000
Equity
NOK 1.3m
Est. value
NOK 4.6m

Financial health · 2025

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

Who owns RØST BRYGGEHOTELL AS?

JOHANSENS NÆRINGSPARK AS
RØST BRYGGEHOTELL AS
NOK 6.3m rev. · NOK −244,000 profit

RØST BRYGGEHOTELL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RØST BRYGGEHOTELL AS

Who owns RØST BRYGGEHOTELL AS?

JOHANSENS NÆRINGSPARK AS is the largest registered owner, with 100.0%.

What is the revenue of RØST BRYGGEHOTELL AS?

RØST BRYGGEHOTELL AS had revenue of NOK 6.3m in 2025.

Where is RØST BRYGGEHOTELL AS based?

RØST BRYGGEHOTELL AS has its business address in Røst.

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.