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

RESIDENTIAL JESSHEIM AS

Org. no. 820951042 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Operating profit NOK −33,000
Equity NOK −16.4m
Incorporated 2018
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−16,4 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−33k kr).

RESIDENTIAL JESSHEIM AS is registered as a limited company in Oslo, Oslo with organisation number 820951042. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Investere i, utvikle og drifte fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”.

Former names: SKARPSNO JESSHEIM AS, BONAVA JESSHEIM AS

Key figures · 2025

Operating profit
NOK −33,000
▲ +41 %
Equity
NOK −16.4m
▼ −31 %

Financial health · 2025

Liquidity
0.88
Weak
Current assets ÷ current liabilities
Profitability
-0.0%
Not satisfactory
Return on total assets
Solidity
-23.7%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns RESIDENTIAL JESSHEIM AS?

RESIDENTIAL JESSHEIM AS
· NOK −33,000 profit

RESIDENTIAL JESSHEIM AS has 1 registered shareholder:

All shareholders and roles →

Group structure

RESIDENTIAL JESSHEIM AS er morselskap for 16 datterselskaper:

Frequently asked questions about RESIDENTIAL JESSHEIM AS

Who owns RESIDENTIAL JESSHEIM AS?

NÅBO AS is the largest registered owner, with 100.0%.

Where is RESIDENTIAL JESSHEIM AS based?

RESIDENTIAL JESSHEIM 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.