BIZTRAC BETA
COMPANY REGISTER PROFILE
919342153 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Computer programming activities

DUOJA AS

Org. no. 919342153 Limited company (AS) Oslo Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 1,000
Operating profit NOK −12,000
Equity NOK 9,000
Incorporated 2017
Share capital NOK 30,000

Signals

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

DUOJA AS is registered as a limited company in Oslo, Oslo with organisation number 919342153. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Utvikling av programvare, konsulentvirksomhet, samt deltagelse i andre virksomheter og andre aktiviteter som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1,000 in revenue and NOK −12,000 in operating profit.

Key figures · 2025

Revenue
NOK 1,000
Operating profit
NOK −12,000
Equity
NOK 9,000
Est. value
NOK 7,000

Financial health · 2025

Liquidity
Not available
Current assets ÷ current liabilities
Profitability
Not available
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 DUOJA AS?

NING ZHOU
DUOJA AS
NOK 1,000 rev. · NOK −12,000 profit

DUOJA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DUOJA AS

Who owns DUOJA AS?

NING ZHOU is the largest registered owner, with 100.0%.

What is the revenue of DUOJA AS?

DUOJA AS had revenue of NOK 1,000 in 2025.

Who is the general manager of DUOJA AS?

Ning Zhou is registered as general manager of DUOJA AS.

Where is DUOJA AS based?

DUOJA 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.