BIZTRAC BETA
Rental and operating of own or leased real estate

S.G.M EIENDOM AS

Org. no. 996269868 Limited company (AS) Lillesand Incorporated 2010 Active
Ownership graph ↗
Revenue 2025 NOK 1.8m
Operating profit NOK 1.1m
Equity NOK 3.5m
Incorporated 2010
Share capital NOK 148,000

S.G.M EIENDOM AS is registered as a limited company in Lillesand, Agder with organisation number 996269868. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2010. Registered share capital is NOK 148,000, divided into 147851 shares. The company's stated purpose is: “Eie, utleie og drift av fast eiendom, samt hva hermed står i forbindelse, herunder deltakelse i annen virksomhet ved aksjeeie eller på annen måte.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.8m in revenue and NOK 1.1m in operating profit.

Key figures · 2025

Revenue
NOK 1.8m
Operating profit
NOK 1.1m
Equity
NOK 3.5m
Est. value
NOK 4.2m

Financial health · 2025

Liquidity
0.14
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
18.7%
Good
Equity as a share of total capital

Who owns S.G.M EIENDOM AS?

S.G.M HOLDING AS
S.G.M EIENDOM AS
NOK 1.8m rev. · NOK 1.1m profit

S.G.M EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Group structure

S.G.M EIENDOM AS er morselskap for 28 datterselskaper:

Frequently asked questions about S.G.M EIENDOM AS

Who owns S.G.M EIENDOM AS?

S.G.M HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of S.G.M EIENDOM AS?

S.G.M EIENDOM AS had revenue of NOK 1.8m in 2025.

Who is the general manager of S.G.M EIENDOM AS?

Marit Gislefoss is registered as general manager of S.G.M EIENDOM AS.

Where is S.G.M EIENDOM AS based?

S.G.M EIENDOM AS has its business address in Lillesand.

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.