BIZTRAC BETA
Retail sale of clothing

DISMA AS

Org. no. 817124402 Limited company (AS) Tønsberg Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 33,000
Operating profit NOK −60,000
Equity NOK −183,000
Incorporated 2016
Share capital NOK 30,000

Signals

3 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−183k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−60k kr).
  • Nylig endring 2026-02-24 Adresseendring registrert 2026-02-24.

DISMA AS is registered as a limited company in Tønsberg, Vestfold with organisation number 817124402. The business is classified under retail sale of clothing (NACE 47.710). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Drive med import kjøp/salg av klær og suvenirer. Det kan også drives med oppussing, restaurering, oppbygging og rengjøring av boliger. Selskapet kan også drive med kjøp/drift av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 33,000 in revenue and NOK −60,000 in operating profit.

Key figures · 2025

Revenue
NOK 33,000
Operating profit
NOK −60,000
Equity
NOK −183,000

Financial health · 2025

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

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

Who owns DISMA AS?

ELENA BELLOS
DISMA AS
NOK 33,000 rev. · NOK −60,000 profit

DISMA AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about DISMA AS

Who owns DISMA AS?

ELENA BELLOS is the largest registered owner, with 50.0%.

What is the revenue of DISMA AS?

DISMA AS had revenue of NOK 33,000 in 2025.

Where is DISMA AS based?

DISMA AS has its business address in Tønsberg.

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.