biztrac. BETA
COMPANY REGISTER PROFILE
930373338 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

STØÅ EIENDOM AS

Org. no. 930373338 Limited company (AS) Gjesdal Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −9,000
Equity NOK −3,000
Incorporated 2022
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−3k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−9k kr).

STØÅ EIENDOM AS is registered as a limited company in Gjesdal, Rogaland with organisation number 930373338. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Eie aksjer eller andeler i andre selskap, samt kjøp, salg, utvikling og forvaltning av fast eiendom, og det som naturlig hører inn under dette.”.

Former names: ALFANOR 22121 AS

Key figures · 2025

Operating profit
NOK −9,000
▼ −7 %
Equity
NOK −3,000
▼ −153 %

Financial health · 2025

Liquidity
355.47
Very good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
-1.0%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns STØÅ EIENDOM AS?

STØÅ EIENDOM AS
· NOK −9,000 profit

STØÅ EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does STØÅ EIENDOM AS own?

STØÅ EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about STØÅ EIENDOM AS

Who owns STØÅ EIENDOM AS?

Helge Nærland is the largest registered owner, with 100.0%.

Who is the general manager of STØÅ EIENDOM AS?

Helge Nærland is registered as general manager of STØÅ EIENDOM AS.

Where is STØÅ EIENDOM AS based?

STØÅ EIENDOM AS has its business address in Ålgård.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.