BIZTRAC BETA
Computer programming activities

LAGSPILL AS

Org. no. 925905410 Limited company (AS) Tromsø Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −277,000
Equity NOK −172,000
Incorporated 2020
Share capital NOK 240,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−172k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−277k kr).

LAGSPILL AS is registered as a limited company in Tromsø, Troms with organisation number 925905410. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2020. Registered share capital is NOK 240,000, divided into 240000 shares. The company's stated purpose is: “Utvikle digitale, nettbaserte hjelpemiddel for spill og tilby spillene til publikum gjennom egne nettsider eller i samarbeid med andre nettjenester, samt det som hører naturlig hører til en slik type virksomhet, samt deltakelse i annen virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −277,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −277,000
Equity
NOK −172,000

Financial health · 2025

Liquidity
8.22
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-533.9%
Weak
Equity as a share of total capital

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

Who owns LAGSPILL AS?

FORETAKSOM AS
LAGSPILL AS
NOK 0 rev. · NOK −277,000 profit

LAGSPILL AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about LAGSPILL AS

Who owns LAGSPILL AS?

FORETAKSOM AS is the largest registered owner, with 25.0%.

What is the revenue of LAGSPILL AS?

LAGSPILL AS had revenue of NOK 0 in 2025.

Where is LAGSPILL AS based?

LAGSPILL AS has its business address in Tromsø.

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.