BIZTRAC BETA
Freight transport by road

TANA THERMO AS

Org. no. 920781195 Limited company (AS) Sør-Varanger Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 892,000
Operating profit NOK −210,000
Equity NOK 2.5m
Incorporated 2018
Share capital NOK 30,000

Signals

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

TANA THERMO AS is registered as a limited company in Sør-Varanger, Finnmark with organisation number 920781195. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 1200 shares. The company's stated purpose is: “Transporttjenester innen vare- og persontransport, samt sjåførutleie.”. The most recent filed accounts, for the 2024 financial year, show NOK 892,000 in revenue and NOK −210,000 in operating profit.

Key figures · 2024

Revenue
NOK 892,000
Operating profit
NOK −210,000
Equity
NOK 2.5m
Est. value
NOK 1.7m

Financial health · 2025

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

Who owns TANA THERMO AS?

MORTEN PAULSEN
TANA THERMO AS
NOK 892,000 rev. · NOK −210,000 profit

TANA THERMO AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TANA THERMO AS own?

TANA THERMO AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TANA THERMO AS

Who owns TANA THERMO AS?

MORTEN PAULSEN is the largest registered owner, with 100.0%.

What is the revenue of TANA THERMO AS?

TANA THERMO AS had revenue of NOK 892,000 in 2024.

Who is the general manager of TANA THERMO AS?

Morten Paulsen is registered as general manager of TANA THERMO AS.

Where is TANA THERMO AS based?

TANA THERMO AS has its business address in Kirkenes.

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.