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

JANSEN GILJE INVEST AS

Org. no. 979194064 Limited company (AS) Stavanger Incorporated 1997 Active
Ownership graph ↗
Operating profit NOK −19,000
Equity NOK −973,000
Incorporated 1997
Share capital NOK 300,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−973k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−19k kr).

JANSEN GILJE INVEST AS is registered as a limited company in Stavanger, Rogaland with organisation number 979194064. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1997. Registered share capital is NOK 300,000. The company's stated purpose is: “Investering i verdipapirer og eiendommer, samt hva hermed står i forbindelse. Selskapet kan delta i andre selskaper med lignende virksomheter.”.

Key figures · 2025

Operating profit
NOK −19,000
▲ +11 %
Equity
NOK −973,000
▼ −7 %

Financial health · 2025

Liquidity
0.03
Not satisfactory
Current assets ÷ current liabilities
Profitability
-63.7%
Not satisfactory
Return on total assets
Solidity
-3096.8%
Weak
Equity as a share of total capital

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

Who owns JANSEN GILJE INVEST AS?

JANSEN GILJE INVEST AS
· NOK −19,000 profit

JANSEN GILJE INVEST AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about JANSEN GILJE INVEST AS

Who owns JANSEN GILJE INVEST AS?

Morten Gilje is the largest registered owner, with 50.0%.

Who is the general manager of JANSEN GILJE INVEST AS?

Morten Gilje is registered as general manager of JANSEN GILJE INVEST AS.

Where is JANSEN GILJE INVEST AS based?

JANSEN GILJE INVEST AS has its business address in Stavanger.

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.