BIZTRAC BETA
Rental and operating of own or leased real estate

RÆKØYA EIENDOM AS

Org. no. 931731173 Limited company (AS) Vågan Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 4.4m
Operating profit NOK 2.1m
Equity NOK 6.0m
Incorporated 2023
Share capital NOK 200,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

RÆKØYA EIENDOM AS is registered as a limited company in Vågan, Nordland with organisation number 931731173. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 200,000, divided into 100 shares. The company's stated purpose is: “Drive kjøp, salg og drift av fast eiendom, samt investere i aksjer i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.4m in revenue and NOK 2.1m in operating profit.

Key figures · 2025

Revenue
NOK 4.4m
Operating profit
NOK 2.1m
Equity
NOK 6.0m
Est. value
NOK 6.9m

Financial health · 2025

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

Who owns RÆKØYA EIENDOM AS?

SORIA HOLDING AS
RÆKØYA EIENDOM AS
NOK 4.4m rev. · NOK 2.1m profit

RÆKØYA EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does RÆKØYA EIENDOM AS own?

RÆKØYA EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about RÆKØYA EIENDOM AS

Who owns RÆKØYA EIENDOM AS?

SORIA HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of RÆKØYA EIENDOM AS?

RÆKØYA EIENDOM AS had revenue of NOK 4.4m in 2025.

Where is RÆKØYA EIENDOM AS based?

RÆKØYA EIENDOM AS has its business address in Svolvær.

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.