BIZTRAC BETA
Legal activities

JURIO NORGE AS

Org. no. 932214784 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 13,000
Operating profit NOK −84,000
Equity NOK −60,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

JURIO NORGE AS is registered as a limited company in Oslo, Oslo with organisation number 932214784. The business is classified under legal activities (NACE 69.100). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Tilby juridiske produkter og tjenester til bedrifter og privatpersoner og alt som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 13,000 in revenue and NOK −84,000 in operating profit.

Key figures · 2024

Revenue
NOK 13,000
Operating profit
NOK −84,000
Equity
NOK −60,000

Financial health · 2024

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

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

Who owns JURIO NORGE AS?

LEGALDESK.DK APS
JURIO NORGE AS
NOK 13,000 rev. · NOK −84,000 profit

JURIO NORGE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does JURIO NORGE AS own?

JURIO NORGE AS holds stakes in 13 companies:

See the full ownership structure →

Frequently asked questions about JURIO NORGE AS

Who owns JURIO NORGE AS?

LEGALDESK.DK APS is the largest registered owner, with 100.0%.

What is the revenue of JURIO NORGE AS?

JURIO NORGE AS had revenue of NOK 13,000 in 2024.

Where is JURIO NORGE AS based?

JURIO NORGE AS has its business address in Oslo.

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.