BIZTRAC BETA
Wholesale of mining, construction and civil engineering machinery

JUNJIN NORGE AS

Org. no. 991375074 Limited company (AS) Sandefjord Incorporated 2007 Active
Ownership graph ↗
Operating profit NOK −7,000
Equity NOK −30,000
Incorporated 2007
Share capital NOK 200,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−30k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−7k kr).

JUNJIN NORGE AS is registered as a limited company in Sandefjord, Vestfold with organisation number 991375074. The business is classified under wholesale of mining, construction and civil engineering machinery (NACE 46.630). The company was incorporated in 2007. Registered share capital is NOK 200,000, divided into 2000 shares. The company's stated purpose is: “Import, eksport, kjøp og salg av borerigger til fjellboring inkl alt tilleggsutstyr, deler og andre produkter som naturlig hører sammen med dette. Kjøp, salg og drift av fast eiendom, deltakelse i andre selskaper samt alt annet som står i forbindelse med dette.”.

Key figures · 2024

Operating profit
NOK −7,000
Equity
NOK −30,000

Financial health · 2024

Liquidity
0.01
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-15902.2%
Weak
Equity as a share of total capital

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

Who owns JUNJIN NORGE AS?

OLAV ÅGE ASKJE
JUNJIN NORGE AS
· NOK −7,000 profit

JUNJIN NORGE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JUNJIN NORGE AS

Who owns JUNJIN NORGE AS?

OLAV ÅGE ASKJE is the largest registered owner, with 100.0%.

Who is the general manager of JUNJIN NORGE AS?

Olav Åge Askje is registered as general manager of JUNJIN NORGE AS.

Where is JUNJIN NORGE AS based?

JUNJIN NORGE AS has its business address in Sandefjord.

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.