BIZTRAC BETA
Collection of non-hazardous waste

SGT EIGENDOM AS

Org. no. 915515762 Limited company (AS) Stranda Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 3.1m
Operating profit NOK 2.0m
Equity NOK 10.0m
Incorporated 2015
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.

SGT EIGENDOM AS is registered as a limited company in Stranda, Møre og Romsdal with organisation number 915515762. The business is classified under collection of non-hazardous waste (NACE 38.110). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Drive virksomhet innen å eie, forvalte og leie ut fast eiendom, og alt som står i naturlig tilknytning til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.1m in revenue and NOK 2.0m in operating profit.

Key figures · 2024

Revenue
NOK 3.1m
Operating profit
NOK 2.0m
Equity
NOK 10.0m
Est. value
NOK 11.6m

Financial health · 2024

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

Who owns SGT EIGENDOM AS?

SGT HOLDING AS
SGT EIGENDOM AS
NOK 3.1m rev. · NOK 2.0m profit

SGT EIGENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SGT EIGENDOM AS

Who owns SGT EIGENDOM AS?

SGT HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of SGT EIGENDOM AS?

SGT EIGENDOM AS had revenue of NOK 3.1m in 2024.

Who is the general manager of SGT EIGENDOM AS?

Pål Kristen Habostad Orheim is registered as general manager of SGT EIGENDOM AS.

Where is SGT EIGENDOM AS based?

SGT EIGENDOM AS has its business address in Stranda.

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.