BIZTRAC BETA
Computer programming activities

SALIENT WORLD AS

Org. no. 925692824 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 440,000
Operating profit NOK −480,000
Equity NOK −288,000
Incorporated 2020
Share capital NOK 417,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−288k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−480k kr).

SALIENT WORLD AS is registered as a limited company in Oslo, Oslo with organisation number 925692824. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2020. Registered share capital is NOK 417,000, divided into 834000 shares. The company's stated purpose is: “Utvikle, patentere, lisensiere og selge softwareteknologi.”. The most recent filed accounts, for the 2025 financial year, show NOK 440,000 in revenue and NOK −480,000 in operating profit.

Key figures · 2025

Revenue
NOK 440,000
Operating profit
NOK −480,000
Equity
NOK −288,000

Financial health · 2025

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

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

Who owns SALIENT WORLD AS?

DREGG AS
SALIENT WORLD AS
NOK 440,000 rev. · NOK −480,000 profit

SALIENT WORLD AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about SALIENT WORLD AS

Who owns SALIENT WORLD AS?

DREGG AS is the largest registered owner, with 33.3%.

What is the revenue of SALIENT WORLD AS?

SALIENT WORLD AS had revenue of NOK 440,000 in 2025.

Who is the general manager of SALIENT WORLD AS?

Petter Dragøy is registered as general manager of SALIENT WORLD AS.

Where is SALIENT WORLD AS based?

SALIENT WORLD 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.