BIZTRAC BETA
Repair and maintenance of motor vehicles

MAXAM TUNING AS

Org. no. 993347213 Limited company (AS) Sarpsborg Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 2.0m
Operating profit NOK 190,000
Equity NOK 2.3m
Incorporated 2008
Share capital NOK 100,000

Signals

1 flags
  • Nylig endring 2026-02-12 Adresseendring registrert 2026-02-12.

MAXAM TUNING AS is registered as a limited company in Sarpsborg, Østfold with organisation number 993347213. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2008. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Vedlikehold og reparasjon av motorvogner, unntatt motorsykler. Salg og import til motorvogner, samt utleie av diverse bilhengere.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.0m in revenue and NOK 190,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.0m
Operating profit
NOK 190,000
Equity
NOK 2.3m
Est. value
NOK 1.7m

Financial health · 2024

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

Who owns MAXAM TUNING AS?

LARS-GUNNAR SÆLID ROSTED
MAXAM TUNING AS
NOK 2.0m rev. · NOK 190,000 profit

MAXAM TUNING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MAXAM TUNING AS

Who owns MAXAM TUNING AS?

LARS-GUNNAR SÆLID ROSTED is the largest registered owner, with 100.0%.

What is the revenue of MAXAM TUNING AS?

MAXAM TUNING AS had revenue of NOK 2.0m in 2024.

Who is the general manager of MAXAM TUNING AS?

Lars-Gunnar Sælid Rosted is registered as general manager of MAXAM TUNING AS.

Where is MAXAM TUNING AS based?

MAXAM TUNING AS has its business address in Sarpsborg.

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.