BIZTRAC BETA
Uoppgitt

WISDOM EDITION AS

Org. no. 918906843 Limited company (AS) Oslo Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −655,000
Equity NOK −22.9m
Incorporated 2017
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−22,9 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−655k kr).

WISDOM EDITION AS is registered as a limited company in Oslo, Oslo with organisation number 918906843. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Investeringer i aksjer og andre selskaper, samt alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −655,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −655,000
Equity
NOK −22.9m

Financial health · 2024

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

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

Who owns WISDOM EDITION AS?

ALTRIX INVEST AG
WISDOM EDITION AS
NOK 0 rev. · NOK −655,000 profit

WISDOM EDITION AS has 2 registered shareholders:

All shareholders and roles →

Which companies does WISDOM EDITION AS own?

WISDOM EDITION AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about WISDOM EDITION AS

Who owns WISDOM EDITION AS?

ALTRIX INVEST AG is the largest registered owner, with 75.0%.

What is the revenue of WISDOM EDITION AS?

WISDOM EDITION AS had revenue of NOK 0 in 2024.

Where is WISDOM EDITION AS based?

WISDOM EDITION 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.