BIZTRAC BETA
Gambling and betting activities

VENDCOMATIC AS

Org. no. 929514351 Limited company (AS) Nittedal Incorporated 1978 Active
Ownership graph ↗
Revenue 2025 NOK 60.0m
Operating profit NOK 3.8m
Equity NOK 18.1m
Incorporated 1978
Employees 9
Share capital NOK 3.5m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

VENDCOMATIC AS is registered as a limited company in Nittedal, Akershus with organisation number 929514351. The business is classified under gambling and betting activities (NACE 92.000). The company was incorporated in 1978 and has 9 registered employees. Registered share capital is NOK 3.5m, divided into 2000 shares. The company's stated purpose is: “Industri og/eller handel og annen virksomhet i forbindelse med dette, herunder deltagelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 60.0m in revenue and NOK 3.8m in operating profit.

Key figures · 2025

Revenue
NOK 60.0m
Operating profit
NOK 3.8m
Equity
NOK 18.1m
Est. value
NOK 27.3m

Financial health · 2025

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

Who owns VENDCOMATIC AS?

GRUVI GAMES AS
VENDCOMATIC AS
NOK 60.0m rev. · NOK 3.8m profit

VENDCOMATIC AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VENDCOMATIC AS

Who owns VENDCOMATIC AS?

GRUVI GAMES AS is the largest registered owner, with 100.0%.

What is the revenue of VENDCOMATIC AS?

VENDCOMATIC AS had revenue of NOK 60.0m in 2025.

Who is the general manager of VENDCOMATIC AS?

Rune Nilsen is registered as general manager of VENDCOMATIC AS.

Where is VENDCOMATIC AS based?

VENDCOMATIC AS has its business address in Hagan.

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.