biztrac. BETA
COMPANY REGISTER PROFILE
914843928 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Beverage serving activities

JGL AS

Org. no. 914843928 Limited company (AS) Ullensaker Incorporated 2014 Active
Revenue 2025 NOK 0
Operating profit NOK −10,000
Equity NOK −475,000
Incorporated 2014
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−475k kr).

JGL AS is registered as a limited company in Ullensaker, Akershus with organisation number 914843928. The business is classified under beverage serving activities (NACE 56.300). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Kaffedrift/pub. Servering av mat/alkohol samt transporttjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −10,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −10,000
▲ +84 %
Equity
NOK −475,000
▼ −2 %

Financial health · 2025

Liquidity
0.02
Not satisfactory
Current assets ÷ current liabilities
Profitability
-3.0%
Not satisfactory
Return on total assets
Solidity
-141.8%
Weak
Equity as a share of total capital

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

Who owns JGL AS?

JGL AS
NOK 0 rev. · NOK −10,000 profit

JGL AS has 2 registered shareholders:

All shareholders and roles →

Which companies does JGL AS own?

JGL AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about JGL AS

Who owns JGL AS?

Jahn Andreassen is the largest registered owner, with 50.0%.

What is the revenue of JGL AS?

JGL AS had revenue of NOK 0 in 2025.

Who is the general manager of JGL AS?

Gerd Lise Nes is registered as general manager of JGL AS.

Where is JGL AS based?

JGL AS has its business address in Kløfta.

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.