BIZTRAC BETA
Rental and operating of own or leased real estate

RAVEIEN 269 SANDEFJORD AS

Org. no. 912108716 Limited company (AS) Ringerike Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 5.2m
Operating profit NOK 3.9m
Equity NOK 48.0m
Incorporated 2013
Share capital NOK 150,000

Signals

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

RAVEIEN 269 SANDEFJORD AS is registered as a limited company in Ringerike, Buskerud with organisation number 912108716. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2013. Registered share capital is NOK 150,000, divided into 30000 shares. The company's stated purpose is: “Eie, utvikle og drifte fast eiendom, samt eie aksjer og andeler i andre selskap.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.2m in revenue and NOK 3.9m in operating profit.

Key figures · 2024

Revenue
NOK 5.2m
Operating profit
NOK 3.9m
Equity
NOK 48.0m
Est. value
NOK 43.0m

Financial health · 2024

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

Who owns RAVEIEN 269 SANDEFJORD AS?

HANDELSEIENDOMMER ØST AS
RAVEIEN 269 SANDEFJORD AS
NOK 5.2m rev. · NOK 3.9m profit

RAVEIEN 269 SANDEFJORD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RAVEIEN 269 SANDEFJORD AS

Who owns RAVEIEN 269 SANDEFJORD AS?

HANDELSEIENDOMMER ØST AS is the largest registered owner, with 100.0%.

What is the revenue of RAVEIEN 269 SANDEFJORD AS?

RAVEIEN 269 SANDEFJORD AS had revenue of NOK 5.2m in 2024.

Where is RAVEIEN 269 SANDEFJORD AS based?

RAVEIEN 269 SANDEFJORD AS has its business address in Hønefoss.

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.