BIZTRAC BETA
Retail sale of second-hand goods

JOMA MULTISERVICE AS

Org. no. 935342538 Limited company (AS) Time Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 106,000
Operating profit NOK −18,000
Equity NOK 115,000
Incorporated 2025
Share capital NOK 30,000

Signals

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

JOMA MULTISERVICE AS is registered as a limited company in Time, Rogaland with organisation number 935342538. The business is classified under retail sale of second-hand goods (NACE 47.790). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Kjøp og salg av brukt sportsutstyr, utleie av utstyr som verktøy og transportoppdrag.”. The most recent filed accounts, for the 2025 financial year, show NOK 106,000 in revenue and NOK −18,000 in operating profit.

Key figures · 2025

Revenue
NOK 106,000
Operating profit
NOK −18,000
Equity
NOK 115,000
Est. value
NOK 89,000

Financial health · 2025

Liquidity
19.90
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
95.0%
Very good
Equity as a share of total capital

Who owns JOMA MULTISERVICE AS?

JOHAN MAGNE SANDAL
JOMA MULTISERVICE AS
NOK 106,000 rev. · NOK −18,000 profit

JOMA MULTISERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JOMA MULTISERVICE AS

Who owns JOMA MULTISERVICE AS?

JOHAN MAGNE SANDAL is the largest registered owner, with 100.0%.

What is the revenue of JOMA MULTISERVICE AS?

JOMA MULTISERVICE AS had revenue of NOK 106,000 in 2025.

Who is the general manager of JOMA MULTISERVICE AS?

Johan Magne Sandal is registered as general manager of JOMA MULTISERVICE AS.

Where is JOMA MULTISERVICE AS based?

JOMA MULTISERVICE AS has its business address in Bryne.

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.