BIZTRAC BETA
Repair and maintenance of computers and communication equipment

MOBILVERKSTEDET AS

Org. no. 917723559 Limited company (AS) Sandefjord Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 3.9m
Operating profit NOK 77,000
Equity NOK 1.2m
Incorporated 2016
Share capital NOK 30,000

MOBILVERKSTEDET AS is registered as a limited company in Sandefjord, Vestfold with organisation number 917723559. The business is classified under repair and maintenance of computers and communication equipment (NACE 95.100). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Salg/reparasjon av mobiltelefoner og tilbehør.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.9m in revenue and NOK 77,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.9m
Operating profit
NOK 77,000
Equity
NOK 1.2m
Est. value
NOK 1.0m

Financial health · 2025

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

Who owns MOBILVERKSTEDET AS?

WARA HOLDING AS
MOBILVERKSTEDET AS
NOK 3.9m rev. · NOK 77,000 profit

MOBILVERKSTEDET AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MOBILVERKSTEDET AS own?

MOBILVERKSTEDET AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MOBILVERKSTEDET AS

Who owns MOBILVERKSTEDET AS?

WARA HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of MOBILVERKSTEDET AS?

MOBILVERKSTEDET AS had revenue of NOK 3.9m in 2025.

Who is the general manager of MOBILVERKSTEDET AS?

Raymond Wassengen is registered as general manager of MOBILVERKSTEDET AS.

Where is MOBILVERKSTEDET AS based?

MOBILVERKSTEDET AS has its business address in Sandefjord.

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.