BIZTRAC BETA
Wholesale of other machinery and equipment

SYSTEMTEKNIKK AS

Org. no. 916552092 Limited company (AS) Enebakk Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 278,000
Operating profit NOK 2,000
Equity NOK 37,000
Incorporated 2016
Share capital NOK 30,000

SYSTEMTEKNIKK AS is registered as a limited company in Enebakk, Akershus with organisation number 916552092. The business is classified under wholesale of other machinery and equipment (NACE 46.640). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Tjenester knyttet til installasjon av lys/AV/lydanlegg, samt salg av GPS baserte enheter og tjenester, herunder tjenester tilknyttet dette formålet.”. The most recent filed accounts, for the 2025 financial year, show NOK 278,000 in revenue and NOK 2,000 in operating profit.

Key figures · 2025

Revenue
NOK 278,000
Operating profit
NOK 2,000
Equity
NOK 37,000
Est. value
NOK 29,000

Financial health · 2025

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

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

Who owns SYSTEMTEKNIKK AS?

KIM ERIK JOSÉ DE SOUSA
SYSTEMTEKNIKK AS
NOK 278,000 rev. · NOK 2,000 profit

SYSTEMTEKNIKK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SYSTEMTEKNIKK AS

Who owns SYSTEMTEKNIKK AS?

KIM ERIK JOSÉ DE SOUSA is the largest registered owner, with 100.0%.

What is the revenue of SYSTEMTEKNIKK AS?

SYSTEMTEKNIKK AS had revenue of NOK 278,000 in 2025.

Who is the general manager of SYSTEMTEKNIKK AS?

Kim Erik José De Sousa is registered as general manager of SYSTEMTEKNIKK AS.

Where is SYSTEMTEKNIKK AS based?

SYSTEMTEKNIKK AS has its business address in Ytre Enebakk.

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.