BIZTRAC BETA
Industrial product and fashion design activities

COSTTRACKER AS

Org. no. 918121293 Limited company (AS) Oslo Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 4.6m
Operating profit NOK −561,000
Equity NOK 280,000
Incorporated 2016
Employees 5
Share capital NOK 1.4m

Signals

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

COSTTRACKER AS is registered as a limited company in Oslo, Oslo with organisation number 918121293. The business is classified under industrial product and fashion design activities (NACE 74.110). The company was incorporated in 2016 and has 5 registered employees. Registered share capital is NOK 1.4m, divided into 14259600 shares. The company's stated purpose is: “Utvikle, produsere og levere geniale produkter til det norske folk mens man samtidig har det gøy og legger inn en fisketur nå og da.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.6m in revenue and NOK −561,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.6m
Operating profit
NOK −561,000
Equity
NOK 280,000
Est. value
NOK 1.3m

Financial health · 2024

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

Who owns COSTTRACKER AS?

TF HOLDINGS AS
COSTTRACKER AS
NOK 4.6m rev. · NOK −561,000 profit

COSTTRACKER AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about COSTTRACKER AS

Who owns COSTTRACKER AS?

TF HOLDINGS AS is the largest registered owner, with 50.0%.

What is the revenue of COSTTRACKER AS?

COSTTRACKER AS had revenue of NOK 4.6m in 2024.

Who is the general manager of COSTTRACKER AS?

Tore Andreas Hansen is registered as general manager of COSTTRACKER AS.

Where is COSTTRACKER AS based?

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