BIZTRAC BETA
Wholesale of information and communication equipment

PYTON SYSTEMER AS

Org. no. 929574028 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 4.7m
Operating profit NOK 32,000
Equity NOK 239,000
Incorporated 2022
Share capital NOK 30,000

PYTON SYSTEMER AS is registered as a limited company in Oslo, Oslo with organisation number 929574028. The business is classified under wholesale of information and communication equipment (NACE 46.500). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Kjøp og salg av data- og elektronikkprodukter og dertil beslektede varer og tjenester, samt annet som naturlig hører inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.7m in revenue and NOK 32,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.7m
Operating profit
NOK 32,000
Equity
NOK 239,000
Est. value
NOK 262,000

Financial health · 2025

Liquidity
1.86
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
12.5%
Satisfactory
Equity as a share of total capital

Who owns PYTON SYSTEMER AS?

DIGITAL IMPULS HOLDING AS
PYTON SYSTEMER AS
NOK 4.7m rev. · NOK 32,000 profit

PYTON SYSTEMER AS has 1 registered shareholder:

All shareholders and roles →

Group structure

PYTON SYSTEMER AS er morselskap for 2 datterselskaper:

Frequently asked questions about PYTON SYSTEMER AS

Who owns PYTON SYSTEMER AS?

DIGITAL IMPULS HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of PYTON SYSTEMER AS?

PYTON SYSTEMER AS had revenue of NOK 4.7m in 2025.

Who is the general manager of PYTON SYSTEMER AS?

Espen Elvekrok is registered as general manager of PYTON SYSTEMER AS.

Where is PYTON SYSTEMER AS based?

PYTON SYSTEMER AS has its business address in Oslo.

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.