biztrac. BETA
COMPANY REGISTER PROFILE
832243752 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

JSG EIENDOM AS

Org. no. 832243752 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK 560,000
Equity NOK 115,000
Incorporated 2023
Share capital NOK 30,000

JSG EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 832243752. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Kjøpe, selge, eie, leie ut, utvikle og drive fast eiendom, samt eie aksjer og andeler i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK 560,000 in operating profit.

Former names: JSG EIENDOM 2 AS

Key figures · 2025

Revenue
NOK 1.1m
▲ +9 %
Operating profit
NOK 560,000
▲ +158 %
Equity
NOK 115,000
▲ +106 %
Est. value
NOK 1.1m

Financial health · 2025

Liquidity
0.67
Weak
Current assets ÷ current liabilities
Profitability
4.2%
Weak
Return on total assets
Solidity
0.8%
Not satisfactory
Equity as a share of total capital

Who owns JSG EIENDOM AS?

JSG EIENDOM AS
NOK 1.1m rev. · NOK 560,000 profit

JSG EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JSG EIENDOM AS

Who owns JSG EIENDOM AS?

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

What is the revenue of JSG EIENDOM AS?

JSG EIENDOM AS had revenue of NOK 1.1m in 2025.

Who is the general manager of JSG EIENDOM AS?

Jørgen Snøås Gustavsen is registered as general manager of JSG EIENDOM AS.

Where is JSG EIENDOM AS based?

JSG 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.