BIZTRAC BETA
Rental and operating of own or leased real estate

SANDFRAKT EIENDOM AS

Org. no. 996124975 Limited company (AS) Vindafjord Incorporated 2009 Active
Ownership graph ↗
Revenue 2024 NOK 3.4m
Operating profit NOK 2.4m
Equity NOK 8.5m
Incorporated 2009
Share capital NOK 823,000

Signals

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

SANDFRAKT EIENDOM AS is registered as a limited company in Vindafjord, Rogaland with organisation number 996124975. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2009. Registered share capital is NOK 823,000, divided into 822780 shares. The company's stated purpose is: “Selv, gjennom hel- eller deleide selskaper eller ved samarbeid med andre virksomheter, å forestå eie, drift og utvikling av fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.4m in revenue and NOK 2.4m in operating profit.

Key figures · 2024

Revenue
NOK 3.4m
Operating profit
NOK 2.4m
Equity
NOK 8.5m
Est. value
NOK 8.6m

Financial health · 2024

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

Who owns SANDFRAKT EIENDOM AS?

SANDFRAKT HOLDING AS
SANDFRAKT EIENDOM AS
NOK 3.4m rev. · NOK 2.4m profit

SANDFRAKT EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SANDFRAKT EIENDOM AS

Who owns SANDFRAKT EIENDOM AS?

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

What is the revenue of SANDFRAKT EIENDOM AS?

SANDFRAKT EIENDOM AS had revenue of NOK 3.4m in 2024.

Where is SANDFRAKT EIENDOM AS based?

SANDFRAKT EIENDOM AS has its business address in Ølensvåg.

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.