BIZTRAC BETA
Research and experimental development on natural sciences and engineering

TEMASI AS

Org. no. 994631950 Limited company (AS) Bærum Incorporated 2009 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −84,000
Equity NOK −466,000
Incorporated 2009
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−466k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−84k kr).

TEMASI AS is registered as a limited company in Bærum, Akershus with organisation number 994631950. The business is classified under research and experimental development on natural sciences and engineering (NACE 72.100). The company was incorporated in 2009. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “a) Forskning og utvikling av produkter for industrien b) Kommersialisere disse produktene c) Kjøp og salg av produkter og tjenester d) Selskapet skal også kunne være deltager i andre selskaper”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −84,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −84,000
Equity
NOK −466,000

Financial health · 2025

Liquidity
135.18
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-188.5%
Weak
Equity as a share of total capital

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

Who owns TEMASI AS?

CONNEX AS
TEMASI AS
NOK 0 rev. · NOK −84,000 profit

TEMASI AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TEMASI AS

Who owns TEMASI AS?

CONNEX AS is the largest registered owner, with 85.0%.

What is the revenue of TEMASI AS?

TEMASI AS had revenue of NOK 0 in 2025.

Where is TEMASI AS based?

TEMASI AS has its business address in Snarøya.

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.