BIZTRAC BETA
Research and experimental development on natural sciences and engineering

GENESEQUE AS

Org. no. 992322551 Limited company (AS) Trondheim Incorporated 2008 Active
Ownership graph ↗
Operating profit NOK −59,000
Equity NOK −232,000
Incorporated 2008
Share capital NOK 348,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−232k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−59k kr).

GENESEQUE AS is registered as a limited company in Trondheim, Trøndelag with organisation number 992322551. The business is classified under research and experimental development on natural sciences and engineering (NACE 72.100). The company was incorporated in 2008. Registered share capital is NOK 348,000, divided into 3475625 shares. The company's stated purpose is: “Fremstilling og salg av laboratorieutstyr og andre produkter som naturlig hører sammen med dette samt elektronisk produksjonsutstyr, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretagende.”.

Key figures · 2024

Operating profit
NOK −59,000
Equity
NOK −232,000

Financial health · 2024

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

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

Who owns GENESEQUE AS?

MICRONAX AS
GENESEQUE AS
· NOK −59,000 profit

GENESEQUE AS has 6 registered shareholders:

All shareholders and roles →

Frequently asked questions about GENESEQUE AS

Who owns GENESEQUE AS?

MICRONAX AS is the largest registered owner, with 60.3%.

Who is the general manager of GENESEQUE AS?

Jarle Kotsbak is registered as general manager of GENESEQUE AS.

Where is GENESEQUE AS based?

GENESEQUE 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.