BIZTRAC BETA
Manufacture of medical and dental instruments and supplies

TEAM TECH AS

Org. no. 961542669 Limited company (AS) Oslo Incorporated 1991 Active
Ownership graph ↗
Revenue 2024 NOK 3.5m
Operating profit NOK 28,000
Equity NOK −38,000
Incorporated 1991
Share capital NOK 204,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−38k kr).

TEAM TECH AS is registered as a limited company in Oslo, Oslo with organisation number 961542669. The business is classified under manufacture of medical and dental instruments and supplies (NACE 32.500). The company was incorporated in 1991. Registered share capital is NOK 204,000, divided into 204000 shares. The company's stated purpose is: “Kjøp og salg av tannteknikertjenester og konsulentbistand i drift og utvikling innen samme og tilliggende bransjer.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.5m in revenue and NOK 28,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.5m
Operating profit
NOK 28,000
Equity
NOK −38,000
Est. value
NOK 228,000

Financial health · 2024

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

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

Who owns TEAM TECH AS?

DENTAL KERAM AS
TEAM TECH AS
NOK 3.5m rev. · NOK 28,000 profit

TEAM TECH AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TEAM TECH AS

Who owns TEAM TECH AS?

DENTAL KERAM AS is the largest registered owner, with 91.2%.

What is the revenue of TEAM TECH AS?

TEAM TECH AS had revenue of NOK 3.5m in 2024.

Who is the general manager of TEAM TECH AS?

Hans-Olav Eek is registered as general manager of TEAM TECH AS.

Where is TEAM TECH AS based?

TEAM TECH 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.