BIZTRAC BETA
Wholesale of other machinery and equipment

ONLINEPOS AS

Org. no. 915837883 Limited company (AS) Moss Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 4.6m
Operating profit NOK −1.9m
Equity NOK −4.9m
Incorporated 2015
Share capital NOK 33,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−4,9 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,9 mill kr).

ONLINEPOS AS is registered as a limited company in Moss, Østfold with organisation number 915837883. The business is classified under wholesale of other machinery and equipment (NACE 46.640). The company was incorporated in 2015. Registered share capital is NOK 33,000, divided into 111 shares. The company's stated purpose is: “Distribusjon og salg av kassa-apparater og butikkdatasystemer med tilhørende produkter.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.6m in revenue and NOK −1.9m in operating profit.

Key figures · 2024

Revenue
NOK 4.6m
Operating profit
NOK −1.9m
Equity
NOK −4.9m

Financial health · 2024

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

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

Who owns ONLINEPOS AS?

ONLINEPOS AS
ONLINEPOS AS
NOK 4.6m rev. · NOK −1.9m profit

ONLINEPOS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ONLINEPOS AS

Who owns ONLINEPOS AS?

ONLINEPOS AS is the largest registered owner, with 100.0%.

What is the revenue of ONLINEPOS AS?

ONLINEPOS AS had revenue of NOK 4.6m in 2024.

Who is the general manager of ONLINEPOS AS?

Kim Vegard Johansen is registered as general manager of ONLINEPOS AS.

Where is ONLINEPOS AS based?

ONLINEPOS AS has its business address in Moss.

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.