BIZTRAC BETA
Rental and operating of own or leased real estate

SG 34 EIENDOM AS

Org. no. 813662442 Limited company (AS) Oslo Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 21.3m
Operating profit NOK 9.7m
Equity NOK 43.9m
Incorporated 2014
Share capital NOK 820,000

SG 34 EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 813662442. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2014. Registered share capital is NOK 820,000, divided into 55000 shares. The company's stated purpose is: “Kjøpe, utvikle og selge fast eiendom, herunder eie aksjer i selskaper som direkte eller indirekte kjøper eller eier, utvikler og selger fast eiendom samt hva som naturlig knytter seg til slik virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 21.3m in revenue and NOK 9.7m in operating profit.

Key figures · 2024

Revenue
NOK 21.3m
Operating profit
NOK 9.7m
Equity
NOK 43.9m
Est. value
NOK 56.8m

Financial health · 2024

Liquidity
0.19
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
76.2%
Very good
Equity as a share of total capital

Who owns SG 34 EIENDOM AS?

LANDBRUKSKVARTALET UTVIKLING AS
SG 34 EIENDOM AS
NOK 21.3m rev. · NOK 9.7m profit

SG 34 EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SG 34 EIENDOM AS

Who owns SG 34 EIENDOM AS?

LANDBRUKSKVARTALET UTVIKLING AS is the largest registered owner, with 100.0%.

What is the revenue of SG 34 EIENDOM AS?

SG 34 EIENDOM AS had revenue of NOK 21.3m in 2024.

Who is the general manager of SG 34 EIENDOM AS?

Leif Egil Slåtten is registered as general manager of SG 34 EIENDOM AS.

Where is SG 34 EIENDOM AS based?

SG 34 EIENDOM AS has its business address in Oslo.

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.