BIZTRAC BETA
Rental and operating of own or leased real estate

STOKKELANDSMARKA EIENDOM AS

Org. no. 994567675 Limited company (AS) Incorporated 2009 Active
Ownership graph ↗
Revenue 2025 NOK 2.6m
Operating profit NOK 2.0m
Equity NOK 111,000
Incorporated 2009
Share capital NOK 100,000

Signals

1 flags
  • Nylig endring 2026-05-18 Adresseendring registrert 2026-05-18.

STOKKELANDSMARKA EIENDOM AS is registered as a limited company in Hå, Rogaland with organisation number 994567675. 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 100,000, divided into 100 shares. The company's stated purpose is: “Drift og utleie av fast eiendom samt hva dermed står i forbindelse, herunder deltakelse i andre foretak med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.6m in revenue and NOK 2.0m in operating profit.

Key figures · 2025

Revenue
NOK 2.6m
Operating profit
NOK 2.0m
Equity
NOK 111,000
Est. value
NOK 2.9m

Financial health · 2025

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

Who owns STOKKELANDSMARKA EIENDOM AS?

HÅ ELEMENT EIENDOM AS
STOKKELANDSMARKA EIENDOM AS
NOK 2.6m rev. · NOK 2.0m profit

STOKKELANDSMARKA EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about STOKKELANDSMARKA EIENDOM AS

Who owns STOKKELANDSMARKA EIENDOM AS?

HÅ ELEMENT EIENDOM AS is the largest registered owner, with 98.0%.

What is the revenue of STOKKELANDSMARKA EIENDOM AS?

STOKKELANDSMARKA EIENDOM AS had revenue of NOK 2.6m in 2025.

Where is STOKKELANDSMARKA EIENDOM AS based?

STOKKELANDSMARKA EIENDOM AS has its business address in Vigrestad.

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.