biztrac. BETA
COMPANY REGISTER PROFILE
926362372 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Wholesale of pharmaceutical and medical goods

ONE DIAGNOSTICS AS

Org. no. 926362372 Limited company (AS) Oslo Incorporated 2020 Active
Revenue 2025 NOK 5.2m
Operating profit NOK −176,000
Equity NOK −218,000
Incorporated 2020
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−218k kr).

ONE DIAGNOSTICS AS is registered as a limited company in Oslo, Oslo with organisation number 926362372. The business is classified under wholesale of pharmaceutical and medical goods (NACE 46.460). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Handel og tjenesteytende virksomhet med medisinske diagnostikk produkter samt alt som faller naturlig inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.2m in revenue and NOK −176,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.2m
▼ −31 %
Operating profit
NOK −176,000
▼ −138 %
Equity
NOK −218,000
▼ −400 %
Est. value
NOK 3.2m

Financial health · 2025

Liquidity
0.75
Weak
Current assets ÷ current liabilities
Profitability
1.8%
Weak
Return on total assets
Solidity
-5.3%
Weak
Equity as a share of total capital

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

Who owns ONE DIAGNOSTICS AS?

ONE DIAGNOSTICS AS
NOK 5.2m rev. · NOK −176,000 profit

ONE DIAGNOSTICS AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about ONE DIAGNOSTICS AS

Who owns ONE DIAGNOSTICS AS?

Marius Grone is the largest registered owner, with 33.3%.

What is the revenue of ONE DIAGNOSTICS AS?

ONE DIAGNOSTICS AS had revenue of NOK 5.2m in 2025.

Where is ONE DIAGNOSTICS AS based?

ONE DIAGNOSTICS 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.