BIZTRAC BETA
Rental and operating of own or leased real estate

STAMNÆSS EIENDOM AS

Org. no. 912158748 Limited company (AS) Ålesund Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 2.0m
Operating profit NOK 1.0m
Equity NOK 3.6m
Incorporated 2013
Share capital NOK 1.5m

Signals

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

STAMNÆSS EIENDOM AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 912158748. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2013. Registered share capital is NOK 1.5m, divided into 30 shares. The company's stated purpose is: “Utleie og utvikling av eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.0m in revenue and NOK 1.0m in operating profit.

Key figures · 2024

Revenue
NOK 2.0m
Operating profit
NOK 1.0m
Equity
NOK 3.6m
Est. value
NOK 4.0m

Financial health · 2024

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

Who owns STAMNÆSS EIENDOM AS?

STAMNÆSS INVEST AS
STAMNÆSS EIENDOM AS
NOK 2.0m rev. · NOK 1.0m profit

STAMNÆSS EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STAMNÆSS EIENDOM AS

Who owns STAMNÆSS EIENDOM AS?

STAMNÆSS INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of STAMNÆSS EIENDOM AS?

STAMNÆSS EIENDOM AS had revenue of NOK 2.0m in 2024.

Who is the general manager of STAMNÆSS EIENDOM AS?

Roger Longva Olsen is registered as general manager of STAMNÆSS EIENDOM AS.

Where is STAMNÆSS EIENDOM AS based?

STAMNÆSS EIENDOM AS has its business address in Ålesund.

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.