BIZTRAC BETA
Activities of agents involved in the wholesale of textiles, clothing, fur, footwear and leather goods

TEMA INVEST AS

Org. no. 975963616 Limited company (AS) Kragerø Incorporated 1995 Active
Ownership graph ↗
Operating profit NOK −431,000
Equity NOK 38.7m
Incorporated 1995
Share capital NOK 560,000

Signals

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

TEMA INVEST AS is registered as a limited company in Kragerø, Telemark with organisation number 975963616. The business is classified under activities of agents involved in the wholesale of textiles, clothing, fur, footwear and leather goods (NACE 46.160). The company was incorporated in 1995. Registered share capital is NOK 560,000, divided into 460 shares. The company's stated purpose is: “Investere i ulike typer virksomhet med økonomisk formål, herunder børsnoterte aksjeselskaper, samt det som står i forbindelse hermed, og å delta i andre selskaper med lignende formål. Videre kan selskapet drive med salg av konsulenttjenester innenfor administrasjon og ledelse. ”.

Key figures · 2024

Operating profit
NOK −431,000
Equity
NOK 38.7m
Est. value
NOK 48.3m

Financial health · 2024

Liquidity
24.96
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
96.2%
Very good
Equity as a share of total capital

Who owns TEMA INVEST AS?

MARTIN UBERG THORKILDSEN
TEMA INVEST AS
· NOK −431,000 profit

TEMA INVEST AS has 2 registered shareholders:

All shareholders and roles →

Which companies does TEMA INVEST AS own?

TEMA INVEST AS holds stakes in 25 companies:

See the full ownership structure →

Frequently asked questions about TEMA INVEST AS

Who owns TEMA INVEST AS?

MARTIN UBERG THORKILDSEN is the largest registered owner, with 66.1%.

Where is TEMA INVEST AS based?

TEMA INVEST AS has its business address in Kragerø.

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.