BIZTRAC BETA
Computer programming activities

GINNTECH AS

Org. no. 931340476 Limited company (AS) Trondheim Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 5.1m
Operating profit NOK −87,000
Equity NOK 500,000
Incorporated 2023
Share capital NOK 60,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−87k kr).

GINNTECH AS is registered as a limited company in Trondheim, Trøndelag with organisation number 931340476. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2023. Registered share capital is NOK 60,000, divided into 100 shares. The company's stated purpose is: “Utvikling og salg av internettbaserte tjenester, produkter og andre relevante tjenester som faller sammen med dette, herunder delta med aksjer og eierandeler i andre selskap som fremmer selskapets lønnsomhet og målsetting.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.1m in revenue and NOK −87,000 in operating profit.

Key figures · 2024

Revenue
NOK 5.1m
Operating profit
NOK −87,000
Equity
NOK 500,000
Est. value
NOK 8.8m

Financial health · 2024

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

Who owns GINNTECH AS?

NYE GINNTECH HOLDING AS
GINNTECH AS
NOK 5.1m rev. · NOK −87,000 profit

GINNTECH AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GINNTECH AS

Who owns GINNTECH AS?

NYE GINNTECH HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of GINNTECH AS?

GINNTECH AS had revenue of NOK 5.1m in 2024.

Who is the general manager of GINNTECH AS?

Svein Iversen is registered as general manager of GINNTECH AS.

Where is GINNTECH AS based?

GINNTECH AS has its business address in Trondheim.

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.