BIZTRAC BETA
Uoppgitt

JEGL INVEST AS

Org. no. 928320812 Limited company (AS) Gloppen Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −102,000
Equity NOK 7.8m
Incorporated 2021
Share capital NOK 30,000

Signals

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

JEGL INVEST AS is registered as a limited company in Gloppen, Vestland with organisation number 928320812. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investeringsvirksomhet som omfatter kjøp og salg av aksjer, verdipapirer og andeler i andre selskaper. Ytelser av tjenester til selskaper der man har direkte eller indirekte eierinteresser, samt det som naturlig hører under forannevnte.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −102,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −102,000
Equity
NOK 7.8m
Est. value
NOK 4.9m

Financial health · 2025

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

Who owns JEGL INVEST AS?

JAN ELLING GLOPPHOLM
JEGL INVEST AS
NOK 0 rev. · NOK −102,000 profit

JEGL INVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JEGL INVEST AS

Who owns JEGL INVEST AS?

JAN ELLING GLOPPHOLM is the largest registered owner, with 100.0%.

What is the revenue of JEGL INVEST AS?

JEGL INVEST AS had revenue of NOK 0 in 2025.

Who is the general manager of JEGL INVEST AS?

Jan Elling Gloppholm is registered as general manager of JEGL INVEST AS.

Where is JEGL INVEST AS based?

JEGL INVEST AS has its business address in Byrkjelo.

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.