biztrac. BETA
COMPANY REGISTER PROFILE
918441557 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Repair and maintenance of motor vehicles

M & M RACING AS

Org. no. 918441557 Limited company (AS) Nordreisa Incorporated 2017 Active
Revenue 2025 NOK 3.1m
Operating profit NOK 356,000
Equity NOK 1.3m
Incorporated 2017
Share capital NOK 30,000

M & M RACING AS is registered as a limited company in Nordreisa, Troms with organisation number 918441557. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Reparasjon og vedlikehold av lett motorkjøretøy samt tjenester som naturlig hører med til dette. Selskapet skal også kunne investere i andre selskap hvis dette er naturlig.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.1m in revenue and NOK 356,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.1m
▲ +12 %
Operating profit
NOK 356,000
▲ +170 %
Equity
NOK 1.3m
▲ +25 %
Est. value
NOK 2.0m

Financial health · 2025

Liquidity
4.25
Very good
Current assets ÷ current liabilities
Profitability
23.3%
Very good
Return on total assets
Solidity
69.9%
Very good
Equity as a share of total capital

Who owns M & M RACING AS?

M & M RACING AS
NOK 3.1m rev. · NOK 356,000 profit

M & M RACING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about M & M RACING AS

Who owns M & M RACING AS?

Geir-Hugo Olsen is the largest registered owner, with 100.0%.

What is the revenue of M & M RACING AS?

M & M RACING AS had revenue of NOK 3.1m in 2025.

Who is the general manager of M & M RACING AS?

Geir-Hugo Olsen is registered as general manager of M & M RACING AS.

Where is M & M RACING AS based?

M & M RACING AS has its business address in Rotsund.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.