BIZTRAC BETA
COMPANY REGISTER PROFILE
994921444 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Gambling and betting activities

NORSKE SPILL AS

Org. no. 994921444 Limited company (AS) Hamar Incorporated 2009 Active
Ownership graph ↗
Operating profit NOK −54,000
Equity NOK 494,000
Incorporated 2009
Share capital NOK 200,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−54k kr).

NORSKE SPILL AS is registered as a limited company in Hamar, Innlandet with organisation number 994921444. The business is classified under gambling and betting activities (NACE 92.000). The company was incorporated in 2009. Registered share capital is NOK 200,000, divided into 200000 shares. The company's stated purpose is: “Eierskap til og forvaltning av immaterielle rettigheter.”.

Former names: NT DS AS

Key figures · 2025

Operating profit
NOK −54,000
▼ −29 %
Equity
NOK 494,000
▼ −6 %
Est. value
NOK 618,000

Financial health · 2025

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

Who owns NORSKE SPILL AS?

NORSKE SPILL AS
· NOK −54,000 profit

NORSKE SPILL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NORSKE SPILL AS

Who owns NORSKE SPILL AS?

NORSK TIPPING AS is the largest registered owner, with 100.0%.

Where is NORSKE SPILL AS based?

NORSKE SPILL AS has its business address in Hamar.

Property

Business address Måsåbekkvegen 20, 2315 Hamar
Cadastral unit 3403-1/4460/0/0

6 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.