BIZTRAC BETA
Holiday and other short-stay accommodation

SULA RORBUER AS

Org. no. 992135336 Limited company (AS) Frøya Incorporated 2007 Active
Ownership graph ↗
Revenue 2025 NOK 8.3m
Operating profit NOK 795,000
Equity NOK 1.2m
Incorporated 2007
Employees 6
Share capital NOK 500,000

SULA RORBUER AS is registered as a limited company in Frøya, Trøndelag with organisation number 992135336. The business is classified under holiday and other short-stay accommodation (NACE 55.200). The company was incorporated in 2007 and has 6 registered employees. Registered share capital is NOK 500,000, divided into 1000 shares. The company's stated purpose is: “Utleie av leiligheter, hotellrom og båter, drift av campingplass samt serveringsvirksomhet og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 8.3m in revenue and NOK 795,000 in operating profit.

Key figures · 2025

Revenue
NOK 8.3m
Operating profit
NOK 795,000
Equity
NOK 1.2m
Est. value
NOK 3.6m

Financial health · 2025

Liquidity
1.06
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
29.7%
Good
Equity as a share of total capital

Who owns SULA RORBUER AS?

SULA EIENDOM AS
SULA RORBUER AS
NOK 8.3m rev. · NOK 795,000 profit

SULA RORBUER AS has 1 registered shareholder:

All shareholders and roles →

Group structure

SULA RORBUER AS er morselskap for 3 datterselskaper:

Frequently asked questions about SULA RORBUER AS

Who owns SULA RORBUER AS?

SULA EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of SULA RORBUER AS?

SULA RORBUER AS had revenue of NOK 8.3m in 2025.

Who is the general manager of SULA RORBUER AS?

Elisabeth Sagfjæra is registered as general manager of SULA RORBUER AS.

Where is SULA RORBUER AS based?

SULA RORBUER AS has its business address in Sula.

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.