BIZTRAC BETA
Wholesale of information and communication equipment

SMB MOBIL AS

Org. no. 927539659 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 74.2m
Operating profit NOK −11.1m
Equity NOK 5.4m
Incorporated 2021
Employees 9
Share capital NOK 13.2m

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−11,1 mill kr).
  • Nylig endring 2026-07-22 Adresseendring registrert 2026-07-22.

SMB MOBIL AS is registered as a limited company in Oslo, Oslo with organisation number 927539659. The business is classified under wholesale of information and communication equipment (NACE 46.500). The company was incorporated in 2021 and has 9 registered employees. Registered share capital is NOK 13.2m, divided into 13165943 shares. The company's stated purpose is: “Salg av telekommunikasjonsløsninger og dertil beslektede tjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 74.2m in revenue and NOK −11.1m in operating profit.

Key figures · 2025

Revenue
NOK 74.2m
Operating profit
NOK −11.1m
Equity
NOK 5.4m
Est. value
NOK 14.6m

Financial health · 2025

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

Who owns SMB MOBIL AS?

RIMA HOLDING AS
SMB MOBIL AS
NOK 74.2m rev. · NOK −11.1m profit

SMB MOBIL AS has 20+ registered shareholders:

All shareholders and roles →

Frequently asked questions about SMB MOBIL AS

Who owns SMB MOBIL AS?

RIMA HOLDING AS is the largest registered owner, with 9.5%.

What is the revenue of SMB MOBIL AS?

SMB MOBIL AS had revenue of NOK 74.2m in 2025.

Who is the general manager of SMB MOBIL AS?

Amund Helland is registered as general manager of SMB MOBIL AS.

Where is SMB MOBIL AS based?

SMB MOBIL 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.