BIZTRAC BETA
COMPANY REGISTER PROFILE
832765082 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Business and other management consultancy activities

MULTITRACK AS

Org. no. 832765082 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 1.2m
Operating profit NOK 83,000
Equity NOK 95,000
Incorporated 2023
Share capital NOK 30,000

MULTITRACK AS is registered as a limited company in Oslo, Oslo with organisation number 832765082. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Bedriftrådgiving, forretning-utvikling, konsulting i sport, sykkel- og mobilitet bransjen.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK 83,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.2m
Operating profit
NOK 83,000
Equity
NOK 95,000
Est. value
NOK 463,000

Financial health · 2024

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

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

Who owns MULTITRACK AS?

RÉMI MATHIEU LELIEVRE
MULTITRACK AS
NOK 1.2m rev. · NOK 83,000 profit

MULTITRACK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MULTITRACK AS

Who owns MULTITRACK AS?

RÉMI MATHIEU LELIEVRE is the largest registered owner, with 100.0%.

What is the revenue of MULTITRACK AS?

MULTITRACK AS had revenue of NOK 1.2m in 2025.

Who is the general manager of MULTITRACK AS?

Rémi Mathieu Lelievre is registered as general manager of MULTITRACK AS.

Where is MULTITRACK AS based?

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