BIZTRAC BETA
Rental and operating of own or leased real estate

STANGE EIENDOM AS

Org. no. 966116722 Limited company (AS) Trondheim Incorporated 1993 Active
Ownership graph ↗
Revenue 2024 NOK 1.1m
Operating profit NOK 848,000
Equity NOK 1.7m
Incorporated 1993
Share capital NOK 30,000

Signals

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

STANGE EIENDOM AS is registered as a limited company in Trondheim, Trøndelag with organisation number 966116722. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1993. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Handel, eie og drive forretningseiendommer, og hva hermed står i forbindelse, herunder ved aksjetegning eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.1m in revenue and NOK 848,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.1m
Operating profit
NOK 848,000
Equity
NOK 1.7m
Est. value
NOK 2.8m

Financial health · 2024

Liquidity
1.27
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
41.9%
Very good
Equity as a share of total capital

Who owns STANGE EIENDOM AS?

I K LYKKE EIENDOM AS
STANGE EIENDOM AS
NOK 1.1m rev. · NOK 848,000 profit

STANGE EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STANGE EIENDOM AS

Who owns STANGE EIENDOM AS?

I K LYKKE EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of STANGE EIENDOM AS?

STANGE EIENDOM AS had revenue of NOK 1.1m in 2024.

Where is STANGE EIENDOM AS based?

STANGE EIENDOM AS has its business address in Trondheim.

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.