BIZTRAC BETA
All other professional, scientific and technical activities n.e.c.

MOBYLINQ AS

Org. no. 931615041 Limited company (AS) Larvik Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 112,000
Operating profit NOK −20.7m
Equity NOK 30,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−20,7 mill kr).

MOBYLINQ AS is registered as a limited company in Larvik, Vestfold with organisation number 931615041. The business is classified under all other professional, scientific and technical activities n.e.c. (NACE 74.990). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Å berike data fra biler og maskiner, og knytte beriket og normalisert data til relevante tjenesteleverandører.”. The most recent filed accounts, for the 2024 financial year, show NOK 112,000 in revenue and NOK −20.7m in operating profit.

Key figures · 2024

Revenue
NOK 112,000
Operating profit
NOK −20.7m
Equity
NOK 30,000
Est. value
NOK 132,000

Financial health · 2024

Liquidity
0.88
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
0.1%
Weak
Equity as a share of total capital

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

Who owns MOBYLINQ AS?

ABAX GROUP AS
MOBYLINQ AS
NOK 112,000 rev. · NOK −20.7m profit

MOBYLINQ AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MOBYLINQ AS

Who owns MOBYLINQ AS?

ABAX GROUP AS is the largest registered owner, with 100.0%.

What is the revenue of MOBYLINQ AS?

MOBYLINQ AS had revenue of NOK 112,000 in 2024.

Who is the general manager of MOBYLINQ AS?

Martijn Frits Zewald is registered as general manager of MOBYLINQ AS.

Where is MOBYLINQ AS based?

MOBYLINQ AS has its business address in Larvik.

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.