BIZTRAC BETA
Uoppgitt

JESSHEIM BOLIGUTVIKLING AS

Org. no. 994241362 Limited company (AS) Bærum Incorporated 2009 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −28,000
Equity NOK 1.6m
Incorporated 2009
Share capital NOK 40,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−28k kr).

JESSHEIM BOLIGUTVIKLING AS is registered as a limited company in Bærum, Akershus with organisation number 994241362. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2009. Registered share capital is NOK 40,000, divided into 2000000 shares. The company's stated purpose is: “Handel, investering i fast eiendom og verdipapirer samt annen virksomhet i tilknytning til dette, herunder deltagelse i andre selskaper med tilsvarende virksomhet gjennom egenkapital, lån eller angivelse av garantier.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −28,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −28,000
Equity
NOK 1.6m
Est. value
NOK 1.9m

Financial health · 2025

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

Who owns JESSHEIM BOLIGUTVIKLING AS?

GHG CONSULTING AS
JESSHEIM BOLIGUTVIKLING AS
NOK 0 rev. · NOK −28,000 profit

JESSHEIM BOLIGUTVIKLING AS has 6 registered shareholders:

All shareholders and roles →

Frequently asked questions about JESSHEIM BOLIGUTVIKLING AS

Who owns JESSHEIM BOLIGUTVIKLING AS?

GHG CONSULTING AS is the largest registered owner, with 36.8%.

What is the revenue of JESSHEIM BOLIGUTVIKLING AS?

JESSHEIM BOLIGUTVIKLING AS had revenue of NOK 0 in 2025.

Where is JESSHEIM BOLIGUTVIKLING AS based?

JESSHEIM BOLIGUTVIKLING AS has its business address in Bekkestua.

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.