BIZTRAC BETA
Rental and operating of own or leased real estate

SAND EIENDOM AS

Org. no. 971231548 Limited company (AS) Sandnes Incorporated 1994 Active
Ownership graph ↗
Revenue 2024 NOK 404,000
Operating profit NOK −151,000
Equity NOK 68.2m
Incorporated 1994
Share capital NOK 544,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−151k kr).

SAND EIENDOM AS is registered as a limited company in Sandnes, Rogaland with organisation number 971231548. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1994. Registered share capital is NOK 544,000, divided into 544000 shares. The company's stated purpose is: “Kjøpe, selge, eie og leie ut fast eiendom, og hva som dermed måtte stå i forbindelse, samt eie aksjer i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 404,000 in revenue and NOK −151,000 in operating profit.

Key figures · 2024

Revenue
NOK 404,000
Operating profit
NOK −151,000
Equity
NOK 68.2m
Est. value
NOK 46.7m

Financial health · 2024

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

Who owns SAND EIENDOM AS?

O.R.T. HOLDING AS
SAND EIENDOM AS
NOK 404,000 rev. · NOK −151,000 profit

SAND EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Which companies does SAND EIENDOM AS own?

SAND EIENDOM AS holds stakes in 10 companies:

See the full ownership structure →

Frequently asked questions about SAND EIENDOM AS

Who owns SAND EIENDOM AS?

O.R.T. HOLDING AS is the largest registered owner, with 40.0%.

What is the revenue of SAND EIENDOM AS?

SAND EIENDOM AS had revenue of NOK 404,000 in 2024.

Where is SAND EIENDOM AS based?

SAND EIENDOM AS has its business address in Sandnes.

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.