BIZTRAC BETA
Buying and selling of own real estate

STANGHELLE EIENDOM AS

Org. no. 935993733 Limited company (AS) Vaksdal Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −12,000
Equity NOK 18,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−12k kr).

STANGHELLE EIENDOM AS is registered as a limited company in Vaksdal, Vestland with organisation number 935993733. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Kjøp, salg og drift av eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −12,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −12,000
Equity
NOK 18,000
Est. value
NOK 16,000

Financial health · 2025

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

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

Who owns STANGHELLE EIENDOM AS?

MIDTSÆTER-BOLSTAD AS
STANGHELLE EIENDOM AS
NOK 0 rev. · NOK −12,000 profit

STANGHELLE EIENDOM AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about STANGHELLE EIENDOM AS

Who owns STANGHELLE EIENDOM AS?

MIDTSÆTER-BOLSTAD AS is the largest registered owner, with 40.0%.

What is the revenue of STANGHELLE EIENDOM AS?

STANGHELLE EIENDOM AS had revenue of NOK 0 in 2025.

Who is the general manager of STANGHELLE EIENDOM AS?

Torje Midtsæter is registered as general manager of STANGHELLE EIENDOM AS.

Where is STANGHELLE EIENDOM AS based?

STANGHELLE EIENDOM AS has its business address in Stanghelle.

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.