BIZTRAC BETA
Other real estate activities on a fee or contract basis

STORD NÆRINGSEIENDOM AS

Org. no. 925287008 Limited company (AS) Stord Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −77,000
Equity NOK −757,000
Incorporated 2020
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−757k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−77k kr).

STORD NÆRINGSEIENDOM AS is registered as a limited company in Stord, Vestland with organisation number 925287008. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Er å eie aksjer og andeler i andre selskaper, samt det som naturlig står i forbindelse med dette, herunder å delta i andre selskaper med lignende virksomhet.”.

Key figures · 2024

Operating profit
NOK −77,000
Equity
NOK −757,000

Financial health · 2024

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-11.3%
Weak
Equity as a share of total capital

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

Who owns STORD NÆRINGSEIENDOM AS?

JAN KÅRE PEDERSEN HOLDING AS
STORD NÆRINGSEIENDOM AS
· NOK −77,000 profit

STORD NÆRINGSEIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about STORD NÆRINGSEIENDOM AS

Who owns STORD NÆRINGSEIENDOM AS?

JAN KÅRE PEDERSEN HOLDING AS is the largest registered owner, with 50.0%.

Who is the general manager of STORD NÆRINGSEIENDOM AS?

Jan Kåre Pedersen is registered as general manager of STORD NÆRINGSEIENDOM AS.

Where is STORD NÆRINGSEIENDOM AS based?

STORD NÆRINGSEIENDOM AS has its business address in Stord.

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.