biztrac. BETA
COMPANY REGISTER PROFILE
931979205 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Education at other colleges

JUSUTDANNING HØYERE UTDANNING AS

Org. no. 931979205 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Operating profit NOK −10,000
Equity NOK 10,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

JUSUTDANNING HØYERE UTDANNING AS is registered as a limited company in Oslo, Oslo with organisation number 931979205. The business is classified under education at other colleges (NACE 85.403). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Tilby høyere utdanning innenfor jus og juridisk kompetanseheving, med tilhørende forskning og faglig utviklingsarbeid, og det som naturlig står i forbindelse med dette.”.

Key figures · 2025

Operating profit
NOK −10,000
▼ −224 %
Equity
NOK 10,000
▼ −50 %
Est. value
NOK 15,000

Financial health · 2025

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

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

Who owns JUSUTDANNING HØYERE UTDANNING AS?

JUSUTDANNING HØYERE UTDANNING AS
· NOK −10,000 profit

JUSUTDANNING HØYERE UTDANNING AS has 1 registered shareholder:

All shareholders and roles →

Group structure

JUSUTDANNING HØYERE UTDANNING AS er morselskap for 2 datterselskaper:

Frequently asked questions about JUSUTDANNING HØYERE UTDANNING AS

Who owns JUSUTDANNING HØYERE UTDANNING AS?

JUSUTDANNING HOLDING AS is the largest registered owner, with 100.0%.

Where is JUSUTDANNING HØYERE UTDANNING AS based?

JUSUTDANNING HØYERE UTDANNING 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.