BIZTRAC BETA
Other support activities to arts and performing arts

TRACK CONSULTING AS

Org. no. 920297668 Limited company (AS) Ringerike Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 617,000
Operating profit NOK 277,000
Equity NOK 1.0m
Incorporated 2018
Share capital NOK 30,000

TRACK CONSULTING AS is registered as a limited company in Ringerike, Buskerud with organisation number 920297668. The business is classified under other support activities to arts and performing arts (NACE 90.390). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Rådgivning, konsulenttjenester, forfatter/skribentvirksomhet, eie og drive fast eiendom, investering i aksjer og andre verdipapirer og kunne delta i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 617,000 in revenue and NOK 277,000 in operating profit.

Key figures · 2024

Revenue
NOK 617,000
Operating profit
NOK 277,000
Equity
NOK 1.0m
Est. value
NOK 1.4m

Financial health · 2024

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

Who owns TRACK CONSULTING AS?

JAN HELGE ØSTLUND
TRACK CONSULTING AS
NOK 617,000 rev. · NOK 277,000 profit

TRACK CONSULTING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TRACK CONSULTING AS

Who owns TRACK CONSULTING AS?

JAN HELGE ØSTLUND is the largest registered owner, with 100.0%.

What is the revenue of TRACK CONSULTING AS?

TRACK CONSULTING AS had revenue of NOK 617,000 in 2024.

Who is the general manager of TRACK CONSULTING AS?

Jan Helge Østlund is registered as general manager of TRACK CONSULTING AS.

Where is TRACK CONSULTING AS based?

TRACK CONSULTING AS has its business address in Hønefoss.

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.