BIZTRAC BETA
Computer programming activities

GAMING4KNOWLEDGE AS

Org. no. 935465656 Limited company (AS) Bodø Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 94,000
Operating profit NOK −22,000
Equity NOK 1,000
Incorporated 2025
Share capital NOK 30,000

Signals

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

GAMING4KNOWLEDGE AS is registered as a limited company in Bodø, Nordland with organisation number 935465656. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Utvikling og salg av digitale læringsverktøy og opplæringspakker.”. The most recent filed accounts, for the 2025 financial year, show NOK 94,000 in revenue and NOK −22,000 in operating profit.

Key figures · 2025

Revenue
NOK 94,000
Operating profit
NOK −22,000
Equity
NOK 1,000
Est. value
NOK 159,000

Financial health · 2025

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

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

Who owns GAMING4KNOWLEDGE AS?

BENTE STJERNHOLM
GAMING4KNOWLEDGE AS
NOK 94,000 rev. · NOK −22,000 profit

GAMING4KNOWLEDGE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GAMING4KNOWLEDGE AS

Who owns GAMING4KNOWLEDGE AS?

BENTE STJERNHOLM is the largest registered owner, with 100.0%.

What is the revenue of GAMING4KNOWLEDGE AS?

GAMING4KNOWLEDGE AS had revenue of NOK 94,000 in 2025.

Who is the general manager of GAMING4KNOWLEDGE AS?

Bente Stjernholm is registered as general manager of GAMING4KNOWLEDGE AS.

Where is GAMING4KNOWLEDGE AS based?

GAMING4KNOWLEDGE AS has its business address in Bodø.

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.